2020-06-14 20:53:20 +00:00
|
|
|
---
|
|
|
|
|
layout: docs
|
|
|
|
|
title: Fulltext Search Engine
|
2020-06-28 21:57:27 +00:00
|
|
|
permalink: dev/adr/0014_fulltext_search_engine
|
2020-06-14 20:53:20 +00:00
|
|
|
---
|
|
|
|
|
|
2020-06-28 21:57:27 +00:00
|
|
|
# {{ page.title }}
|
2020-06-14 20:53:20 +00:00
|
|
|
|
|
|
|
|
It should be possible to search the contents of all documents.
|
|
|
|
|
|
|
|
|
|
## Context and Problem Statement
|
|
|
|
|
|
|
|
|
|
To allow searching the documents contents efficiently, a separate
|
|
|
|
|
index is necessary. The "defacto standard" for fulltext search on the
|
|
|
|
|
JVM is something backed by [Lucene](https://lucene.apache.org).
|
|
|
|
|
Another option is to use a RDBMS that supports fulltext search.
|
|
|
|
|
|
|
|
|
|
This adds another component to the mix, which increases the complexity
|
|
|
|
|
of the setup and the software. Since docspell works great without this
|
|
|
|
|
feature, it shouldn't have a huge impact on the application, i.e. if
|
|
|
|
|
the fulltext search component is down or broken, docspell should still
|
|
|
|
|
work (just the fulltext search is then not working).
|
|
|
|
|
|
|
|
|
|
## Considered Options
|
|
|
|
|
|
|
|
|
|
* [Apache SOLR](https://lucene.apache.org/solr)
|
|
|
|
|
* [ElasticSearch](https://www.elastic.co/elasticsearch/)
|
|
|
|
|
* [PostgreSQL](https://www.postgresql.org/docs/12/textsearch.html)
|
|
|
|
|
* All of them or a subset
|
|
|
|
|
|
|
|
|
|
## Decision Outcome
|
|
|
|
|
|
2020-06-23 21:02:58 +00:00
|
|
|
If docspell is running on PostgreSQL, it would be nice to also use it
|
|
|
|
|
for fulltext search to save the cost of running another component. But
|
|
|
|
|
I don't want to lock the database to PostgreSQL *only* because of the
|
|
|
|
|
fulltext search feature.
|
2020-06-14 20:53:20 +00:00
|
|
|
|
|
|
|
|
ElasticSearch and Apache SOLR are quite similiar in features. SOLR is
|
|
|
|
|
part of Lucene and therefore lives in the Apache ecosystem. I would
|
2020-06-23 21:02:58 +00:00
|
|
|
choose SOLR over ElasticSearch, because I used it before.
|
2020-06-14 20:53:20 +00:00
|
|
|
|
|
|
|
|
The last option (supporting all) is interesting, since it would enable
|
2020-06-23 21:02:58 +00:00
|
|
|
to use PostgreSQL for fulltext search for those that use PostgreSQL as
|
|
|
|
|
the database for docspell.
|
|
|
|
|
|
|
|
|
|
In a first step, identify what docspell needs from a fulltext search
|
|
|
|
|
component and create this interface and an implementation for Apache
|
|
|
|
|
SOLR. This enables all users to use the fulltext search feature. As a
|
|
|
|
|
later step, an implementation based on PostgreSQL and/or ElasticSearch
|
|
|
|
|
could be provided, too.
|
