nextcloud / nextcloud/fulltextsearch
Error when initializing index : "pipeline with id [attachment] does not exist"
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Error description
When setting up FullTextSearch on a test installation, with this command ./occ fulltextsearch:index I have the following error coming:
┌─ Errors ────
│ Error: 16/16
│ Index: files:13
│ Exception: Elasticsearch\Common\Exceptions\BadRequest400Exception
│ Message: pipeline with id [attachment] does not exist
│
│
└──
This happens when first initializing the index as mentionned here: https://github.com/nextcloud/fulltextsearch/wiki/Commands#fulltextsearchindex
Workaround
I found a workaround reseting the index with ./occ fulltextsearch:reset and restarting the index with ./occ fulltextsearch:index
This is easy to do on a brand new test env with a very few files, but I guess this can be quite problematic for large instance with many files...
Environment details
Docker, NC22, Elastic Search 7.15.1 with ingest attachment plugin in, see Dockerfile below.
FROM docker.elastic.co/elasticsearch/elasticsearch:7.15.1
RUN bin/elasticsearch-plugin install --batch ingest-attachment
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing ./occ fulltextsearch:index with the Elasticsearch 7.15.1 Dockerfile and ingest-attachment plugin configuration shown in the report. Trace the index initialization that produces the missing attachment pipeline error; done means a new index completes without requiring fulltextsearch:reset first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, elasticsearch
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100