Range filter queries degrade nicely across unmapped dynamic_template fields, while numeric_range queries throw an error : "failed to find mapping for field". Bug, Feature, or as Designed? Tested on 0.19.11 Thank you. --

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.

Inconsistent behavior between "range" and "numeric_range" on unmapped dynamic_template fields