I am seeing strange warnings (see below) when putting mappings
containing 'dynamic_templates'. The mapping seems perfectly right and
if you closely look at the warning below you find that only the order
of the 'match' and 'match_mapping_type' is different. Content wise the
mappings are the same. Is this a bug in Elastic Search? Is there
anything I can do on my end to avoid the warning (as it is badly
spamming my log files)?
Its not something that breaks the system, its just a warning that extra processing of mapping is done (which should not really be done). I simply need to fix it (the warning is there so if I miss something, it will bubble up through the users ). Can you gist a recreation of this so it will be simpler for me to fix it? (Elasticsearch Platform — Find real-time answers at scale | Elastic)
-shay.banon
On Tuesday, March 8, 2011 at 5:15 PM, Jan Fiedler wrote:
I am seeing strange warnings (see below) when putting mappings
containing 'dynamic_templates'. The mapping seems perfectly right and
if you closely look at the warning below you find that only the order
of the 'match' and 'match_mapping_type' is different. Content wise the
mappings are the same. Is this a bug in Elastic Search? Is there
anything I can do on my end to avoid the warning (as it is badly
spamming my log files)?
Its not something that breaks the system, its just a warning that extra processing of mapping is done (which should not really be done). I simply need to fix it (the warning is there so if I miss something, it will bubble up through the users ). Can you gist a recreation of this so it will be simpler for me to fix it? (Elasticsearch Platform — Find real-time answers at scale | Elastic)
-shay.banonOn Tuesday, March 8, 2011 at 5:15 PM, Jan Fiedler wrote:
I am seeing strange warnings (see below) when putting mappings
containing 'dynamic_templates'. The mapping seems perfectly right and
if you closely look at the warning below you find that only the order
of the 'match' and 'match_mapping_type' is different. Content wise the
mappings are the same. Is this a bug in Elastic Search? Is there
anything I can do on my end to avoid the warning (as it is badly
spamming my log files)?
Its not something that breaks the system, its just a warning that extra processing of mapping is done (which should not really be done). I simply need to fix it (the warning is there so if I miss something, it will bubble up through the users ). Can you gist a recreation of this so it will be simpler for me to fix it? (Elasticsearch Platform — Find real-time answers at scale | Elastic)
-shay.banonOn Tuesday, March 8, 2011 at 5:15 PM, Jan Fiedler wrote:
I am seeing strange warnings (see below) when putting mappings
containing 'dynamic_templates'. The mapping seems perfectly right and
if you closely look at the warning below you find that only the order
of the 'match' and 'match_mapping_type' is different. Content wise the
mappings are the same. Is this a bug in Elastic Search? Is there
anything I can do on my end to avoid the warning (as it is badly
spamming my log files)?
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.