We are using Elasticsearch 1.3.2 and having issues running queries with
aggregations on unmapped fields. Some documents in the index will have this
nested aggregation field but some will not. Did some initial research but
did not find a way to tell ES to ignore unmapped fields in aggregations.
Looks like there is a setting to ignore unmapped fields for sort fields but
not for aggregation fields.
This is the exception that am getting
"status" : 500,
"reason" :
"RemoteTransportException[[serverXXXX][inet[/serverXXXX:9300]][search/phase/query]];
nested: AggregationExecutionException[[nested] nested path [fieldName] not
found]; "
We are using Elasticsearch 1.3.2 and having issues running queries with
aggregations on unmapped fields. Some documents in the index will have this
nested aggregation field but some will not. Did some initial research but
did not find a way to tell ES to ignore unmapped fields in aggregations.
Looks like there is a setting to ignore unmapped fields for sort fields but
not for aggregation fields.
This is the exception that am getting
"status" : 500,
"reason" :
"RemoteTransportException[[serverXXXX][inet[/serverXXXX:9300]][search/phase/query]];
nested: AggregationExecutionException[[nested] nested path [fieldName] not
found]; "
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.