nextcloud / nextcloud/fulltextsearch
Elastic 8.x.x include_type_name error and update of app
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
As indicated here [https://www.elastic.co/guide/en/elasticsearch/reference/7.17/removal-of-types.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/removal-of-types.html) the parameter "include_type_name" is deprecated since Elasticsearch version 7.x and was removed in version 8.x
So in fact, Nextcloud is incompatible with the current version 8.x of Elasticsearch.
What are the plans regarding this issue? Especially, since version 7.x of Elastic was release in April 2019, so the issue is known already quite a while...
Originally posted by @linuzer in https://github.com/nextcloud/fulltextsearch/issues/525#issuecomment-1120422983
Is there something plan to edit this error ?
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 locating the Elasticsearch integration and every use of the include_type_name parameter; compare those calls with Elasticsearch 8 requirements. The issue names no file, entry point, or test, so first identify the relevant code and compatibility coverage. Done means full-text search works with Elasticsearch 8 without using the removed parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, php
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100