Dating index template

Rated 3.91/5 based on 643 customer reviews

Therefore, use of this template for non-Gregorian dates or dates outside that range constitutes a false claim of conformance to the ISO 8601 standard.

What you see happens because in the initial match on name (without type), it ends up actually matching on the catch all Is there any plan to fix this? Is there any other way to provide specific dynamic mapping template for strings and another template for all other types? I want strings within a subpath to be analyzed with a specific analyzer, and for all other types in the same subpath to be not_analyzed (but with some other changes for which I need a mapping defined -- for example, a set index_name).It seems because of this behavior I may need to put my strings into a different subpath.I was hoping to avoid making structure choices in my documents just so I can map it correctly.This is the template used by logstash: https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/lib/logstash/outputs/elasticsearch/There is a valuable reason to make index template support built into the plugin: in a containerized environment we do not know when elasticsearch container will start and we have to PUT index template to it before fluentd will send data.There are some possible workarounds but every of them looks really ugly.

Leave a Reply