Why I'm doing:

If an add_partition operation is executed during the ALTER process, the ALTER operation will be canceled first. Therefore, the latest indexes will not include shadow indexes. but the schema's index may still contain shadow indexes, so the index check will fail and ingestion task will failed. [1] [2]

What I'm doing:

Skip the shadow index in the index check.

Fixes https://github.com/StarRocks/StarRocksTest/issues/8833

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.4
  • 3.3
  • 3.2
  • 3.1
  • 3.0

    ---

    This is an automatic backport of pull request [BugFix] Fix random table broker load fails when table has schema change #53041 done by Mergify.

Why I'm doing:

If an add_partition operation is executed during the ALTER process, the ALTER operation will be canceled first. Therefore, the latest indexes will not include shadow indexes. but the schema's index may still contain shadow indexes, so the index check will fail and ingestion task will failed. [1] [2]

What I'm doing:

Skip the shadow index in the index check.

Fixes https://github.com/StarRocks/StarRocksTest/issues/8833

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr