nextcloud / nextcloud/fulltextsearch
configure filetypes/paths to ignore
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Hi,
my initial index keeps running into memory errors. Just noticed it always happens on a .m2ts file. This is several GB big and I suspect if fulltextsearch passes it to elasticsearch things go crazy. Moreover indexing videofiles in general might not be a good idea.
How can I tell the plugin or elasticsearch to ignore certain extensions, filesizes or paths?
On another note: Do I need to do anything special to have PDFs,TIFFs etc OCRed besides having tesseract installed?
Regards,
JP
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
No implementation files, tests, or entry points are named in the issue. First clarify whether the scope is configurable extension, size, and path exclusions, OCR behavior, or all of these; then identify the existing indexing configuration and define tests for each supported exclusion and OCR case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100