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 an issue where ConfigBlocksEqual was returning false #10587

Merged
merged 2 commits into from
Feb 6, 2019

Conversation

ph
Copy link
Contributor

@ph ph commented Feb 5, 2019

The ordering was not preserved when comparing the values for conflict
blocks which result in multiple reload on each fetch even if the
configuration didn't change.

@ph ph requested a review from urso February 5, 2019 21:06
@ph ph added the needs_backport PR is waiting to be backported to other branches. label Feb 5, 2019
ph added 2 commits February 5, 2019 16:33
The ordering was not preserved when comparing the values for conflict
blocks which result in multiple reload on each fetch even if the
configuration didn't change.
@ph ph force-pushed the fix/configuration-equals branch from 05c65b9 to 6c96763 Compare February 5, 2019 21:34
@ph
Copy link
Contributor Author

ph commented Feb 5, 2019

rebase because of #10582

@ph ph merged commit 20809e1 into elastic:master Feb 6, 2019
ph added a commit to ph/beats that referenced this pull request Feb 6, 2019
* Fix an issue where ConfigBlocksEqual was returning false

The ordering was not preserved when comparing the values for conflict
blocks which result in multiple reload on each fetch even if the
configuration didn't change.

(cherry picked from commit 20809e1)
@ph ph added v6.7.0 and removed needs_backport PR is waiting to be backported to other branches. labels Feb 6, 2019
urso pushed a commit to urso/beats that referenced this pull request Feb 6, 2019
* Fix an issue where ConfigBlocksEqual was returning false

The ordering was not preserved when comparing the values for conflict
blocks which result in multiple reload on each fetch even if the
configuration didn't change.

(cherry picked from commit 20809e1)
urso pushed a commit that referenced this pull request Feb 6, 2019
…0617)

* Fix an issue where ConfigBlocksEqual was returning false

The ordering was not preserved when comparing the values for conflict
blocks which result in multiple reload on each fetch even if the
configuration didn't change.

(cherry picked from commit 20809e1)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants