Thanks Chris, Radu for helping out!
Here is my scenario: The reason I chose dynamic mapping (via templates) is
that I am not completely aware of what fields will be indexed (thus mapped)
on the fly. If I knew the exact range/domain of fields that I would
encounter, I would have created explicit mappings. So, if I query (any
facet query) for say 100 such fields and even if 1 of them is absent, I get
an exception from ES with "missing mapping" error. This means that I am
required to know what fields are already mapped before sending a query
which makes dynamic mapping less useful to me. I would love to get response
for other 99 fields which were present in the mapping rather than a failed
query. ES can just skip the fields that are not present in mapping. Does it
On Wednesday, November 7, 2012 2:26:43 AM UTC-8, Chris Male wrote:
What would you like to happen instead of the error? The error is reporting
that the mapping wasn't found and so it cannot create any facet information.
On Wednesday, November 7, 2012 4:58:47 PM UTC+11, revdev wrote:
Any idea how to suppress these errors? Otherwise, I need to keep track of
what all dynamic fields were indexed and then request only those which is
thanks in advance.
On Tuesday, November 6, 2012 1:55:05 PM UTC-8, revdev wrote:
I am performing a facet query on a dynamic object field but if field is
not already indexed, I get an error
"ElasticSearchIllegalArgumentException[failed to find mappings for
[object1.object2.field]]; }]" since it is not available in the mapping. Is
there anyway to suppress that warming and just return no results ?