You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
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: