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

Text aggregations are failing #5

Open
dbason opened this issue Mar 21, 2017 · 4 comments
Open

Text aggregations are failing #5

dbason opened this issue Mar 21, 2017 · 4 comments

Comments

@dbason
Copy link

dbason commented Mar 21, 2017

When generating the list of hosts I get the following error in the Kibana logs:
"Fielddata is disabled on text fields by default. Set fielddata=true on [type] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory"

Should the source, host, and type aggregations be using the .raw or .keyword fields?

@elessarkrin
Copy link
Member

elessarkrin commented Mar 24, 2017

If you are getting these issues is probably that you don't have the type field as keyword, all host, source, type should be keyword

@dbason
Copy link
Author

dbason commented Mar 30, 2017

We're using the default logstash template which analyzes the base field and uses .keyword for the keyword fields, and I'd prefer to keep using this scheme. Not a problem, I can just fork and update it for my environment.

@sunomie
Copy link

sunomie commented Jan 7, 2018

@dbason any chance you'd be willing to share your fork? I'm running into this same issue (type is text and have type.keyword), but I cannot seem to figure out how to patch kibana-logbrowser to use type.keyword instead. Thanks!

@dbason
Copy link
Author

dbason commented Jan 7, 2018

@sunomie I actually didn't pursue this sorry. We've ended up using the logtrail plugin instead - https://github.com/sivasamyk/logtrail

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

3 participants