There is a level
analyzed field with values like "INFO"
, "WARN"
, "ERROR"
...
Sometimes the values can be lowercased like "info"
.
When I do a simple terms aggregation in Kibana 2 buckets are created: one for "INFO"
and another for "info"
.
I've specified the CASE_INSENSITIVE
flag without any success.
Is it possible to get this behavior without touching the tokenization of this field at the ElasticSearch level?
OK finally I've found a way to do that:
level
String
Upper Case
Update Field
buttonNow when I build most visualizations "INFO"
and "info"
are considered the same and are merged.
But table views still continue to consider them as distinct even if they both appear as "INFO"
!