Skip to content

Conversation

@original-brownbear
Copy link
Contributor

* We should compare the target value with the to be applied value before interpreting the update as a change
* This speeds up the test failing in elastic#36496 considerably by preventing state updates on noop setting updates
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@original-brownbear
Copy link
Contributor Author

@elasticmachine retest this please

Copy link
Member

@danielmitterdorfer danielmitterdorfer left a comment

Choose a reason for hiding this comment

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

LGTM

@original-brownbear
Copy link
Contributor Author

@danielmitterdorfer thanks!

@original-brownbear original-brownbear merged commit 34d7cc1 into elastic:master Dec 13, 2018
@original-brownbear original-brownbear deleted the faster-settings-update branch December 13, 2018 09:02
original-brownbear added a commit that referenced this pull request Dec 13, 2018
* We should compare the target value with the to be applied value before interpreting the update as a change
* This speeds up the test failing in #36496 considerably by preventing state updates on noop setting updates
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants