9 Commits (f1313339ac6f45bcf0afcf572d372c7e3660c0af)

Author	SHA1	Message	Date
Ash Vardanian	d01bad5169	core[patch]: Convert SimSIMD back to NumPy (#19473) ... This patch fixes the #18022 issue, converting the SimSIMD internal zero-copy outputs to NumPy. I've also noticed, that oftentimes `dtype=np.float32` conversion is used before passing to SimSIMD. Which numeric types do LangChain users generally care about? We support `float64`, `float32`, `float16`, and `int8` for cosine distances and `float16` seems reasonable for practically any kind of embeddings and any modern piece of hardware, so we can change that part as well 🤗	6 months ago
Max Jakob	6f544a6a25	elasticsearch: check for deployed models (#18973) ... When creating a new index, if we use a retrieval strategy that expects a model to be deployed in Elasticsearch, check if a model with this name is indeed deployed before creating an index. This lowers the probability to get into a state in which an index was created with a faulty model ID, which cannot be overwritten any more (the index has to manually be deleted).	6 months ago
Erick Friis	a29e8d8594	elasticsearch[patch]: fix integration tests for release (#18980)	6 months ago
Erick Friis	0d1f6c417c	elasticsearch[patch]: release 0.1.1 (#18978)	6 months ago
Max Jakob	911ccf9aa6	docs: elasticsearch retriever (#18965) ... Add documentation notebook for `ElasticsearchRetriever`. ## Dependencies - [ ] Release new `langchain-elasticsearch` version 0.2.0 that includes `ElasticsearchRetriever`	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.	6 months ago
Max Jakob	ee7a7954b9	elasticsearch: add `ElasticsearchRetriever` (#18587) ... Implement [Retriever](https://python.langchain.com/docs/modules/data_connection/retrievers/) interface for Elasticsearch. I opted to only expose the `body`, which gives you full flexibility, and none the other 68 arguments of the [search method](https://elasticsearch-py.readthedocs.io/en/v8.12.1/api/elasticsearch.html#elasticsearch.Elasticsearch.search). Added a user agent header for usage tracking in Elastic Cloud. --------- Co-authored-by: Erick Friis <erick@langchain.dev>	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