ElasticSearch installation help needed

Hello All,
I’ve to solve some ES issues on an existing NEOS 3.3.13 page. To observe the default behavior, I decided to play with a vanilla installation first. What I have done so far:

cloned the Neos base distribution from github

checkedout 3.3.13
composter install, setup Neos.Demo (Database etc)

Neos.Demo Site works as expected

then:

composer require flowpack/elasticsearch
composer require flowpack/elasticsearch-contentrepositoryadaptor
composer require flowpack/searchplugin

Settings.yaml

Neos:
  ContentRepository:
    Search:
      indexAllWorkspaces: false
      elasticSearch:
        indexName: neos3demo

Flowpack:
  ElasticSearch:
    ContentRepositoryAdaptor:
      driver:
        version: 2.x
    clients:
      default:
        - host: localhost
          port: 9200    

I’ve started a elasticsearch 2.6

./flow nodeindex:build

Response body: {
    "error": {
        "root_cause": [
            {
                "type": "mapper_parsing_exception",
                "reason":"analyzer
[autocomplete
                ] not found for field
[__completion
                ]"}],"type":"mapper_parsing_exception","reason":"analyzer
[autocomplete
                ] not found for field [__completion
                ]"},"status":400}

Any hints?

Tom

I’ve found out, that this error comes from defining a new indexName in my root Settings.yaml
Defining this in this style cuts all the ContentRepository settings.
So, its a yaml issue, I’ve to find out, how to overwrite a single property…

that was not the reason :frowning: Using a name which differs from typo3cr causes the error. Maybe creating the index in ES is hardcoded somewhere, I’ll try to create the index maually…

Hey Thomas,

Yeah there has been a hard dependency to the index name in the SearchPlugin configuration. This was removed some time ago but never released.

I’ve just done that:

Please try, if switching to the SearchPlugin version 4 fixes your index issues.

All the best,
Daniel

2 Likes