nextcloud / nextcloud/fulltextsearch
indexed content special chars brake searches
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
If the document is indexed newlines are added as \n to elasticsearch content.
Because there is no space after the \n all first words of lines arent searchable.
Same goes for other special chars like \t
curl http://localhost:9200/fulltext_search/files/104?pretty
" authentication\n\n\tManage Connected Browsers"
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
Reproduce the issue with the documented curl request to /fulltext_search/files/104 and inspect the indexed content containing escaped newlines and tabs. Trace how document text is indexed and searched, then verify that words following special characters are searchable without breaking the displayed content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, php
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100