Skip to content

Conversation

@williamrandolph
Copy link
Contributor

This is a small bit of #53637 that will save us some headaches if it sneaks into 7.7 before we cut an official release. It just changes the value of a string constant that is being introduced in 7.7.

As described here, this is not a change to the user-facing value for the adaptive selection metric. It simply changes the internal token so that it matches the adaptive selection metric.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Plugins)

Copy link
Contributor

@bpintea bpintea left a comment

Choose a reason for hiding this comment

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

LGTM

DISCOVERY("discovery"),
INGEST("ingest"),
ADAPTIVE_SELECTION("adaptiveSelection");
ADAPTIVE_SELECTION("adaptive_selection");
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure changing this will work in 7.x, because in mixed cluster, the server/request would not align? Additionally, the transport client would have similar failure scenarios?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My plan is that this PR will change the token in 7.7, which will mean that 7.7.0 and all following 7.7.x releases will have the change. #53637 will make the change in master and the change will come in for 7.x in #54141. Both of those PRs are ready for merge once this issue is resolved. I believe that if we make this change on 7.7, 7.x, and master, then there won't be any releases where the versions won't align. Does that make sense? Am I missing something?

Copy link
Member

Choose a reason for hiding this comment

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

Thanks for the explanation. I just realized where my confusion lies: I was thinking this enum existed and these strings were serialized currently, when in fact the 7.6 and before request is serialized with boolean flags.

@williamrandolph williamrandolph requested a review from rjernst March 26, 2020 17:25
Copy link
Member

@rjernst rjernst left a comment

Choose a reason for hiding this comment

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

LGTM

DISCOVERY("discovery"),
INGEST("ingest"),
ADAPTIVE_SELECTION("adaptiveSelection");
ADAPTIVE_SELECTION("adaptive_selection");
Copy link
Member

Choose a reason for hiding this comment

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

Thanks for the explanation. I just realized where my confusion lies: I was thinking this enum existed and these strings were serialized currently, when in fact the 7.6 and before request is serialized with boolean flags.

@williamrandolph williamrandolph merged commit 3af0e22 into elastic:7.7 Mar 26, 2020
@williamrandolph williamrandolph deleted the backport/7.7/bwc-fix-for-nodes-stats branch May 23, 2022 17:25
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