Revert "Push back excessive requests for stats" (#83832) from 8.2 #85504
Conversation
This file contains 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
This reverts commit ed0bb2a.
joegallo
added
>non-issue
:Data Management/Stats
elasticmachine
added
the
Team:Data Management
|
Pinging @elastic/es-data-management (Team:Data Management) |
original-brownbear
approved these changes
Mar 30, 2022
|
Yeah, there was a trivial conflict that I resolved but besides that it's a straight revert. |
dakrone
approved these changes
Mar 30, 2022
There was a problem hiding this comment.
Assuming this is a straight revert like Armin said, this LGTM; but can you please change the title to have some keywords for what this is actually reverting (not just an issue number) as like 90% of my memory is based on title-matching things in my browser history? :D
joegallo
changed the title
This was referenced Mar 31, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Due to #85333, we want to have a little longer to figure out how to address #51992 -- for the moment, that looks like reverting #83832 from 8.2 so that we have another release cycle to figure out what changes (if any) to make to #83832 in order to address the issues raised on #85333.
Once this is merged, I'll update the version tag on #83832 to 8.3.0 rather than 8.2.0