-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Better handling of multiple types #2943
Comments
We intentionally don't handle types as we don't recommend their usage. Types tend to confuse people, they believe that they can have different core types (eg, string, long) across different elasticsearch types, which is not the case. Elasticsearch has actually discussed completely getting rid of types in the past. Feel free to comment on this ticket with additional suggestions for handling large mappings: #1540 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've got quite a few different data sources going into elasticsearch, but rather than having a daily index for each, I put them all into the same indices and separate them by type, as is recommended to avoid a large number of indices. I then have an filtered alias for each data type, so it "looks" as if they have their own index, which works well with Kibana 4.
Apart from one thing... when selecting fields I have a very long list as all fields from all the types are shown, rather than just the one for this alias (=type in my case). Could Kibana take an extra option of type when defining indicies?
The text was updated successfully, but these errors were encountered: