Skip to content

[8.x] Remove unnecessary interfaces/abstractions from search phases (#120079) #126511

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

Merged
merged 2 commits into from
Apr 9, 2025

Conversation

original-brownbear
Copy link
Member

backport of #120079 and #119272

…c#120079)

A couple obvious cleanups where declared general interfaces aren't actually used
+ we shouldn't escape potentially heavy-weight search phases just to get their name
in a call so adjusted the failure API.
…itions (elastic#119272)

We only need the extensibility for testing and it's a lot easier to
reason about the code if we have explicit methods instead of overly
complicated composition with lots of redundant references being retained
all over the place.

-> lets simplify to inheritance and get shorter code that performs more
predictably (especially when it comes to memory) as a first step.
This also opens up the possibility of further simplifications and
removing more retained state/memory as we go through the search phases.
@original-brownbear original-brownbear added the :Search Foundations/Search Catch all for Search Foundations label Apr 9, 2025
@original-brownbear original-brownbear merged commit 4c28581 into elastic:8.x Apr 9, 2025
2 of 4 checks passed
@original-brownbear original-brownbear deleted the 119272-8.x branch April 9, 2025 08:35
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.

2 participants