Skip to content
This repository has been archived by the owner on Dec 1, 2018. It is now read-only.

ElasticSearch data is not mapped well #1262

Closed
AlmogBaku opened this issue Aug 18, 2016 · 2 comments · Fixed by #1276
Closed

ElasticSearch data is not mapped well #1262

AlmogBaku opened this issue Aug 18, 2016 · 2 comments · Fixed by #1276

Comments

@AlmogBaku
Copy link
Contributor

AlmogBaku commented Aug 18, 2016 •
edited
Loading

elastic/kibana#364

ES Sink does not configure a mapping scheme for the data, this causing the ES to analyze fields such as names.. (then it's problematic to create visualizations)

I.e I have an container named "my-nginx-proxy", but when I create a visualization it's analyzed into 3 different entities "my", "nginx", "proxy"
@AlmogBaku
Copy link
Contributor Author

http://thomasardal.com/terms-aggregations-on-analyzed-fields-in-elasticsearch/

@AlmogBaku
Copy link
Contributor Author

@huangyuqi what do you think about that?

AlmogBaku added a commit to AlmogBaku/heapster that referenced this issue Sep 2, 2016
@AlmogBaku
add mapping to ES Sink. fixes kubernetes-retired#1262
424fd50
@AlmogBaku AlmogBaku mentioned this issue Sep 2, 2016
Merged
AlmogBaku added a commit to AlmogBaku/heapster that referenced this issue Sep 2, 2016
@AlmogBaku
add mapping to ES Sink. fixes kubernetes-retired#1262
6ecdc58
AlmogBaku added a commit to AlmogBaku/heapster that referenced this issue Sep 2, 2016
@AlmogBaku
fixes kubernetes-retired#1262 :
4dee570 
 - mapping fields as well (keeps an indexable and raw versions of most of the strings)
 - added an alias in order to create to indexes in kibana
@AlmogBaku AlmogBaku mentioned this issue Sep 23, 2016
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix ElasticSearch sink mapping AlmogBaku/heapster
1 participant
@AlmogBaku