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

[Discover] Selected fields persist even after changing index pattern #72829

Closed
mbondyra opened this issue Jul 22, 2020 · 2 comments
Closed

[Discover] Selected fields persist even after changing index pattern #72829

mbondyra opened this issue Jul 22, 2020 · 2 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Discover Discover Application Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@mbondyra
Copy link
Contributor

mbondyra commented Jul 22, 2020

I am not exactly sure if it's a bug, @kertal can you assess?

Kibana version:
master

Steps to reproduce:

  1. Use kibana instance with at least 2 index patterns defined
  2. Go to discover
  3. Choose some of the fields from available fields list to add them to selected fields
  4. Change index pattern
  5. Current behavior: the selected fields list is empty on the fields list, but the table displays them without data

Here's the video showing the behaviour: https://www.loom.com/share/20afb40eb85a497e8e12ef2ff0ddb842

Expected behavior:
Table is displayed with '_source'. (?)

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

@mbondyra mbondyra added bug Fixes for quality problems that affect the customer experience Feature:Discover Discover Application Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jul 22, 2020
@lizozom
Copy link
Contributor

lizozom commented Jul 22, 2020

I suspect this might be related to a use case where the same fields are present in both IPs (for example if they are using the Elastic Common Schema).

I think the better logic would be, if the field does not exist in the new IP, remove it.

@mbondyra
Copy link
Contributor Author

Closing as it's the duplicate of #57322

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 Feature:Discover Discover Application Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

2 participants