Is it possible to somehow configure dynamic_templates so that multiple
matching templates will be applied? It seems to me that only the first
matching template is used. I can see why that is, but if there's a
workaround I'd love to know about it
As an example, I'm using something like the dynamic templates below
and would like strings to be mapped both as multifield and as not
included in all IF their names end with "!inall".
Multiple matching templates are supported by ES (see the end of Elasticsearch Platform — Find real-time answers at scale | Elastic).
It looks like you don't have a parallel structure between your two
mappings, though -- did you intend to put the 'include_in_all' key
inside a field definition?
Is it possible to somehow configure dynamic_templates so that multiple
matching templates will be applied? It seems to me that only the first
matching template is used. I can see why that is, but if there's a
workaround I'd love to know about it
As an example, I'm using something like the dynamic templates below
and would like strings to be mapped both as multifield and as not
included in all IF their names end with "!inall".
I'm not sure what you mean by parallel structure? The last template is
applied if I remove the first, otherwise the first but not the second
is applied.
I should probably add that I'm using these for the default type in a
default-mapping.json file.
Multiple matching templates are supported by ES (see the end ofhttp://www.elasticsearch.org/guide/reference/api/admin-indices-templa...).
It looks like you don't have a parallel structure between your two
mappings, though -- did you intend to put the 'include_in_all' key
inside a field definition?
Is it possible to somehow configure dynamic_templates so that multiple
matching templates will be applied? It seems to me that only the first
matching template is used. I can see why that is, but if there's a
workaround I'd love to know about it
As an example, I'm using something like the dynamic templates below
and would like strings to be mapped both as multifield and as not
included in all IF their names end with "!inall".
Multiple matching templates are supported by ES (see the end ofhttp://www.elasticsearch.org/guide/reference/api/admin-indices-templa...).
It looks like you don't have a parallel structure between your two
mappings, though -- did you intend to put the 'include_in_all' key
inside a field definition?
Is it possible to somehow configure dynamic_templates so that multiple
matching templates will be applied? It seems to me that only the first
matching template is used. I can see why that is, but if there's a
workaround I'd love to know about it
As an example, I'm using something like the dynamic templates below
and would like strings to be mapped both as multifield and as not
included in all IF their names end with "!inall".
There isn't support in dynamic templates to "aggregate templates", the first
one matches (ordered) will be used, so you need to provide full mapping on
relevant ones. Its a bit tricky (at least in the way its implemented
currently) to apply everything the matches to the new field mapping
introduced.
Multiple matching templates are supported by ES (see the end ofhttp:// Elasticsearch Platform — Find real-time answers at scale | Elastic...).
It looks like you don't have a parallel structure between your two
mappings, though -- did you intend to put the 'include_in_all' key
inside a field definition?
Is it possible to somehow configure dynamic_templates so that multiple
matching templates will be applied? It seems to me that only the first
matching template is used. I can see why that is, but if there's a
workaround I'd love to know about it
As an example, I'm using something like the dynamic templates below
and would like strings to be mapped both as multifield and as not
included in all IF their names end with "!inall".
There isn't support in dynamic templates to "aggregate templates", the
first one matches (ordered) will be used, so you need to provide full
mapping on relevant ones. Its a bit tricky (at least in the way its
implemented currently) to apply everything the matches to the new field
mapping introduced.
Multiple matching templates are supported by ES (see the end ofhttp:// Elasticsearch Platform — Find real-time answers at scale | Elastic...).
It looks like you don't have a parallel structure between your two
mappings, though -- did you intend to put the 'include_in_all' key
inside a field definition?
Is it possible to somehow configure dynamic_templates so that multiple
matching templates will be applied? It seems to me that only the first
matching template is used. I can see why that is, but if there's a
workaround I'd love to know about it
As an example, I'm using something like the dynamic templates below
and would like strings to be mapped both as multifield and as not
included in all IF their names end with "!inall".
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.