Fix Clone Index setting override for replication type

[luyuncheng]

Description

• Fix index setting override for replication type clone/shrink/split indices

Related Issues

we see there is previous pr and issues, but when we do clone/shirnk/split which is Resize Action it would make a Segment Replication Type indices to Document Replication Type.

#11417 @kotwanikunal
#11230

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

❌ Gradle check result for 2353b72: 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?

[github-actions]

❌ Gradle check result for 81aec5e: 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?

[github-actions]

❌ Gradle check result for 81aec5e: 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?

[github-actions]

❌ Gradle check result for ba11329: 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?

[gaobinlong]

@luyuncheng thanks for your work, please resolve the conflicts and ensure all checks can pass.

[github-actions]

❌ Gradle check result for 9d342b3: 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?

[github-actions]

❌ Gradle check result for 9e2205a: 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?

[github-actions]

❌ Gradle check result for 1682001: 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?

[gaobinlong]

❌ Gradle check result for 1682001: 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?

@luyuncheng you may need to add a skip version section to the yaml test file to make sure the yaml test can pass in a mixed version cluster.

[luyuncheng]

❌ Gradle check result for 1682001: 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?

@luyuncheng you may need to add a skip version section to the yaml test file to make sure the yaml test can pass in a mixed version cluster.

there is some IT for Resize AND SegmentReplication do not consider resize with same replication type, let me fixed IT

[luyuncheng]

@gaobinlong there is #11583 can limited replication change explicit, but i do not see any merge settings for resize indices, resize would changed the replication implicit? and i will change this PR. also i think the yamlRest is also needed for #11583,

[gaobinlong]

@gaobinlong there is #11583 can limited replication change explicit, but i do not see any merge settings for resize indices, resize would changed the replication implicit? and i will change this PR. also i think the yamlRest is also needed for #11583,

@dreamer-89 , please help to confirm this, do we allow setting a replication type different from the source index for the resize operations?(when cluster.index.restrict.replication.type is false), thank you!

[msfroh]

@dreamer-89 , please help to confirm this, do we allow setting a replication type different from the source index for the resize operations?(when cluster.index.restrict.replication.type is false), thank you!

@mch2 and I were looking at Clone Index together a few weeks ago. If I recall correctly it (and the other similar operations) creates a whole new index.

If you want the new index to use a different replication type, I don't think there's any technical reason why it wouldn't work, since the new index doesn't really have anything to do with the old index once it's created.