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

"Visualize: Fielddata is disabled on text fields by default." #22633

Closed
rootameen opened this issue Jan 16, 2017 · 3 comments
Closed

"Visualize: Fielddata is disabled on text fields by default." #22633

rootameen opened this issue Jan 16, 2017 · 3 comments

Comments

@rootameen
Copy link

Hi guys,
I recently started a new setup of ELK stack based on version 5.1. Everything went smoothly except for the visualization section on Kibana. Whenever I try to create something (like a visual of beat.name), I get the error message:

Visualize: Fielddata is disabled on text fields by default. Set fielddata=true on [beat.name] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory.

I'm currently using filebeat to ship all my log messages, and I've checked the official documentation and came across this link: https://www.elastic.co/guide/en/elasticsearch/reference/5.0/fielddata.html

I tried to apply it on my setup but I just can't figure out what exactly to put in the curl statement to reflect this change on logs. What should I relpace "/my_index/_mapping/my_type" with?

I appreciate your help.

Thanks.

@rootameen rootameen changed the title Unable to get rid off error: "Visualize: Fielddata is disabled on text fields by default." "Visualize: Fielddata is disabled on text fields by default." Jan 16, 2017
@dadoonet
Copy link
Member

Please ask questions on discuss.elastic.co where we can help.

@rootameen
Copy link
Author

Hi @dadoonet. I already posted twice there but got 0 responses, that's why I thought about posting here :)

@clintongormley
Copy link
Contributor

@rootameen Did you try searching? If so you would have found this: #15267 (comment)

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