-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Index alias filters are not respected (Kibana 4.3) #5640
Comments
Due to the way kibana resolves the indices of timebased indices we can not support filtered aliases. It is the nature of the elasticsearch We use the The right way to bind visualizations to a filtered subset of data in Kibana is to create a saved search, then link the visualization to it. They're also a lot easier to update than aliases! |
Ok perhaps Kibana should disallow adding an index pattern for an alias and provide a helpful message. Otherwise you end up with multiple copies of the index pattern for the base index and a confused user looking at every type of data in the index despite the filter. |
But I really need the alias to distinguish index privileges。 |
If an index pattern is created from an alias that has a filter the discover pane shows results which somehow bypass the filter. In my case I am using a terms filter based on _type. The discover pane also lists the fields for the type which I should not be seeing. The goal in using aliases was to make it easier for a user to make a visualization based on data of a particular type without needing to mess with the search bar. These limitations make using the index alias feature pointless in our case.
The text was updated successfully, but these errors were encountered: