Is there a way to define multiple path_unmatch? I've a requirement where I
need to exclude more than one fields from that regex but I also can't give
away with regex in path_match.
Is there a way to define multiple path_unmatch? I've a requirement where I
need to exclude more than one fields from that regex but I also can't give
away with regex in path_match.
Sorry for late reply. The reply got missed in filters and I wasn't
notified. My current template looks like: http://pb.abhijeetr.com/RiUH and
indices are created with the name "logstash-date-here".
These are basically logs and text from logs is parsed and corresponding
fields are created. My aim is to not analyse all "@fields.*" but specify
analyzers for only the fields I want, in the above template ( http://pb.abhijeetr.com/RiUH), "@fields.syslog_message" (want it whitespace
analyzed) & "@fields.size". (want it to be a long so that I can use
term_stats facets).
Is there a way to define multiple path_unmatch? I've a requirement where
I need to exclude more than one fields from that regex but I also can't
give away with regex in path_match.
Dynamic templates are applied only to fields that are created dynamically.
In other words, if a field is already defined in the mappings (in the
properties sections), it is not affected by dynamic templates in any way.
So, you don't need to list such fields in "path_unmatch".
On Thursday, April 18, 2013 5:59:17 AM UTC-4, Abhijeet Rastogi wrote:
Hi Igor,
Sorry for late reply. The reply got missed in filters and I wasn't
notified. My current template looks like: http://pb.abhijeetr.com/RiUHand indices are created with the name "logstash-date-here".
These are basically logs and text from logs is parsed and corresponding
fields are created. My aim is to not analyse all "@fields.*" but specify
analyzers for only the fields I want, in the above template ( http://pb.abhijeetr.com/RiUH), "@fields.syslog_message" (want it
whitespace analyzed) & "@fields.size". (want it to be a long so that I can
use term_stats facets).
Is there a way to define multiple path_unmatch? I've a requirement where
I need to exclude more than one fields from that regex but I also can't
give away with regex in path_match.
--
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 elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.
On Fri, Apr 19, 2013 at 3:04 AM, Igor Motov imotov@gmail.com wrote:
Dynamic templates are applied only to fields that are created dynamically.
In other words, if a field is already defined in the mappings (in the
properties sections), it is not affected by dynamic templates in any way.
So, you don't need to list such fields in "path_unmatch".
On Thursday, April 18, 2013 5:59:17 AM UTC-4, Abhijeet Rastogi wrote:
Hi Igor,
Sorry for late reply. The reply got missed in filters and I wasn't
notified. My current template looks like: http://pb.abhijeetr.com/RiUHand indices are created with the name "logstash-date-here".
These are basically logs and text from logs is parsed and corresponding
fields are created. My aim is to not analyse all "@fields.*" but specify
analyzers for only the fields I want, in the above template ( http://pb.abhijeetr.com/RiUH), "@fields.syslog_message" (want it
whitespace analyzed) & "@fields.size". (want it to be a long so that I can
use term_stats facets).
Is there a way to define multiple path_unmatch? I've a requirement
where I need to exclude more than one fields from that regex but I also
can't give away with regex in path_match.
--
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 elasticsearc...@**googlegroups.com.
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.