-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Fix ShardFollowNodeTask.Status equals and hash code #33189
Fix ShardFollowNodeTask.Status equals and hash code #33189
Conversation
These were broken when fetch exceptions were introduced to the status object but equals and hash code were not updated then. This commit addresses that.
Pinging @elastic/es-distributed |
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.
LGTM.
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.
LGTM
* ccr: Only fetch mapping updates when necessary (elastic#33182)
@dnhatn @martijnvg This ended up being a little sneakier because |
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.
That is sneaky indeed. LGTM
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.
LGTM.
* ccr: Fix ShardFollowNodeTask.Status equals and hash code (elastic#33189) Make soft-deletes settings final (elastic#33172) Only fetch mapping updates when necessary (elastic#33182)
These were broken when fetch exceptions were introduced to the status object but equals and hash code were not updated then. This commit addresses that.
These were broken when fetch exceptions were introduced to the status object but equals and hash code were not updated then. This commit addresses that.