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

Elasticsearch 8.x to OpenSearch 2 Support #1071

Open
sumobrian opened this issue Oct 13, 2024 · 0 comments
Open

Elasticsearch 8.x to OpenSearch 2 Support #1071

sumobrian opened this issue Oct 13, 2024 · 0 comments
Labels
enhancement New feature or request MAv5.0

Comments

@sumobrian
Copy link
Collaborator

sumobrian commented Oct 13, 2024

Is your feature request related to a problem?

The lack of Elasticsearch 8 as a source prevents users from migrating directly from Elasticsearch 8 to OpenSearch 2.x. Elasticsearch 8 introduces several newer features and changes compared to earlier versions, which adds complexity to migrations.

What solution would you like?

Migration Assistant and all products within the migration repo will support migrating from Elasticsearch 8 to OpenSearch 2.x. This should include compatibility for features introduced in Elasticsearch 8, as well as the ability to perform metadata migrations, existing data migrations with RFS, and Capture and Replay functionalities.

Additionally, while not all transformations required for metadata, existing data, and live traffic will be supported "out of the box," there should be a mechanism for users performing such migrations to add custom transformations to the OpenSearch-Migrations transformation framework.

What alternatives have you considered?

Performing manual, step-by-step upgrades through intermediate versions of Elasticsearch or OpenSearch, but this is complex, time-consuming, and may introduce data inconsistency risks.

Do you have any additional context?

Migrating from Elasticsearch 8 introduces several considerations that were not as relevant for earlier versions:

  1. Security Features: Elasticsearch 8 brings enhanced security features, such as enforced security and TLS by default. Migration paths should account for transitioning these configurations.
  2. Versioned APIs: Elasticsearch 8 introduces versioned APIs, which could present challenges for clients expecting different API versions. Proper handling of API compatibility is needed.
  3. Breaking Changes: Elasticsearch 8 has several breaking changes in its API and core functionality. Compatibility layers or transformation tools may be needed to handle these differences.
  4. Lucene Version: Elasticsearch 8 uses a newer version of Lucene (likely Lucene 9). The migration process must ensure that index data from this Lucene version is handled correctly in OpenSearch.
  5. Deprecations: Elasticsearch 8 deprecates several features, so ensuring smooth handling of deprecated features in OpenSearch 2.x is essential.

The feature should account for these differences and ensure that indices and data created in Elasticsearch 8 are properly handled in OpenSearch 2.x without the need for significant manual intervention.

@sumobrian sumobrian added enhancement New feature or request untriaged and removed untriaged labels Oct 13, 2024
@sumobrian sumobrian changed the title [FEATURE] Add Support for Elasticsearch 8.x to migrate to the latest version of OpenSearch 2.<latest> Elasticsearch 8.x to OpenSearch 2 Support Oct 23, 2024
@sumobrian sumobrian added MAv5.0 and removed MAv3.0 labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request MAv5.0
Projects
Status: 6 Months - 1 Year
Development

No branches or pull requests

1 participant