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

Cannot run Kibana upgrade assistant (7.x=>8.0) on Security Index #39018

Open
tvernum opened this issue Feb 17, 2019 · 2 comments
Open

Cannot run Kibana upgrade assistant (7.x=>8.0) on Security Index #39018

tvernum opened this issue Feb 17, 2019 · 2 comments
Labels
:Security/Security Security issues without another label Team:Security Meta label for security team

Comments

@tvernum
Copy link
Contributor

tvernum commented Feb 17, 2019

The Kibana upgrade assistant reindexes to a single _doc type in preparation for the full removal of types.
The security index cannot handle this because it explicitly indexes into the doc type.

We hope and expect that there won't be a standard "security index" in 8.0, rather it will be migrated to a special "system index" with a different internal API that will have different feature/compatibility trade offs, and we will need to provide a special migration process to move the 7.x security index to a 8.0 style system-index.

However, if for some reason that doesn't happen, then we will need to move the security code to use the typeless APIs during the 7.x series so that it is compatible with 8.0, and the Kibana upgrade assistant.

Related: #38740

@tvernum tvernum added the :Security/Security Security issues without another label label Feb 17, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

@droberts195
Copy link
Contributor

I think this is the same problem as #38796 (comment), which is hopefully fixed by #39256, i.e. moving to typeless APIs in 7.0. However, I have some concerns that there are edge cases where there will be problems: #39256 (comment)

We're aiming to test these edge cases at the beginning of next week so you might want to subscribe to that issue and PR in case we find anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Security/Security Security issues without another label Team:Security Meta label for security team
Projects
None yet
Development

No branches or pull requests

4 participants