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

Fix ShardFollowNodeTask.Status equals and hash code #33189

Merged
merged 4 commits into from
Aug 28, 2018

Conversation

jasontedor
Copy link
Member

@jasontedor jasontedor commented Aug 28, 2018

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.
@jasontedor jasontedor added >non-issue :Distributed Indexing/CCR Issues around the Cross Cluster State Replication features labels Aug 28, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@jasontedor jasontedor requested review from martijnvg and dnhatn August 28, 2018 01:17
Copy link
Member

@dnhatn dnhatn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Copy link
Member

@martijnvg martijnvg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jasontedor
Copy link
Member Author

@dnhatn @martijnvg This ended up being a little sneakier because ElasticsearchException does not implement equals and hashCode. This led to a test failure in ShardFollowNodeTaskStatusTests. I pushed an iteration. Would you take another look?

@jasontedor jasontedor requested review from martijnvg and dnhatn August 28, 2018 10:36
Copy link
Member

@martijnvg martijnvg left a 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

Copy link
Member

@dnhatn dnhatn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@jasontedor jasontedor merged commit 5954354 into elastic:ccr Aug 28, 2018
jasontedor added a commit to martijnvg/elasticsearch that referenced this pull request Aug 28, 2018
* 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)
jasontedor added a commit that referenced this pull request Aug 28, 2018
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.
@jasontedor jasontedor deleted the fix-status-equals-hash-code branch August 28, 2018 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Indexing/CCR Issues around the Cross Cluster State Replication features >non-issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants