0 results, test returns "Unexpected SearchResult" error about fulltextsearch

[joshlukas]

Same here. Updated Nextcloud to latest version 27.1.2, ocr search is not available anymore.

sudo -u www-data php /var/www/nextcloud/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. ok
Indexing generated documents. ok
Pausing 3 seconds 1 2 3 ok
Retreiving content from a big index (license). (size: 32386) ok
Comparing document with source. ok
Searching basic keywords:

• 'test' (result: 0, expected: ["simple"]) fail
  Error detected, unlocking process ok
  In Test.php line 676:

Unexpected SearchResult: {"provider":{"id":"test_provider","name":"Test Provider"},"platform":{"id":"elastic_search","name":"Elasticsearch"},"documents":[],"info":[],"meta":{"timedOu
t":false,"time":0,"count":0,"total":0,"maxScore":0}}

fulltextsearch:test [--output [OUTPUT]] [-j|--json] [-d|--platform_delay PLATFORM_DELAY]
`

[Sommerwiesel]

Have probably found a fix for this, the elasticsearch cluster was still running in version 7.11 (older elasticsearch).
You have to either update the cluster via elasticsearch REST API or completely wipe your cluster (i.e. rm -r /var/lib/elasticsearch) after the update to fulltextsearch 27.1.

[lumintulogic-admin]

Same problem here with NC 27.1.2, and Elasticsearch Version: 7.17.14, Build: default/deb/774e3bfa4d52e2834e4d9d8d669d77e4e5c1017f/2023-10-05T22:17:33.780167078Z, JVM: 21

Installing latest elasticsearch doesn't resolve the problem

[Sommerwiesel]

Have probably found a fix for this, the elasticsearch cluster was still running in version 7.11 (older elasticsearch). You have to either update the cluster via elasticsearch REST API or completely wipe your cluster (i.e. rm -r /var/lib/elasticsearch) after the update to fulltextsearch 27.1.

Can confirm that updating or purging the elasticsearch cluster fixes the problem.
Updating elasticsearch from 7.x to 8.x leaves the cluster and fulltextsearch index in 7.x compatibility mode.
For anyone having this bug too, see the elasicsearch wiki on how to perform a cluster update via elasticsearch REST API or simply delete /var/lib/elasticsearch/* and run a full reindex via fulltextsearch:index.
Closed.

@joshlukas
@lumintulogic-admin

[joshlukas]

Can not confirm that. Upgrading or installing to ver. 8 and also purging the index in /var/lib/elasticsearch/ does not change anything. Still not able to search ocr data.

[DecaTec]

I ran into the same problem here. On one cloud instance, I just deleted the index and created a new one, problem solved.

But on another cloud instance, there are 2.5 TB of data and I really don't want to reindex here.
@Sommerwiesel You mentioned that you could also perform a cluster update via API. Do you have a link where this specific endpoint is explained or even an example API call? Searched the ES API but couldn't find anything of value here.