-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for the aggregation pipeline updates #4859
Comments
Thanks for getting in touch, but it feels like this is a question that would be better suited to Stack Overflow. We prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug. |
@christophstrobl Thank you for reply! Actually, I'm not asking how I can translate this query to Spring Data MongoDB code, but I just wanted to suggest future improvements if Spring Data MongoDB doesn't support this functionality at the moment. |
Please have a look at the reference documentation for updates using an aggregation pipeline. |
I've actually seen that part of the documentation. According to it, The update in a aggregation pipeline can consist of the following stages: set, unset, replaceWith, but not replaceRoot. So, I'd like to suggest future support for replaceRoot operation in aggregation pipeline updates. Additionally, it doesn't seem like I can specify the filtering condition(it is just |
I'd like to translate following MongoDB query into Spring Data MongoDB(and QueryDSL if needed).
Does Spring Data MongoDB support this kind of query?
I've already asked this on stackoverflow, but I couldn't get any answer.
A format of the
user_history
collection would be like this.The text was updated successfully, but these errors were encountered: