Repository navigation
Add search pipelines - #145
Open
esmarkowski wants to merge 2 commits into
Open
esmarkowski wants to merge 2 commits into
esmarkowski wants to merge 2 commits into
Conversation
Stretchy::IngestPipeline replaces Stretchy::Pipeline, and Stretchy::SearchPipeline adds request, response and phase results processors managed through PUT /_search/pipeline/<name>. Both share Pipelines::Base and Pipelines::Processor, whose model: option now accepts a model class, class name or id. Stretchy::Pipeline still works as a deprecated subclass of IngestPipeline, warning through Stretchy.deprecator until 0.8. The pipeline rake tasks manage both kinds, skipping search pipelines on Elasticsearch, and select one with PIPELINE instead of MODEL. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`default_search_pipeline :rag_pipeline` sets index.search.default_pipeline in the index settings, and `Post.search_pipeline(:rag_pipeline)` sends the search_pipeline request parameter for one query. Both accept a SearchPipeline class, its class name or a pipeline name. routing and search_pipeline share one definition for single value search options. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or 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
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.
Ingest and search pipelines are now separate classes that share one base and one processor DSL. Models can set a default search pipeline, and a relation can choose a pipeline for a single query.
SearchPipeline.create!issuesPUT /_search/pipeline/<name>.PIPELINEinstead ofMODEL.model:option accepts a model class, a class name or a model id.Stretchy::Pipelinestill works as a deprecated subclass ofStretchy::IngestPipeline. It warns throughStretchy.deprecatoruntil 0.8.Verified against OpenSearch 3.9.0:
filter_querydefault search pipeline filtered results.search_pipelineoverrode the default.Specs pass on OpenSearch 3.9.0, OpenSearch 2.19.7 and Elasticsearch 8.12.2.
Closes #138