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

[Remove] Legacy 6x BWC Support #1218

Closed
wants to merge 3 commits into from

Conversation

nknize
Copy link
Collaborator

@nknize nknize commented Sep 6, 2021

This PR removes all support for legacy 6x bwc logic that is no longer supported in 2.0.

This commit removes all support for legacy 6x bwc logic that is no longer
supported in 2.0.

Signed-off-by: Nicholas Walter Knize <[email protected]>
Signed-off-by: Nicholas Walter Knize <[email protected]>
@nknize nknize marked this pull request as draft September 6, 2021 21:45
@opensearch-ci-bot
Copy link
Collaborator

✅   DCO Check Passed 881d2f3

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Wrapper Validation success 881d2f3

@opensearch-ci-bot
Copy link
Collaborator

❌   Gradle Precommit failure 881d2f3
Log 1092

@dblock
Copy link
Member

dblock commented Sep 8, 2021

I'm going to ask the hard question: do we have to? Wouldn't users prefer we tried to maintain bcw support over more major versions and how bad would that be in terms of effort?

Signed-off-by: Nicholas Walter Knize <[email protected]>
@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Wrapper Validation success 587bc7b

@opensearch-ci-bot
Copy link
Collaborator

✅   DCO Check Passed 587bc7b

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Precommit success 587bc7b

@nknize
Copy link
Collaborator Author

nknize commented Sep 9, 2021

do we have to?

Unfortunately, for the deprecated features we inherited (e.g., zen1, deprecated types).. yes. Unfortunately, because the versioning mechanism we inherited is tied to specific Lucene versions that will no longer be available in the next major lucene releases (e.g., IndexFormat changes, endianess, overall improvements)...yes.

I know there have been public discussions about supporting bwc indefinitely, but we just don't have the mechanisms or designs in place (e.g., compatibility modules, legacy format support) to support such a capability and that will take some time. Furthermore, we're not actually removing anything that hasn't already been deprecated and/or disabled upstream (outside OpenSearch purview). So we're safe to remove these pre-selected deprecated features in OpenSearch 2.0. This also gives us some runway to thoughtfully decide how to implement LTS for OpenSearch 1+ in OpenSearch 3+ versions.

@nknize
Copy link
Collaborator Author

nknize commented Sep 9, 2021

start gradle check

@opensearch-ci-bot
Copy link
Collaborator

❌   Gradle Check failure 587bc7b
Log 514

Reports 514

@dblock
Copy link
Member

dblock commented Sep 28, 2021

@nknize Want to rebase and finish this?

@opensearch-ci-bot
Copy link
Collaborator

Can one of the admins verify this patch?

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Wrapper Validation success 587bc7b

@opensearch-ci-bot
Copy link
Collaborator

✅   DCO Check Passed 587bc7b

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Precommit success 587bc7b

@adnapibar
Copy link
Contributor

@nknize does it make sense to do this in small chunks e.g. remove a specific 6.x version in one PR ?

@nknize
Copy link
Collaborator Author

nknize commented Jan 18, 2022

closing in favor of individual commits related to #1674

@nknize nknize closed this Jan 18, 2022
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.

4 participants