-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Revert "Add ResolvedExpression wrapper (#114592)" #115317
Revert "Add ResolvedExpression wrapper (#114592)" #115317
Conversation
This reverts commit 4c15cc0.
Pinging @elastic/es-data-management (Team:Data Management) |
Hi @original-brownbear, I've created a changelog YAML for you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Mary said she would look into this tomorrow also.
Thanks Lee! |
💚 Backport successful
|
) This reverts commit 4c15cc0. This commit introduced an orders of magnitude regression when searching many shards.
@original-brownbear this needs to go to 8.17 (the 8.x branch) also |
Ah right thanks! |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
It appears that adding the |
Thanks again Lee! |
) This reverts commit 4c15cc0. This commit introduced an orders of magnitude regression when searching many shards.
) This reverts commit 4c15cc0. This commit introduced an orders of magnitude regression when searching many shards.
**Introduction** > In order to make adoption of failure stores simpler for all users, we are introducing a new syntactical feature to index expression resolution: The selector. > > Selectors, denoted with a :: followed by a recognized suffix will allow users to specify which component of an index abstraction they would like to operate on within an API call. In this case, an index abstraction is a concrete index, data stream, or alias; Any abstraction that can be resolved to a set of indices/shards. We define a component of an index abstraction to be some searchable unit of the index abstraction. > > To start, we will support two components: data and failures. Concrete indices are their own data components, while the data component for index aliases are all of the indices contained therein. For data streams, the data component corresponds to their backing indices. Data stream aliases mirror this, treating all backing indices of the data streams they correspond to as their data component. > > The failure component is only supported by data streams and data stream aliases. The failure component of these abstractions refer to the data streams' failure stores. Indices and index aliases do not have a failure component. For more details and examples see elastic#113144. All this work has been cherry picked from there. **Purpose of this PR** This PR is introducing a wrapper around the resolved expression that used to be a `String` to create the base on which the selectors are going to be added. The current PR is just a refactoring and does not and should not change any existing behaviour.
This reverts commit 4c15cc0.
This commit introduced an orders of magnitude regression when searching many shards.
Small Rally excerpt: