[HUDI-8537] Alter table operation no need to do rollback for failed writes

[zhuanshenbsj1]

Change Logs

When executing an alter-table- command, it is unnecessary to perform a clean operation.
This can mistakenly delete the regular files of the Flink stream-write task.

Impact

Describe any public API or user-facing feature change or any performance impact.

Risk level (write none, low medium or high below)

If medium or high, explain what verification was done to mitigate the risks.

Documentation Update

Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

• The config description must be updated if new configs are added or the default value of the configs are changed
• Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
  ticket number here and follow the instruction to make
  changes to the website.

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable
• CI passed

[danny0405]

There is no need to introduce new APIs in base write client, just use startCommit should be fine. And it's not for clean but for rollback of failed writes.

Usually we have concurrent modifications to one table tween Flink pipeline and this alter table job, one solution is to config the rollback of failed writes as lazy, but fix here to remove the rollback should also be feasible.

[zhuanshenbsj1]

There is no need to introduce new APIs in base write client, just use startCommit should be fine. And it's not for clean but for rollback of failed writes.

Usually we have concurrent modifications to one table tween Flink pipeline and this alter table job, one solution is to config the rollback of failed writes as lazy, but fix here to remove the rollback should also be feasible.

Alter table will involve rollback, clean, and archive, modify the paras will reduce the intrusiveness.

[hudi-bot]

CI report:

• b44d362 Azure: FAILURE

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build