nextcloud / nextcloud/fulltextsearch
Indexing does not stop - documents are indexed several times
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Hi Folks
I have a large collection (~5000 PDF) of documents (mostly scans) and startet a reindex some weeks ago. Its still not finished and a check in the logs reveals that most of the documents got indexed several times, one "round" of indexing takes about 2 weeks, which seems to be OK for this amount of data and OCR. But after that the whole process is repeatet.
Is there any way to cleanup this?
I've some SQL knowlege and I discovered some tables related to fulltext search in the DB, It is worth a try emptying all these tables?
Or is there any "job" table with the reindex command which needs a cleanup as well?
I'm using Nextcloud 24.0.7 and the newest fulltextsearch apps with elasticcloud and OCR etc.
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 with the indexing logs and inspect the full-text search tables and any job table related to the reindex command. Confirm why the same documents are scheduled repeatedly and identify the cleanup or state change needed so a reindex completes once; the issue is done when repeat indexing is prevented and the cleanup path is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- databases, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100