perf: optimize rollback validation by checking lazy rollback policy before clustering validation

[suryaprasanna]

Describe the issue this Pull Request addresses

This PR optimizes the rollback validation process by reordering conditional checks to avoid unnecessary file I/O operations. Currently, determining whether an instant is a clustering instant requires opening and reading the .requested file. By checking if the lazy rollback is enabled first, we can skip the expensive clustering instant validation for lazy rollback scenarios.

Summary and Changelog

Improves rollback performance by reducing unnecessary file reads during validation.

Changes:

• Moved lazy rollback policy check (config.getFailedWritesCleanPolicy().isEager()) earlier in the validation flow
• Restructured validateRollbackCommitSequence() to only execute when needed (eager clean policy on non-metadata tables)

Impact

Minor performance improvement for rollback operations when lazy rollback is enabled. No API changes or breaking changes.

Risk Level

none - This is a code restructuring that maintains the same validation logic but changes the order of execution to optimize performance. The validation behavior remains unchanged.

Documentation Update

None. This is an internal optimization with no user-facing changes or new configurations.

Contributor's checklist

• Read through contributor's guide
• Enough context is provided in the sections above
• Adequate tests were added if applicable

[hudi-bot]

CI report:

• 0f11821 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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