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

Ensure elasticsearch doesn't start with unuspported indices #20514

Merged
merged 1 commit into from
Sep 16, 2016

Conversation

s1monw
Copy link
Contributor

@s1monw s1monw commented Sep 15, 2016

If an index was created with pre 2.0 we should not treat it as supported
even if all segments have been upgraded to a supported lucene version.

Closes #20512

If an index was created with pre 2.0 we should not treat it as supported
even if all segments have been upgraded to a supported lucene version.

Closes elastic#20512
@rjernst
Copy link
Member

rjernst commented Sep 15, 2016

LGTM

@s1monw
Copy link
Contributor Author

s1monw commented Sep 15, 2016

retest this please

@s1monw s1monw added the >bug label Sep 15, 2016
@s1monw
Copy link
Contributor Author

s1monw commented Sep 16, 2016

retest this please

1 similar comment
@s1monw
Copy link
Contributor Author

s1monw commented Sep 16, 2016

retest this please

@s1monw s1monw merged commit 3aabda6 into elastic:master Sep 16, 2016
s1monw added a commit that referenced this pull request Sep 16, 2016
If an index was created with pre 2.0 we should not treat it as supported
even if all segments have been upgraded to a supported lucene version.

Closes #20512
s1monw added a commit that referenced this pull request Sep 16, 2016
If an index was created with pre 2.0 we should not treat it as supported
even if all segments have been upgraded to a supported lucene version.

Closes #20512
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants