nextcloud / nextcloud/fulltextsearch
elasticsearch add indexing offsets option
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Hello,
my elasticsearch is posting warning into the logfile about a upcoming change in elasticsearch.
elasticsearch | 2018-02-28T14:56:06.851743014Z [2018-02-28T14:56:06,851][WARN ][d.o.a.l.s.u.CustomUnifiedHighlighter] The length of text to be analyzed for highlighting [114528] exceeded the allowed maximum of [10000] set for the next major Elastic version. For large texts, indexing with offsets or term vectors is recommended!
I found this post https://github.com/elastic/elasticsearch/issues/28830 referring to this document https://www.elastic.co/guide/en/elasticsearch/reference/current/index-options.html
When I unterstand the option correctly the offsets option need to be set in the fulltextsearch plugin when indexing the data right?
Maybe you could add this as an feature.
Thank you in advance.
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 fulltextsearch plugin's Elasticsearch indexing path and compare its mappings with Elasticsearch's index-options documentation. Determine where indexing offsets or term vectors would be configured, then verify that large-text highlighting no longer produces the reported warning. The issue names no files or tests, so locating the entry point requires repository exploration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, php
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100