Call for participation: Do you want to help fighting COVID-19 using haystack? Support us in the COVID-QA Project
The performance of modern Question Answering Models (BERT, ALBERT ...) has seen drastic improvements within the last year enabling many new opportunities for accessing information more efficiently. However, those models are designed to find answers within rather small text passages. Haystack lets you scale QA models to large collections of documents! While QA is the focussed use case for haystack, we will soon support additional options to boost search (re-ranking, most-similar search, tagging ...).
Haystack is designed in a modular way and lets you use any models trained with FARM or Transformers.
Switching between different backends allows fast prototyping (SQLite) and scalable deployment for production (elasticsearch).
- Powerful models: Utilize all latest transformer based models (BERT, ALBERT roBERTa ...)
- Modular & future-proof: Easily switch to newer models once they get published.
- Developer friendly: Easy to debug, extend and modify.
- Scalable: Production-ready deployments via Elasticsearch backend.
- Customizable: Fine-tune models to your own domain.
- Retriever: Fast, simple algorithm that identifies candidate passages from a large collection of documents. Algorithms include TF-IDF or BM25, which is similar to what's used in Elasticsearch. The Retriever helps to narrow down the scope for Reader to smaller units of text where a given question could be answered.
- Reader: Powerful neural model that reads through texts in detail to find an answer. Use diverse models like BERT, Roberta or XLNet trained via FARM or Transformers on SQuAD like tasks. The Reader takes multiple passages of text as input and returns top-n answers with corresponding confidence scores. You can just load a pretrained model from huggingface's model hub or fine-tune it to your own domain data.
- Finder: Glues together a Reader and a Retriever as a pipeline to provide an easy-to-use question answering interface.
- Labeling Tool: Hosted version (Beta), Docker images (coming soon)
- Tutorial 1 - Basic QA Pipeline: Jupyter notebook or Colab
- Tutorial 2 - Fine-tuning a model on own data: Jupyter notebook or Colab
- Tutorial 3 - Using Elasticsearch as Backend: Jupyter notebook or Colab
There are two ways to install:
- (recommended) from source,
git clone <url>
and runpip install [--editable] .
from the root of the repositry. - from PyPI, do a
pip install farm-haystack
Haystack has an extensible document store layer.
There are currently implementations of Elasticsearch and SQL (see haystack.database.elasticsearch.ElasticsearchDocumentStore
and haystack.database.sql.SQLDocumentStore
).
Elasticsearch is recommended for deploying on a large scale. The documents can optionally be chunked into smaller units (e.g., paragraphs) before indexing to make the results returned by the Retriever more granular and accurate. Retrievers can access an Elasticsearch index to find the relevant paragraphs(or documents) for a query. The default ElasticsearchRetriever uses Elasticsearch's native scoring (BM25), but can be extended easily with custom implementations.
You can get started by running a single Elasticsearch node using docker:
docker run -d -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" elasticsearch:7.5.1
The SQL backend layer is mainly meant to simplify the first development steps. By default, a local file-based SQLite database is initialized. However, if you prefer a PostgreSQL or MySQL backend for production, you can easily configure this since our implementation is based on SQLAlchemy.
A simple REST API based on FastAPI is included to answer questions at inference time. To serve the API, run uvicorn haystack.api.inference:app
.
You will find the Swagger API documentation at http://127.0.0.1:8000/docs
- Use the hosted version (Beta) or deploy it yourself via Docker images (coming soon)
- Create labels with different techniques: Come up with questions (+ answers) while reading passages (SQuAD style) or have a set of predefined questions and look for answers in the document (~ Natural Questions).
- Structure your work via organizations, projects, users
- Upload your documents or import labels from an existing SQuAD-style dataset
- Coming soon: more file formats for document upload, metrics for label quality ...