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

Invisible filter applied after index deleted and re-created. #9704

Closed
stacey-gammon opened this issue Jan 3, 2017 · 3 comments
Closed

Invisible filter applied after index deleted and re-created. #9704

stacey-gammon opened this issue Jan 3, 2017 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience

Comments

@stacey-gammon
Copy link
Contributor

stacey-gammon commented Jan 3, 2017

Kibana version: master

When an index gets deleted out from under Kibana, the filters aren't cleared. When a new index is created, the filter will remain in the queries but not be visible in the UI.

Steps to repro:

  • Start elasticsearch & Kibana
  • Run npm run makelogs
  • Create your logstash index and pin a filter on the discover tab (e.g. machine.os: xp)
  • Reboot your elasticsearch instance so it loses all it's data (I'm running it off gradle run so stopping and starting clears all the data).
  • Refresh the page in Kibana.
  • You'll be redirected to the management section and asked to create a default index, run npm run makelogs and re-create the logstash index. Notice the filter persists in the url.

screen shot 2017-01-03 at 10 02 44 am

  • Go to the visualize tab and try to create a new visualization, like a metric of the count. Notice the filter is still in the url but not shown in the filter bar. Your request will show the invisible filter applied.

screen shot 2017-01-03 at 9 39 29 am

@stacey-gammon stacey-gammon added the bug Fixes for quality problems that affect the customer experience label Jan 3, 2017
@stacey-gammon stacey-gammon changed the title Corrupt filter stored in state being used on the wrong index Invisible filter applied after index deleted and re-created. Jan 3, 2017
@Bargs
Copy link
Contributor

Bargs commented Jan 3, 2017

Similar (or same?) issue: #7767

@ThomasFlanaghan
Copy link

Seems to be the same but a different method was used to recreate it.

@stacey-gammon
Copy link
Contributor Author

Duplicate of #7767

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience
Projects
None yet
Development

No branches or pull requests

3 participants