Skip to content

docs: add S3 Repository report for v3.4.0#1771

Merged
tkykenmt merged 1 commit into
mainfrom
docs/s3-repository-v3.4.0
Jan 11, 2026
Merged

docs: add S3 Repository report for v3.4.0#1771
tkykenmt merged 1 commit into
mainfrom
docs/s3-repository-v3.4.0

Conversation

@tkykenmt
Copy link
Copy Markdown
Owner

Summary

This PR adds documentation for the S3 Repository enhancement in OpenSearch v3.4.0.

Changes in v3.4.0

The LEGACY_MD5_CHECKSUM_CALCULATION setting was added to the list of repository-s3 plugin settings, enabling it to be configured in opensearch.yml in addition to repository creation time. This completes the fix for S3-compatible storage compatibility that was introduced in v3.3.0.

Reports Created

  • Release report: docs/releases/v3.4.0/features/opensearch/s3-repository.md
  • Feature report: Updated docs/features/opensearch/s3-repository.md

Related PR

Related Issue

Closes #1712

@tkykenmt tkykenmt merged commit 3ec7e7d into main Jan 11, 2026
@tkykenmt tkykenmt deleted the docs/s3-repository-v3.4.0 branch January 11, 2026 07:12
@RamHaridas
Copy link
Copy Markdown

Hi, May I know that if there is a plan to deprecate this parameter from OpenSearch in near future versions?

@tkykenmt
Copy link
Copy Markdown
Owner Author

Hi @RamHaridas,

Based on my investigation of the OpenSearch GitHub repository, there is currently no announced plan to deprecate the LEGACY_MD5_CHECKSUM_CALCULATION parameter.

This setting was introduced in v3.3.0 (PR #19220) as a compatibility fix for S3-compatible storage providers that don't support the newer checksum trailing headers introduced in AWS SDK v2.30.0.

The deprecation of this parameter would likely depend on:

  1. S3-compatible storage providers adopting support for the newer checksum format
  2. OpenSearch project's decision on how long to maintain backward compatibility

For the most authoritative answer, I'd recommend asking directly in the OpenSearch community forums or creating a discussion in the OpenSearch repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants