[Backport 2.x] Add recovery chunk size setting#14131
[Backport 2.x] Add recovery chunk size setting#14131opensearch-trigger-bot[bot] wants to merge 2 commits into
Conversation
Signed-off-by: Shubh Sahu <shubhvs@amazon.com> (cherry picked from commit 53ea952) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Looks like there's a breaking API change here @gbbafna @astute-decipher. Want to make sure we're ok with it?
|
❌ Gradle check result for 42b7e87: 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? |
Hi @dblock , this PR doesn't cause any breaking API change. It just adds a new setting Sorry, my bad. It is due to this PR only . We have removed a field However, would this cause other PRs's breaking changes workflow to fail as well ? In this case, how do we proceed ? |
|
The only question is whether there are users that may or may no rely on this setting out there. So what makes us be sure that |
|
Looks like I am wrong about the backwards incompatible change being ok, see #14105 (comment). cc: @andrross, how should this PR be solving it? |
…ettings.java Co-authored-by: Andrew Ross <andrross@amazon.com> Signed-off-by: Gaurav Bafna <85113518+gbbafna@users.noreply.github.com>
|
❌ Gradle check result for b058d55: 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? |
|
❌ Gradle check result for b058d55: 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? |
|
Closing in favor of #14161 |
Backport 53ea952 from #13997.