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

Kibana support for indices without types #11149

Closed
alexfrancoeur opened this issue Apr 11, 2017 · 3 comments
Closed

Kibana support for indices without types #11149

alexfrancoeur opened this issue Apr 11, 2017 · 3 comments
Assignees
Labels
Team:QA Team label for QA Team

Comments

@alexfrancoeur
Copy link

alexfrancoeur commented Apr 11, 2017

The Elasticsearch team is targeting a 5.5 feature that will allow users to disable the _type field when creating indices. I'd like to make sure Kibana does not break when working with indices that are missing this field. This work would involve testing all supported aspects of Kibana.

Elasticsearch issue: Remove support for types? #15613

@epixa
Copy link
Contributor

epixa commented Apr 11, 2017

We only need to verify that this works with indices that we search against (in the data cluster) rather than our own indices (in the admin cluster). We have a migration plan in place for the latter, and people shouldn't be manually changing settings on our internal indices.

@Bargs
Copy link
Contributor

Bargs commented Apr 11, 2017

Relevant bit from the ES ticket:

Add support for setting enabled:false to the _type field, which will exclude type from the UID and use a fixed type name for (eg) mapping requests/responses.

I think we'll be mostly ok since the API response structure will remain the same. The change to UID might cause issues if we're using it anywhere

@jbudz
Copy link
Member

jbudz commented Oct 3, 2019

This is good - next phase at #47217

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:QA Team label for QA Team
Projects
None yet
Development

No branches or pull requests

8 participants