MongoRepository | Repository abstraction layer on top | Object-Relational Mapping library

The error was not related to pageable or the query itself. The error was happening because junk at mongodb. There was a property on Foo that some time ago was a String and currently is a boolean, there is a record where this property was saved with the value 'String' and the mongo converter can't convert this value to boolean, and then this error is thrown.

NOT ($ne) operator is suppose to be after field name. so correct syntax will be

With a stroke of dumb luck I managed to figure out the issue. The problem was with the type of identifier annotation I was using. This explanation from another stackoverflow user (What is use of @MongoId in Spring Data MongoDB over @Id?) had me revisit this aspect of the model.

I switched the identifier annotation from @MongoId to @Id. Since I have both JPA and MongoDB annotations I needed to make sure I chose the one from the org.springframework.data.annotation package rather than the javax.persistance package.

Hope this explanation helps others!

The reason why you get null, Mongodb default field of id is _id. And spring data converts id to _id in any classes. When you try to run, you can check the console find using query: { "user._id" : 1} fields: Document{{}}. It mentioned _id there also which is not mapped to database, database has id. (No underscore). To over come this problem ,you can use @Field.

You are misleading the variable name for jpa convention query. Your variable name is type. So your query should be this:

Optional findAnimalByIdAndTypeLike(String id, AnimalType type);

You are misinterpreting the code.

This line defines the primary query getting executed:

According to Officials Docs query method subject keyword in your case should end with 'By' so the method name should be findAllByOrderBySomeFieldDesc()

Spring Data MongoDB is converting fieldNested to field.nested because your InData class & its collection is having fields in that hierarchy. If you want to project that nested field using @Aggregation, then project it using any other name that is not part of your InData class & its collection's fields so Spring Data won't convert it.

Filed injection is not recommended, to avoid this kind of warnings you should give priority to constructor injections, which allows you to build immutable components.

Like this: