hbgstc123 opened a new pull request, #8950:
URL: https://github.com/apache/hudi/pull/8950
If flink offline table service fail after commit the compaction/clustering
instant, and a restart strategy is enable, then the completed instant will be
rerun.
Consequence is, if the completed instant happen to be archived, there will
be a file not found error; if not archived, then there will be duplicated base
files.
### Change Logs
check if the compaction/clustering instant is pending in active timeline
before running flink offline table service
### Impact
none
### Risk level (write none, low medium or high below)
none
### Documentation Update
_Describe any necessary documentation update if there is any new feature,
config, or user-facing change_
- _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](https://hudi.apache.org/contribute/developer-setup#website) to
make
changes to the website._
### Contributor's checklist
- [ ] Read through [contributor's
guide](https://hudi.apache.org/contribute/how-to-contribute)
- [ ] Change Logs and Impact were stated clearly
- [ ] Adequate tests were added if applicable
- [ ] CI passed
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]