nextcloud / nextcloud/files_fulltextsearch
Disable indexing for subtree
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 72
- Forks
- 41
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 9
Description
I have a cloud that shares a large music folder using external mount to a complete group. In the past, I was able to exclude this folder from the indexing by creating a .noindex file accordingly. This feature seems to be gone in the meantime.
The problem is that the indexing of the complete music archive (>300GB, >50,000 files, counting is just running) multiplied by the number of users having access to the external storage results in such a huge number of files that indexing takes days to weeks. Currently, the index is somehow broken. I try to figure out what the problem is but I cannot get it as each testing iteration takes so incredibly long.
Was there a 9good) reason for removing this very handy feature?
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 lib/Service/FilesService.php around the linked .noindex handling and review the surrounding indexing flow. Determine how subtree exclusions currently work for externally mounted storage and define completion as preventing indexing of a marked subtree without affecting other files; the issue mentions no test file to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100