You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the _default_ mapping specification disables doc_values for tags field. I think we should consider enabling it but it will require a bit of discussion and can introduce breaking change.
# existing ES 2.x notation
- name: tagstype: stringdoc_values: falseindex: analyzedanalyzer: whitespacedescription: > Optionally provided operator defined list of tags placed on each log by the collector or normalizer. The payload can be a string with whitespace-delimited string tokens, or a JSON list of string tokens.
more efficient aggregations and sorting (I guess tags field is a good candidate to aggregate on)
Cons:
not possible on analyzed string which means users will be able to provide multiple tags only via an array, like: "tags": ["foo", "bar"] and no whitespace analyzer will be run on the content of individual values.
The text was updated successfully, but these errors were encountered:
Currently, the
_default_
mapping specification disablesdoc_values
fortags
field. I think we should consider enabling it but it will require a bit of discussion and can introduce breaking change.Relevant read: https://www.elastic.co/guide/en/elasticsearch/reference/5.5/doc-values.html
Pros:
tags
field is a good candidate to aggregate on)Cons:
"tags": ["foo", "bar"]
and nowhitespace
analyzer will be run on the content of individual values.The text was updated successfully, but these errors were encountered: