Dynamic template match precendece

(David Severski) #1

I'm a LS 1.4.0 / ES 1.1.1 user and I seem to be hitting some precedence
problems with my custom ES template -
https://gist.github.com/davidski/84fb9e2b32c111bfd2d5. My Elasticsearch
logs are full of errors about my src_geoip field not being a fully
qualified IP address, which suggests that the wildcard "*ip" dynamic match
is taking precedence over the specific "src_geoip" field later in the file.
Is the interaction between multiple matches a defined case in ES? Since I
want specific definitions to always be honored over wildcard matches,
should these more specific matches be placed first in the template file in
order to take effect?

Thanks for the help!


You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/bae909fb-fe3a-4e10-bd1a-a9f42c418fdf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

(system) #2