elasticsearch-setup operation is not compatible with es 6.x or 7.x version
See original GitHub issueDescribe the bug
When I start the elasticsearch-setup container, Something is wrong with ES v7.7.1:
{"error":"Content-Type header [application/x-www-form-urlencoded] is not supported","status":406}
When I add the Content-Type
header, The following exception is reported:
dev@docker-build-1:/opt/datahub/docker/elasticsearch$ curl -sS -XPUT 10.191.7.1:9200/corpuserinfodocument -H 'Content-Type: Application/JSON' --data @corpuser-index-config.json | jq .
{
"error": {
"root_cause": [
{
"type": "mapper_parsing_exception",
"reason": "Root mapping definition has unsupported parameters: [doc : {properties={skills={type=text}, urn={normalizer=custom_normalizer, type=keyword}, teams={type=text}, ldap={analyzer=lowercase_keyword, type=text, fields={ngram={analyzer=delimit_edgengram, type=text}}}, managerLdap={analyzer=lowercase_keyword, type=text, fields={ngram={analyzer=delimit_edgengram, type=text}}}, active={type=boolean}, fullName={type=text, fields={ngram={analyzer=delimit_edgengram, type=text}}}, title={normalizer=custom_normalizer, type=keyword}, aboutMe={type=text}}}]"
}
],
"type": "mapper_parsing_exception",
"reason": "Failed to parse mapping [_doc]: Root mapping definition has unsupported parameters: [doc : {properties={skills={type=text}, urn={normalizer=custom_normalizer, type=keyword}, teams={type=text}, ldap={analyzer=lowercase_keyword, type=text, fields={ngram={analyzer=delimit_edgengram, type=text}}}, managerLdap={analyzer=lowercase_keyword, type=text, fields={ngram={analyzer=delimit_edgengram, type=text}}}, active={type=boolean}, fullName={type=text, fields={ngram={analyzer=delimit_edgengram, type=text}}}, title={normalizer=custom_normalizer, type=keyword}, aboutMe={type=text}}}]",
"caused_by": {
"type": "mapper_parsing_exception",
"reason": "Root mapping definition has unsupported parameters: [doc : {properties={skills={type=text}, urn={normalizer=custom_normalizer, type=keyword}, teams={type=text}, ldap={analyzer=lowercase_keyword, type=text, fields={ngram={analyzer=delimit_edgengram, type=text}}}, managerLdap={analyzer=lowercase_keyword, type=text, fields={ngram={analyzer=delimit_edgengram, type=text}}}, active={type=boolean}, fullName={type=text, fields={ngram={analyzer=delimit_edgengram, type=text}}}, title={normalizer=custom_normalizer, type=keyword}, aboutMe={type=text}}}]"
}
},
"status": 400
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:27 (20 by maintainers)
Top Results From Across the Web
elasticsearch-setup operation is not compatible with es 6.x or ...
I would like to input some extra information about using the AWS ElasticSearch. 1 - I created a AWS VPC ElasticSearch version 5.6....
Read more >Breaking changes in 7.0 | Elasticsearch Guide [7.17] | Elastic
An Elasticsearch 7.0 node will not start in the presence of indices created in a version of Elasticsearch before 6.0. Reindex indices from...
Read more >Test if ES Client version 7.x is compatible with ES 6.x server
Given that our compatibility with Elasticsearch version 6.x is conflicting with out ability to use Opensearch 1.2.x #327560 (comment 829496980) ...
Read more >6 Elasticsearch setup - Zabbix
The setup procedure described in this section is applicable to Elasticsearch version 7.X. In case an earlier or later version of Elasticsearch is...
Read more >Elasticsearch Setup | Nuxeo Documentation
x with x >= 7 RestClient protocol only (Elastic ensures forward compatibility on minor version, 7.7 has been validated). Library: 6.5.3. Cluster ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, yes, that’s ok. Company name is Kindred Group.
@shirshanka This should have been fixed along with the ES7 migration. Let’s close the ticket!