You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
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
The text was updated successfully, but these errors were encountered: