-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[Rest Api Compatibility] _time and _term sort orders #74919
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
[Rest Api Compatibility] _time and _term sort orders #74919
Conversation
Previously removed in elastic#39450, deprecated in es6 but not removed in es 7. defaults to _key behaviour relates elastic#51816
|
Pinging @elastic/es-analytics-geo (Team:Analytics) |
|
removal of _time and _term was marked as |
Do you mean you'd prefer to just merge this to master, no backports? In other words, this removal gets a super long deprecation cycle? That's fine with me. I don't think it's hurting anyone. |
yes, there is a chance to make it easier for users to upgrade, so why not :) |
|
Yeah - I'm 👍 to do it the way you've proposed. Do we have a way of knowing when to drop support for it? I guess at some point we'll remove the constant you are comparing to and just zap all of the statements it guards. |
|
when we bump RestApiVersion.minimumSupported to 8 (current version would be 9) then the code https://github.com/elastic/elasticsearch/pull/74919/files#diff-ab996c9a4e31c3c2e1c2df8238d258c0217fecc258066faa02e0c7a5701255afR578 will become dead. |
That's awesome! I that we can remove the dead code in as many changes as we need after dropping the support. |
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Previously removed in #39450, deprecated in es6 but not removed in es 7.
defaults to _key behaviour
relates #51816
gradle check?