Closed prashantcodecraft closed 1 year ago
Should be doable in next micronaut-data patch release
Thank you 👍 💯
@radovanradic : I am trying to upgrade my micronaut application from 3.9.4 to 4.x due to above issue, but facing another issue : https://github.com/micronaut-projects/micronaut-maven-plugin/issues/805 . Can you please suggest what wrong with this ?
Sorry, not very familiar with that but I believe team working on it will handle it.
@radovanradic : It looks the fix for like query is in master and not in 4.0.2 . So probably will be coming in 4.0.3.
Right, the fix is not released yet and should be in 4.0.3.
@radovanradic : Is there any possibility to add this fix to Micronaut 3.10.x /3.9.x version ? basically we are still at 3.9.4 and upgrading to 4.0.x is giving us issue mainly around build custom AWS labda, hence to keep us going this would help.
Expected Behavior
As per documented on : micronaut pages , I have created an implementation of PredicateSpecification. The purpose of the implementation is to add criteria to query dynamically.
I expect the query to work like contain, just the way it works if I use direct JPA query.
Actual Behaviour
Mongo throws an error :
The query generated is have following :
Where as I want it to be
Steps To Reproduce
Environment Information
Example Application
No response
Version
3.9.4