[X] I searched in the issues and found nothing similar.
Motivation
In some special cases, there maybe exists a situation that the CommitMessage is not empty but all the table files in it are empty, and if the job failover because of conflict, the job will be unrecoverable since the value of numCommitted will be greater than 1, so the job will failover infinite and can't be restore.
The exception is "This exception is intentionally thrown after committing the restored checkpoints. By restarting the job we hope that writers can start writing based on these new commits".
Solution
We can add an core options such as 'commit.ignore-empty-commit' to support commit an empty snapshot, and then we can restore the job normally.
Search before asking
Motivation
In some special cases, there maybe exists a situation that the CommitMessage is not empty but all the table files in it are empty, and if the job failover because of conflict, the job will be unrecoverable since the value of numCommitted will be greater than 1, so the job will failover infinite and can't be restore.
The exception is "This exception is intentionally thrown after committing the restored checkpoints. By restarting the job we hope that writers can start writing based on these new commits".
Solution
We can add an core options such as 'commit.ignore-empty-commit' to support commit an empty snapshot, and then we can restore the job normally.
Anything else?
No response
Are you willing to submit a PR?