we have some fields which are marked as below
old version
"field1": {
"type": "string",
"index": "no"
}
v8
"field1": {
"type": "text",
"index": false
}
earlier in older version it used to send empty response without any exception but now when we search in the new ES version its throwing one exception Cannot search on field [field1] since it is not indexed
is there any recommendations to handle this scenario or is there any config available to suppress this behaviour(something similar to ignore_unmapped )
@dadoonet we have dynamic templates to have mappings to the fields which are not recognised and we mark them as non-indexed fields, even though these fields are not indexed users can still go ahead and search on these dynamic fields.
this is the reason why i am ending up in this situation.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.