Skip to content

Update created version major #14607

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

rahulgoswami
Copy link

Description

@rmuir
Copy link
Member

rmuir commented May 4, 2025

As states on the dev list, I don't think we should do this.

@rahulgoswami
Copy link
Author

As states on the dev list, I don't think we should do this.

Can you please elaborate why? I have tried to address the concern you brought up on the mailing list via the implementation in this PR.

The primary premise behind the API is that IF all segments of an index are created by the LATEST version, the index in all respects is LATEST. "indexCreatedVersionMajor" should ideally not block a Lucene upgrade in that case.

Happy to learn if I am missing anything.

@rmuir
Copy link
Member

rmuir commented May 5, 2025

Because that's not what this variable means. If you want to change index backwards compatibility policy, lying about the version is not the way. -1

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.

2 participants