-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Register s3.client.<client>.disable_chunked_encoding in repository-s3 node settings
#20161
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
base: main
Are you sure you want to change the base?
Register s3.client.<client>.disable_chunked_encoding in repository-s3 node settings
#20161
Conversation
WalkthroughAdded S3ClientSettings.DISABLE_CHUNKED_ENCODING to the plugin settings list, added a unit-test assertion for its presence, and adjusted S3ClientSettings.equals/hashCode to include maxSyncConnections and use primitive comparison for disableChunkedEncoding. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
🔇 Additional comments (2)
Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (2)
plugins/repository-s3/src/test/java/org/opensearch/repositories/s3/S3RepositoryPluginTests.java (1)
78-79: Keep the assertion, but avoid PR-specific comment wordingThe new assertion correctly verifies that
DISABLE_CHUNKED_ENCODINGis registered in the plugin settings. The inline comment (“New assertion for your bug fix”) is tied to this PR and doesn’t convey long-term intent; consider either removing it or replacing it with something descriptive like “ensure DISABLE_CHUNKED_ENCODING is registered as a node setting”.plugins/repository-s3/src/main/java/org/opensearch/repositories/s3/S3RepositoryPlugin.java (1)
366-367: Setting registration is correct; clean up the inline bug-fix commentIncluding
S3ClientSettings.DISABLE_CHUNKED_ENCODINGingetSettings()is the right fix to register this node setting. The comment “Fixed the bug in this line” is tied to this PR and doesn’t describe behavior; consider removing it or replacing it with a brief description of what the setting does (e.g., that it controls disabling HTTP chunked encoding for S3 clients).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
plugins/repository-s3/src/main/java/org/opensearch/repositories/s3/S3RepositoryPlugin.java(1 hunks)plugins/repository-s3/src/test/java/org/opensearch/repositories/s3/S3RepositoryPluginTests.java(1 hunks)
|
❌ Gradle check result for bfa670a: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
bfa670a to
217b8b7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
plugins/repository-s3/src/main/java/org/opensearch/repositories/s3/S3RepositoryPlugin.java (1)
366-368: DISABLE_CHUNKED_ENCODING registration is correct; consider cleaning up the commentThe addition of
S3ClientSettings.DISABLE_CHUNKED_ENCODINGtogetSettings()is exactly what’s needed for the node setting to be registered; behavior-wise this looks good.The inline comment
// Fixed the bug in this lineis not very descriptive and will age quickly. I’d either drop it or replace it with a comment about what the setting does instead of the historical note.For example, to just remove the historical comment:
- S3ClientSettings.SIGNER_OVERRIDE, - // Fixed the bug in this line - S3ClientSettings.DISABLE_CHUNKED_ENCODING, + S3ClientSettings.SIGNER_OVERRIDE, + S3ClientSettings.DISABLE_CHUNKED_ENCODING,Or, if you want a descriptive comment:
- S3ClientSettings.SIGNER_OVERRIDE, - // Fixed the bug in this line - S3ClientSettings.DISABLE_CHUNKED_ENCODING, + S3ClientSettings.SIGNER_OVERRIDE, + // Allows disabling AWS SDK chunked encoding for S3-compatible storage + S3ClientSettings.DISABLE_CHUNKED_ENCODING,
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
plugins/repository-s3/src/main/java/org/opensearch/repositories/s3/S3RepositoryPlugin.java(1 hunks)plugins/repository-s3/src/test/java/org/opensearch/repositories/s3/S3RepositoryPluginTests.java(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- plugins/repository-s3/src/test/java/org/opensearch/repositories/s3/S3RepositoryPluginTests.java
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: gradle-check
|
❌ Gradle check result for 217b8b7: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
217b8b7 to
8d42f07
Compare
|
❌ Gradle check result for 8d42f07: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
… settings Signed-off-by: Aman Gautam <amangautam2128@gmail.com>
8d42f07 to
068a2bd
Compare
|
CI didn't start due to a Jenkins trigger 403 / jq parsing error. |
|
❌ Gradle check result for 068a2bd: null Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
|
I ran the suite locally via The CI failure appears to be due to the Jenkins trigger issue (403 / jq parsing). |
Description
This PR registers the
s3.client.<client>.disable_chunked_encodingsetting in therepository-s3plugin.Currently, configuring the setting in
opensearch.ymlsuch as: