fulltextsearch icon indicating copy to clipboard operation
fulltextsearch copied to clipboard

Tokenizer failure on Connection.php while running Elasticsearch 6.7.1

Open daveonkels opened this issue 5 years ago • 8 comments

I've read through the related Connections.php issues but am not running version 7+ Elasticsearch. After retracing my steps, I've noticed that if the "Fullsearch Files" plugin is disabled, the error is not thrown, however, there is still no index being generated in either case. Any thoughts?

In Connection.php line 615:

{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Custom Analyzer [analyzer] failed to find tokenizer under name []"}],"type":"illegal_argument_exception","reason":"Custom Analyzer [analyzer] failed to find tokenizer under name []"},"status":400}

{ "name" : "rubber", "cluster_name" : "elasticgirl", "cluster_uuid" : "HlEvorBoQu6gE79LU9Q9Mg", "version" : { "number" : "6.7.1", "build_flavor" : "default", "build_type" : "deb", "build_hash" : "2f32220", "build_date" : "2019-04-02T15:59:27.961366Z", "build_snapshot" : false, "lucene_version" : "7.7.0", "minimum_wire_compatibility_version" : "5.6.0", "minimum_index_compatibility_version" : "5.0.0" }, "tagline" : "You Know, for Search" }

Screen Shot 2019-04-21 at 8 16 58 AM Screen Shot 2019-04-21 at 8 26 57 AM

daveonkels avatar Apr 21 '19 15:04 daveonkels

please paste result of

./occ fulltextsearch:reset
./occ fulltextsearch:test

ArtificialOwl avatar Apr 24 '19 10:04 ArtificialOwl

You bet, here's the result:

.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 615:

{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Custom Analyzer [analyzer] failed to find tokenizer under na
me []"}],"type":"illegal_argument_exception","reason":"Custom Analyzer [analyzer] failed to find tokenizer under name []"},"status"
:400}

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

Screen Shot 2019-04-24 at 6 42 27 PM

daveonkels avatar Apr 25 '19 01:04 daveonkels

Hello,

have the same issue.

local installed elasticsearch 7.0.0 and readonlyrest 7.0.0

`.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 615:

{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Custom Analyzer [analyzer] failed to find tokenizer under name []"}],"type":"illegal_argument_exception","reason":" Custom Analyzer [analyzer] failed to find tokenizer under name []"},"status":400}

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

Happyfeet01 avatar Apr 28 '19 10:04 Happyfeet01

please use elasticsearch 6.x, as the app is not (yet) compatible with ES 7.x

ArtificialOwl avatar May 02 '19 10:05 ArtificialOwl

@daveonkels strange, can you confirm you ran the reset command before the test ?

ArtificialOwl avatar May 02 '19 10:05 ArtificialOwl

same issue here with ES 6.8.4. Any solution?

spaceduck518 avatar Nov 19 '19 17:11 spaceduck518

ES and

same issue here with ES 6.8.4. Any solution?

Be sure that elasticsearch and readonlyrest have the same Version.

Happyfeet01 avatar Nov 19 '19 18:11 Happyfeet01

No updates?

Happyfeet01 avatar Nov 07 '21 16:11 Happyfeet01