Bump TransportVersion to first non-Version constant #95286
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
…ynamically computing it
| Hi @thecoop, I've created a changelog YAML for you. |
| Pinging @elastic/es-core-infra (Team:Core/Infra) |
thecoop changed the title 
| @elasticsearchmachine rerun elasticsearch-ci/part-3 |
| @elasticmachine update branch |
| @elasticsearchmachine rerun elasticsearch-ci/part-3 |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Use first non-Version TransportVersion CURRENT constant. It needs to be one that is still accepted by 7.17 clusters (so <9,000,000).
Once this is merged, the new procedures for managing transport versions are in effect. A new TransportVersion constant needs to be defined for every separate serialization change within ES.