nextcloud / nextcloud/fulltextsearch
index-reset after nextcloud-upgrade
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
I always need to do occ fulltextsearch:reset after upgrading to a new nextcloud version (this time 13.0.4 to 13.0.5), because just further indexing occ fulltextsearch:index does not index any new files after nextcloud-upgrade. For instances with only few users/files this will not be a problem, but on larger instances it would be nice to keep the index.
Full text search - Elasticsearch Platform (BETA) 0.8.0
Full text search - Files (BETA) 0.8.2
Full text search (BETA) 0.8.1
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 the upgrade from Nextcloud 13.0.4 to 13.0.5 with Full text search components 0.8.0–0.8.2. Compare occ fulltextsearch:index behavior before and after the upgrade; done means new files are indexed without requiring occ fulltextsearch:reset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100