nextcloud / nextcloud/fulltextsearch
Cant index using elasticsearch 8
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Failed to index after upgrade to elastic 8.1.0, reverted to 7.17.1 work again.
Unrecognized parameter, something depreceated?
debian@b06dd1767b73:/var/www/html$ ./occ fulltextsearch:test
.Testing your current setup:
Creating mocked content provider. ok
Testing mocked provider: get indexable documents. (2 items) ok
Loading search platform. (Elasticsearch) ok
Testing search platform. ok
Locking process ok
Removing test. ok
Pausing 3 seconds 1 2 3 ok
Initializing index mapping. fail
Error detected, unlocking process ok
In Connection.php line 693:
{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"request [/nextcloudfts] contains unrecognized parameter: [include_type_name]"}],"type":"illegal_argument_exception","reason":"request [/nextcloudfts] contains
unrecognized parameter: [include_type_name]"},"status":400}
fulltextsearch:test [--output [OUTPUT]] [-j|--json] [-d|--platform_delay PLATFORM_DELAY]
confirmed, deprecated
https://www.elastic.co/guide/en/elasticsearch/reference/master/migrating-8.0.html
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 running ./occ fulltextsearch:test against Elasticsearch 8.1.0 and follow the failure during index mapping initialization. Inspect the code responsible for that mapping request, focusing on the reported include_type_name parameter; done means the setup test succeeds with Elasticsearch 8 while preserving the supported behavior indicated by the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, php
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100