Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terms table that has a "-" in the field splits the item up #765

Closed
datreic opened this issue Dec 11, 2013 · 5 comments
Closed

Terms table that has a "-" in the field splits the item up #765

datreic opened this issue Dec 11, 2013 · 5 comments

Comments

@datreic
Copy link

datreic commented Dec 11, 2013

Creating a "Terms" panel and setting the term to a field that contains "-" in the items causes them to either be broken into multiple rows (duplicated statistics) in the panel or to be removed from the panel

For exampe:

image

image

@randywallace
Copy link

This is a problem you have with your mapping in elasticsearch.

The default analyzer will split your fields by dash, among other characters; the solution is to either change the analyzer for that field, to disable it altogether, or to use a multi-field mapping to handle both analyzed and non_analyzed fields (for which you should use the non-analyzed variant for the terms panel search). Reluctantly, this will likely require re-indexing your data for all given solutions.

Please refer to this for some tips on how to prevent this (and the extremely high possibility of heap spacing your elasticsearch datanodes): http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-facets-terms-facet.html#_memory_considerations_2

Since this is not a Kibana issue, @rashidkpc will likely close this ticket.

@samdoran
Copy link

I'm having the same issue and was wondering if it's Kibana or ES. Nice to know where to start looking.

@samdoran
Copy link

I found two awesome answers on this issue:
elasticsearch index template management
Logstash 1.3.1 Release

The short answer if you're using LS 1.3.1 or later is change your terms query to [field].raw and it will behave is expected. This was addressed using an index template that applies not_analyzed to the .raw fields. Very slick.

@fireflyk
Copy link

fireflyk commented Aug 5, 2014

I met the same problem. Indeed, use xxxxx.raw as the key field.

@chrisspiegl
Copy link

As of logstash 1.4 this seems to no longer work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants
@randywallace @chrisspiegl @rashidkpc @fireflyk @samdoran @datreic and others