-
Notifications
You must be signed in to change notification settings - Fork 1.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
[Search Pipelines] Split search pipeline processor factories by type #7597
[Search Pipelines] Split search pipeline processor factories by type #7597
Conversation
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
139e591
to
76e3245
Compare
server/src/main/java/org/opensearch/search/pipeline/SearchPipelineInfo.java
Show resolved
Hide resolved
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
@@ Coverage Diff @@
## main #7597 +/- ##
============================================
+ Coverage 70.80% 70.87% +0.06%
- Complexity 56085 56118 +33
============================================
Files 4676 4676
Lines 265927 265895 -32
Branches 39053 39051 -2
============================================
+ Hits 188292 188446 +154
+ Misses 61678 61474 -204
- Partials 15957 15975 +18
|
Gradle Check (Jenkins) Run Completed with:
|
4a5c9bc
to
63f0fa7
Compare
Gradle Check (Jenkins) Run Completed with:
|
Flaky test: #7592 |
Looking for some feedback on this change. @reta @andrross @navneet1v ? I would like to get it in for 2.8, since it will be much harder to change if/when we release the search pipelines feature more broadly. |
can we have a reviewer in addition to @reta and @andrross take a look at this please? @VachaShah @kartg @saratvemulapalli @tlfeng, perhaps? thanks! |
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.
Pretty straightforward, overall LGTM. Just one Q on thread safety.
server/src/main/java/org/opensearch/search/pipeline/SearchPipelineService.java
Show resolved
Hide resolved
Le sigh.. another unrelated failure. #7592 These "flaky" tests need some attention. They're starting to get unmanageable and gridlock our PRs. |
Gradle Check (Jenkins) Run Completed with:
|
I'm happy to approve w/ the minor changes above. Don't worry about unrelated flaky tests here. We'll fix those separately. |
In the initial search pipelines commit, I threw request and response processor factories into one combined map. I think that was a mistake. We should embrace type-safety by making sure that the kind of processor is clear from end to end. As we add more processor types (e.g. search phase processor), throwing them all in one big map would get messier. As a bonus, we'll be able to reuse processor names across different types of processor. Closes opensearch-project#7576 Signed-off-by: Michael Froh <froh@amazon.com>
Signed-off-by: Michael Froh <froh@amazon.com>
Signed-off-by: Michael Froh <froh@amazon.com>
Thanks @nknize! Signed-off-by: Michael Froh <froh@amazon.com>
63f0fa7
to
faabc42
Compare
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. 🤞🏻 we don't hit flaky test hell...
Gradle Check (Jenkins) Run Completed with:
|
…7597) In the initial search pipelines commit, I threw request and response processor factories into one combined map. I think that was a mistake. We should embrace type-safety by making sure that the kind of processor is clear from end to end. As we add more processor types (e.g. search phase processor), throwing them all in one big map would get messier. As a bonus, we'll be able to reuse processor names across different types of processor. Signed-off-by: Michael Froh <froh@amazon.com> (cherry picked from commit eb51f2b) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…tories by type (#7669) * [Search Pipelines] Split search pipeline processor factories by type (#7597) In the initial search pipelines commit, I threw request and response processor factories into one combined map. I think that was a mistake. We should embrace type-safety by making sure that the kind of processor is clear from end to end. As we add more processor types (e.g. search phase processor), throwing them all in one big map would get messier. As a bonus, we'll be able to reuse processor names across different types of processor. Signed-off-by: Michael Froh <froh@amazon.com> (cherry picked from commit eb51f2b) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> * Update SearchPipelineInfo serialization check to < 2.8 We needed to check for onOrBefore 2.8 in order to pass back-compat tests on main. Now that we're backporting to 2.8, we need to update the check (on 2.x and on main). Signed-off-by: Michael Froh <froh@amazon.com> --------- Signed-off-by: Michael Froh <froh@amazon.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…pensearch-project#7597) In the initial search pipelines commit, I threw request and response processor factories into one combined map. I think that was a mistake. We should embrace type-safety by making sure that the kind of processor is clear from end to end. As we add more processor types (e.g. search phase processor), throwing them all in one big map would get messier. As a bonus, we'll be able to reuse processor names across different types of processor. Signed-off-by: Michael Froh <froh@amazon.com> Signed-off-by: Bharathwaj G <bharath78910@gmail.com>
…pensearch-project#7597) In the initial search pipelines commit, I threw request and response processor factories into one combined map. I think that was a mistake. We should embrace type-safety by making sure that the kind of processor is clear from end to end. As we add more processor types (e.g. search phase processor), throwing them all in one big map would get messier. As a bonus, we'll be able to reuse processor names across different types of processor. Signed-off-by: Michael Froh <froh@amazon.com>
…pensearch-project#7597) In the initial search pipelines commit, I threw request and response processor factories into one combined map. I think that was a mistake. We should embrace type-safety by making sure that the kind of processor is clear from end to end. As we add more processor types (e.g. search phase processor), throwing them all in one big map would get messier. As a bonus, we'll be able to reuse processor names across different types of processor. Signed-off-by: Michael Froh <froh@amazon.com>
…pensearch-project#7597) In the initial search pipelines commit, I threw request and response processor factories into one combined map. I think that was a mistake. We should embrace type-safety by making sure that the kind of processor is clear from end to end. As we add more processor types (e.g. search phase processor), throwing them all in one big map would get messier. As a bonus, we'll be able to reuse processor names across different types of processor. Signed-off-by: Michael Froh <froh@amazon.com> Signed-off-by: Shivansh Arora <hishiv@amazon.com>
Description
In the initial search pipelines commit, I threw request and response processor factories into one combined map. I think that was a mistake.
We should embrace type-safety by making sure that the kind of processor is clear from end to end. As we add more processor types (e.g. search phase processor), throwing them all in one big map would get messier.
As a bonus, we'll be able to reuse processor names across different types of processor.
Related Issues
Resolves #7576
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.