illegal_argument_exception while starting a new index

Hi daita,

today I wanted to add a new instance of nextcloud (16.0.1) with Fulltextsearch (1.3.4), Fulltextsearch-Elasticsearch (1.3.3), Fulltextsearch-Files (1.3.2) on my ElasticSearch 6.2.4-Server (with ingest-attachment an readonlyrest 1.18).

Starting with ./occ fulltextsearch:test gives

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

{"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"request [/cloud_index] contains unrecognized parameter: [include_type_name]"}],"type":"illegal_argument_exception","reason":"request [/cloud_index] contain
s unrecognized parameter: [include_type_name]"},"status":400}

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

Starting with ./occ fulltextsearch:index (after ./occ fulltextsearch:reset) and building an elasticsearch index by hand with

curl --noproxy -XPOST "http://cloud_user:password@1.2.3.4:9200/cloud_index/type" -H "Content-Type: application/json" -d "{ "field" : "value"}"

{"_index":"cloud_index","_type":"type","_id":"O-zMrGsBbpR17RLI-dox","_version":1,"result":"created","_shards":{"total":2,"successful":1,"failed":0},"_seq_no":0,"_primary_term":1}

and

curl -H'Content-Type: application/json' -XPUT 'http://cloud_user:password@1.2.3.4:9200/cloud_index/_settings' -d '
{
"index.mapping.total_fields.limit": 10000
}'

{"acknowledged":true}

gives the following error for every file:

┌─ Errors ────
│ Error: 112/112
│ Index: files:10780
│ Exception: Elasticsearch\Common\Exceptions\BadRequest400Exception
│ Message: Rejecting mapping update to [cloud_index] as the final mapping would have more than 1 type: [standard, type]
│
│
└──

│ Exception: Elasticsearch\Common\Exceptions\BadRequest400Exception
│ Message: pipeline with id [attachment] does not exist

Do You have an idea, where to start debugging?

I did not want to stop/reset/restart the other indeces for tests, because the ./occ fulltextsearch:live is still running in the screen-sessions of these instances.

Thanks in advance!

Start by reproducing the failure with ./occ fulltextsearch:test against the reported Elasticsearch 6.2.4 setup, then compare it with ./occ fulltextsearch:index after a reset. Investigate the reported include_type_name, multiple mapping types, and missing attachment pipeline errors; done means index initialization and file indexing complete without these errors.