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
detect_noop
now understands null
as a valid value
#11210
Conversation
modified = true; | ||
continue; | ||
} | ||
modified = !old.equals(changesEntry.getValue()); | ||
modified = old == null ? changesEntry.getValue() != null : !old.equals(changesEntry.getValue()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe this could be simplified to modified = !java.util.Objects.equal(old, changesEntry.getValue())
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. I forget about that one.
This looks good to me, I'll merge it tomorrow if nobody else has objections. |
Updated based on your comment. I can squash the changes if you want. |
That would be great. :-) |
If the source contrains a null value for a field then detect_noop should consider setting it to null again to be a noop. Closes elastic#11208
Squashed. |
detect_noop now understands null as a valid value
detect_noop
now understands null
as a valid value
If the source contrains a null value for a field then detect_noop should
consider setting it to null again to be a noop.
Closes #11208