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

Support v6 mappings for saved objects import/export #12792

Merged
merged 3 commits into from
Jul 13, 2017

Conversation

tylersmalley
Copy link
Contributor

@tylersmalley tylersmalley commented Jul 12, 2017

Buried in here is a change that closes #10779

@@ -76,6 +76,7 @@ export default function MappingSetupService(kbnIndex, esAdmin) {
const prom = getKnownKibanaTypes()
.then(function (knownTypes) {
// if the type is in the knownTypes array already
return false;
Copy link
Contributor Author

@tylersmalley tylersmalley Jul 12, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hack until #12793 is resolved.

@spalger spalger removed the blocked label Jul 13, 2017
@spalger
Copy link
Contributor

spalger commented Jul 13, 2017

jenkins, test this

1 similar comment
@spalger
Copy link
Contributor

spalger commented Jul 13, 2017

jenkins, test this

@thomasneirynck
Copy link
Contributor

region map test failure looks unrelated. Looking into it..

@tylersmalley
Copy link
Contributor Author

jenkins, test this

@tylersmalley
Copy link
Contributor Author

@epixa and @spalger, this is now green.

@@ -53,7 +53,6 @@ export function SavedObjectProvider(esAdmin, kbnIndex, Promise, Private, Notifie

// type name for this object, used as the ES-type
const esType = config.type;
this.index = kbnIndex;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you remove this? Are you sure this doesn't have trickle down effects elsewhere, on xpack or something?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldn't find any instance of it being used and never ran into an error when testing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is why I love getters so much, easier to find uses but mostly that unexpected accesses that are broken by changes/removal are much louder

@epixa
Copy link
Contributor

epixa commented Jul 13, 2017

I'm noticing an issue with this:

If I have a fresh install of Elasticsearch/Kibana and I create my first index pattern. The first time I navigate to discover, I get warning notification. This is easily repeatedly by deleting the index pattern, refreshing, creating it again, and then navigating to discover.

screen shot 2017-07-13 at 3 50 48 pm

@epixa
Copy link
Contributor

epixa commented Jul 13, 2017

Regarding my previous comment, the data does load in discover, so I'm not really sure what this is warning about.

@tylersmalley
Copy link
Contributor Author

I am fairly certain this is caused by the session storage. The dashboard is attempting to redirect you back to the page you were previously on which contained an index pattern you since deleted.

@epixa
Copy link
Contributor

epixa commented Jul 13, 2017

Yep, you're right.

@spalger
Copy link
Contributor

spalger commented Jul 13, 2017

In a separate PR we should probably change that error message to We couldn't load the previously used index pattern, switched to the default index pattern "{{ indexPattern.title }}"

@epixa
Copy link
Contributor

epixa commented Jul 13, 2017

LGTM

@tylersmalley tylersmalley merged commit 496fd93 into elastic:master Jul 13, 2017
tylersmalley added a commit to tylersmalley/kibana that referenced this pull request Jul 13, 2017
tylersmalley added a commit that referenced this pull request Jul 13, 2017
_id: hit._id.replace(`${this.type}:`, ''),
_type: this.type,
_source: hit._source[this.type],
_meta: {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😻

@jimgoodwin jimgoodwin added Team:Operations Team label for Operations Team release_note:roadmap labels Jul 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Append version on exported saved objects
6 participants