You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{
"error": {
"root_cause": [
{
"type": "mapper_parsing_exception",
"reason": "Cannot set [doc_values] on field of type [search_as_you_type]"
}
],
"type": "mapper_parsing_exception",
"reason": "Failed to parse mapping: Cannot set [doc_values] on field of type [search_as_you_type]",
"caused_by": {
"type": "mapper_parsing_exception",
"reason": "Cannot set [doc_values] on field of type [search_as_you_type]"
}
},
"status": 400
}
But then, after a field mapper "search_as_you_type" has been correctly created, a GET will always have doc_values set as false:
Reported in the java repo.
Search as you type doesn’t support
doc_values
as a field, in fact trying to add it will result in a server error:returns
But then, after a field mapper "search_as_you_type" has been correctly created, a GET will always have
doc_values
set as false:There's a justification for this in a comment in the server code.
Possible ways to handle this:
I don't think we can have a separate response class since
SearchAsYouTypeProperty
is part of theProperty
variant and would complicate things a lot.Field definition:
The text was updated successfully, but these errors were encountered: