morphia | MongoDB object-document mapper

You'd write something like: datastore.find(type).filter(eq("_id", id.toUUID())).first(). You can also just refer to the name of the java field and Morphia will map that correctly.

What version are you updating from? That API looks crazy old to me.

If you're on 1.6.1, you can happily use that method. Once you move to 2.x, the way that modify operations are done and how options are passed changes a bit so you'll need to do a bit of rework regardless. (There's an option to keep using the legacy API that's deprecated in it's entirety and will be removed soon. maybe in 2.4.)

2.x is a complete rethink of that API in to what is intended to be a more reasonable, usable set of interfaces. So far folks seem happy with it. I'd highly recommend an upgrade.

Adding the annotation @EnableMongoRepositories({"path.to.repos"}) above my main class as well as the following pom dependencies:

By referring to Case insensitive sorting in MongoDB, we can set the collation with {locale: "en"}. This is a little bit counter intuitive at first glance. How come setting the locale can make the query ignore case?

So let's check the documentation of collation, the case sensitivity is actually determined by caseLevel.

Optional. Flag that determines whether to include case comparison at strength level 1 or 2.
...
If false, do not include case comparison at level 1 or 2. The default is false.

The default value is false and hence sorting will ignore case just by setting the locale.

In Morphia, we can set the Collation through FindOptions, as below.

It depends on what version you're using but with version 2.2, you would connect something like this:

I'm the morphia dev so there's some bias here but i'll try to be fair. when i first started building the pojo support in to the driver (i used to work for mongodb) my goal was to build as close to an ODM as possible in the driver so that morphia, such as it was, would only need to be a thin veneer on the driver. Some of my plans never came to fruition as I left the company mid-effort. That said, it came pretty close.

I know of several projects that are happily using the pojo codecs. If they fit your needs, then I would suggest to just go with that. For my own perspective, I think morphia offers a fair bit that the driver doesn't (to my knowledge.) Morphia supports annotation driven index and document validation definitions, and collection caps, e.g. It's a bit more powerful and forgiving in mapping. e.g., morphia can map non-String keyed Maps as fields and I don't think the driver supports. Morphia supports lifecycle events but the driver does not and last I checked it seemed like Morphia's generics support had a slight edge. (Granted that edge is probably an extreme edge case that most won't run in to. It's been a while so the details are fuzzy.)

There are a few other features that Morphia has that the driver doesn't (transparent reference support, e.g.) and some features I have planned that the driver will never support (build-time generated codecs to eliminate most/all reflection at runtime, e.g.).

So do we still need Morphia? It depends on what you want to do. I plan on working on Morphia until no one needs it, though. :)

You should always map your entities as part of initialization. Without that, Morphia won't know what to map that discriminator to.

Morphia does not support that kind of serialization. 1.3.2 is super old so i'm trying to remember the details. I think it can read such values (but that's not a promise) but will write out a List as an array in the documents.

SUGGESTION: focus on your JVM;

• Ensure you have a 64-bit version of Java
• Try tuning your JVM parameters:

https://docs.opsmanager.mongodb.com/current/reference/troubleshooting/system/

1. Open mms.conf in your preferred text editor.

2. Find this line: