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

Importing legacy json file throws index pattern exception #64280

Closed
flash1293 opened this issue Apr 23, 2020 · 3 comments · Fixed by #66186
Closed

Importing legacy json file throws index pattern exception #64280

flash1293 opened this issue Apr 23, 2020 · 3 comments · Fixed by #66186
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v7.8.0

Comments

@flash1293
Copy link
Contributor

Kibana version: master

Describe the bug: Importing a legacy json file exported from 6.8 sems to successfully import all objects, but an exception is thrown and the user sees a technical warning about not being able to clear the index pattern cache

Steps to reproduce:

  1. Go to management > saved objects
  2. Open import flyout
  3. Drop this file: https://gist.githubusercontent.com/flash1293/0ea158f94dd165647c560d1b90a5ed72/raw/e322a98549a4893589d36e1f42a431b66113a979/export.json
  4. Start import
  5. Error is shown: this.patternCache.clear is not a function

Expected behavior:
Success message shown

Screenshots (if relevant):
Screenshot 2020-04-23 at 09 42 17

@flash1293 flash1293 added bug Fixes for quality problems that affect the customer experience Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Apr 23, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@pgayvallet
Copy link
Contributor

Seems like the relevant call is here, in IndexPattern.save:

// Clear cache
this.patternCache.clear(this.id);

@elastic/kibana-app-arch I think this is an issue in the data plugin, not in the SOM consumer. Would you mind taking a look?

@ppisljar
Copy link
Member

taking a look

@ppisljar ppisljar mentioned this issue May 13, 2020
@ppisljar ppisljar self-assigned this May 13, 2020
kibana-app-arch automation moved this from To triage to Done in current release Jun 8, 2020
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 Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v7.8.0
Projects
kibana-app-arch
  
Done in current release
Development

Successfully merging a pull request may close this issue.

5 participants