This repository hosts the code for two self-install re-rankers that integrate into Search Pipelines. User documentation for the Personalize Reranker is here. For Kendra, it is here.
The current guideline for developing processors is that if you are developing a processor that would introduce new dependencies in OpenSearch Core (e.g. new libraries, makes a network connection outside of OpenSearch), it should be in a separate repository. Please consider creating it in a standalone repository since each processor should be thought of like a *NIX command with input and output connected by pipes (i.e. a Search Pipeline). Each processor should do one thing and do it well. Otherwise, it could go into the OpenSearch repository under org.opensearch.search.pipeline.common. If you have doubts, just create an issue in OpenSearch Core and, if you have one, a new PR. Maintainers will help guide you.
This repository has also been used for discussion and ideas around search relevance. These discussions still exist here, however due to the relatively new standard of having one repo per plugin in OpenSearch and our implementations beginning to make it into the OpenSearch build, we have two repositories now. This repository will develop into a plugin that will allow OpenSearch users to rewrite search queries, rerank results, and log data about those actions. The other repository, dashboards-search-relevance, is where we will build front-end tooling to help relevance engineers and business users tune results.
- OpenSearch Project Website
- Downloads
- Project Principles
- Search Pipelines
- Contributing to OpenSearch Search Request Processor
- Search Relevance
- Maintainer Responsibilities
- Release Management
- Admin Responsibilities
- Security
This project has adopted the Amazon Open Source Code of Conduct. For more information see the Code of Conduct FAQ, or contact [email protected] with any additional questions or comments.
This project is licensed under the Apache v2.0 License.
Copyright OpenSearch Contributors. See NOTICE for details.