Elasticsearch exception "type": "illegal_state_exception", "reason": "only value lists are allowed in serialized settings"

Elastic Stack Elasticsearch
1

Hi all,

Am trying to set up the index in my new environment which is installed with elasticsearch version 6.6.1. The index is already in use in production having elasticsearch version 6.5.1.
I get the following Exception while creating the index which is already used in production.

{
"error": {
"root_cause": [
{
"type": "settings_exception",
"reason": "Failed to load settings from [.....complete index structure.....]",
"caused_by": {
"type": "illegal_state_exception",
"reason": "only value lists are allowed in serialized settings"
}
},
"status": 500
}

The analyzer i have in Index is as follows
"analysis" : {
"filter" : {
"email_filter" : {
"type" : "pattern_capture",
"preserve_original" : "true",
"patterns" : [
"([^@]+)",
"(\p{L}+)",
"(\d+)",
"@(.+)"
]
},
"autocomplete_filter" : {
"type" : "edge_ngram",
"min_gram" : "3",
"max_gram" : "10"
}
},
"char_filter" : {
"digit_only" : {
"pattern" : "\D+",
"type" : "pattern_replace",
"replacement" : ""
}
},
"analyzer" : {
"number_analyzer" : {
"filter" : [
"trim"
],
"char_filter" : [
"digit_only"
],
"type" : "custom",
"tokenizer" : "digit_edge_ngram_tokenizer"
},
"email_analyzer" : {
"filter" : [
"email_filter",
"lowercase",
"unique"
],
"tokenizer" : "uax_url_email"
},
"search_number_analyzer" : {
"filter" : [
"trim"
],
"char_filter" : [
"digit_only"
],
"type" : "custom",
"tokenizer" : "keyword"
},
"autocomplete" : {
"filter" : [
"lowercase",
"autocomplete_filter"
],
"type" : "custom",
"tokenizer" : "standard"
}
},
"tokenizer" : {
"digit_edge_ngram_tokenizer" : {
"token_chars" : [
"digit"
],
"min_gram" : "3",
"type" : "edgeNGram",
"max_gram" : "15"
}
}
},

Any quick response will be very helpful. Kindly let me know if you need complete index structure.

2

please share a fully reproducible example along with information what Elasticsearch version you are using.

Also, please take the time to properly format your posts, as this is hard to read. You can use markdown in here, so please make use of that.

3

I have update the query again. Kindly let me know if you need any further details

4

I would like to see the full request, including HTTP verb and path in order to reproduce it.

The request sample ends with a comma, thus is invalid JSON and there might be something missing. It is super important to see everything you did in order to understand and reproduce the issue.

Please read https://www.elastic.co/help

5

The issue was with the index name which i provided in the script as i get when i do a 'GET party ' from the existing index.
But the error message was misleading .

Thanks for your quick response

6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.