Skip to content
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

Enforce execution of field update operations is in alphabetic order #164

Closed
tatu-at-datastax opened this issue Feb 21, 2023 · 0 comments · Fixed by #221
Closed

Enforce execution of field update operations is in alphabetic order #164

tatu-at-datastax opened this issue Feb 21, 2023 · 0 comments · Fixed by #221
Assignees

Comments

@tatu-at-datastax
Copy link
Contributor

tatu-at-datastax commented Feb 21, 2023

(from #132)

Currently update operations on fields are executed in the order specified by input document, so for example:

{"$set": {"foo" : 1, "bar" : 2}}

would first set value of "foo" and then "bar". Specification mandates ordering to be the opposite.
The most obvious change resulting from this is that in case of adding (setting) new properties, insertion order is changed; for most other aspects it should not significantly change behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant