thunderbird / thunderbird/thundermail-deploy

Consider using Elastic/OpenSearch for Stalwart FTS

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Shell
Stars
0
Forks
0
Avg merge
4h 31m
Merged PRs (30d)
26

Description

Stalwart documentation suggests using a dedicated search engine to support its full text search functions. It also suggests that ElasticSearch provides the best performance of the supported options. AWS provides hosted ElasticSearch under the "OpenSearch" banner.

However, we have determined that this is too much lift and complexity for our initial launch, and we will therefore punt on this until a later time. This issue is a placeholder for later discovery and development.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Stalwart storage/search-store documentation linked in the issue and compare the supported dedicated search options, including Elasticsearch/OpenSearch. Define the deployment and configuration scope before implementation; this placeholder names no files, tests, or completion criterion.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch, kubernetes
Domain
infrastructure, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.