4 Commits (e980c14d6a22f41b31d5d7153a3a598148a120de)

Author	SHA1	Message	Date
Erick Friis	0d1f6c417c	elasticsearch[patch]: release 0.1.1 (#18978)	6 months ago
Max Jakob	61a2eba081	elasticsearch[patch]: add top-level import, remove obsolete dependency (#18644) ... Make `ElasticsearchRetriever` available as top-level import. The `langchain` package depends on `langchain-community` so we do not need to depend on it explicitly.	7 months ago
Max Jakob	81e9ab6e3a	docs: Update elasticsearch README (#18497) ... Update Elasticsearch README with information on how to start a deployment. Also make some cosmetic changes to the [Elasticsearch docs](https://python.langchain.com/docs/integrations/vectorstores/elasticsearch). Follow up on https://github.com/langchain-ai/langchain/pull/17467	7 months ago
Max Jakob	5ab69f907f	partners: add Elasticsearch package (#17467) ... ### Description This PR moves the Elasticsearch classes to a partners package. Note that we will not move (and later remove) `ElasticKnnSearch`. It were previously deprecated. `ElasticVectorSearch` is going to stay in the community package since it is used quite a lot still. Also note that I left the `ElasticsearchTranslator` for self query untouched because it resides in main `langchain` package. ### Dependencies There will be another PR that updates the notebooks (potentially pulling them into the partners package) and templates and removes the classes from the community package, see https://github.com/langchain-ai/langchain/pull/17468 #### Open question How to make the transition smooth for users? Do we move the import aliases and require people to install `langchain-elasticsearch`? Or do we remove the import aliases from the `langchain` package all together? What has worked well for other partner packages? --------- Co-authored-by: Erick Friis <erick@langchain.dev>	7 months ago