Skip to content

Additional packages (components, document stores and the likes) to extend the capabilities of Haystack

License

NotificationsYou must be signed in to change notification settings

deepset-ai/haystack-core-integrations

Haystack Core Integrations

This repository contains integrations to extend the capabilities of Haystack. The code in this repo is maintained by deepset, see each integration's README file for details around installation, usage and support.

Quick start

You will need hatch to work on or create new integrations, open this link and follow the install instructions for your operating system and platform.

All the integrations are self contained, so the first step before working on one is to cd into the proper folder. For example, to run the tests suite for the Chroma document store, from the root of the repo:

$ cd integrations/chroma
$ hatch run test

Hatch will take care of setting up an isolated Python environment and run the tests.

Please check out our Contribution Guidelines for all the details.

Inventory

License Compliance

PackageTypePyPi PackageStatus
amazon-bedrock-haystackEmbedder, Generator, RankerPyPI - VersionTest / amazon_bedrock
amazon-sagemaker-haystackGeneratorPyPI - VersionTest / amazon_sagemaker
anthropic-haystackGeneratorPyPI - VersionTest / anthropic
astra-haystackDocument StorePyPI - VersionTest / astra
azure-ai-search-haystackDocument StorePyPI - VersionTest / azure-ai-search
chroma-haystackDocument StorePyPI - VersionTest / chroma
cohere-haystackEmbedder, Generator, RankerPyPI - VersionTest / cohere
deepeval-haystackEvaluatorPyPI - VersionTest / deepeval
elasticsearch-haystackDocument StorePyPI - VersionTest / elasticsearch
fastembed-haystackEmbedder, RankerPyPI - VersionTest / fastembed
google-ai-haystackGeneratorPyPI - VersionTest / google-ai
google-vertex-haystackGeneratorPyPI - VersionTest / google-vertex
instructor-embedders-haystackEmbedderPyPI - VersionTest / instructor-embedders
jina-haystackConnector, Embedder, RankerPyPI - VersionTest / jina
langfuse-haystackTracerPyPI - VersionTest / langfuse
llama-cpp-haystackGeneratorPyPI - VersionTest / llama-cpp
mcp-haystackToolPyPI - VersionTest / mcp
mistral-haystackEmbedder, GeneratorPyPI - VersionTest / mistral
mongodb-atlas-haystackDocument StorePyPI - VersionTest / mongodb-atlas
nvidia-haystackEmbedder, Generator, RankerPyPI - VersionTest / nvidia
ollama-haystackEmbedder, GeneratorPyPI - VersionTest / ollama
opensearch-haystackDocument StorePyPI - VersionTest / opensearch
optimum-haystackEmbedderPyPI - VersionTest / optimum
pinecone-haystackDocument StorePyPI - VersionTest / pinecone
pgvector-haystackDocument StorePyPI - VersionTest / pgvector
qdrant-haystackDocument StorePyPI - VersionTest / qdrant
ragas-haystackEvaluatorPyPI - VersionTest / ragas
snowflake-haystackRetrieverPyPI - VersionTest / snowflake
stackit-haystackEmbedder, GeneratorPyPI - VersionTest / stackit
unstructured-fileconverter-haystackFile converterPyPI - VersionTest / unstructured
uptrain-haystackEvaluatorPyPI - VersionStaged
weaviate-haystackDocument StorePyPI - VersionTest / weaviate
weave-haystackTracerPyPI - VersionTest / weights_and_biases_weave

Releasing

Note

Only maintainers can release new versions of integrations. If you're a community contributor and want to release a new version of an integration, reach out to a maintainer.

To release a new version of an integration to PyPI tag the commit with the right version number and push the tag to . The Actions workflow will take care of the rest.

  1. Tag the commit with the right version number

    The tag needs to have the following format:

    git tag integrations/<INTEGRATION_FOLDER_NAME>-<version>
    

    For example, if we want to release version 1.0.99 of the google-vertex-haystack integration we'd have to push the tag:

    git tag integrations/google_vertex-v1.0.99
    
  2. Push the tag to

    git push --tags origin
    
  3. Wait for the CI to do its magic

  4. Review the changelog PR

    If the release is successful, the HaystackBot will open a pull request to generate the changelog. Add yourself as the reviewer. If there are any issues, edit the changelog manually.

Important

To ensure the changelog is accurate, it's recommended to tag a commit that includes the actual changes for the integration (usually the PR merge commit). Tagging a commit that doesn't contain those changes can lead to an incorrect changelog.

About

Additional packages (components, document stores and the likes) to extend the capabilities of Haystack

Topics

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks