LXin96 opened a new pull request, #9956:
URL: https://github.com/apache/hudi/pull/9956

   currently, when flink job start async compaction on a mor table, the metrics 
in org.apache.hudi.metrics.FlinkCompactionMetrics 
   will update including pendingCompactionCount,compactionDelay,compactionCost. 
However, when a compaction failed need a metric to
   help user to know specific instant whether the final compaction has occured 
rollback.
   so attemp to add a metric named compactionFailedState in 
org.apache.hudi.sink.compact.CompactionCommitSink to record the instance
   happend rollback, which also means the current compaction failed in current 
time
   
   ### Change Logs
   
   add a metric named compactionFailedState in 
org.apache.hudi.sink.compact.CompactionCommitSink to record the instance
   happend rollback, which also means the current compaction failed in current 
time
   
   ### Impact
   
   no impact
   
   ### Risk level (write none, low medium or high below)
   
   low medium
   
   ### 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]

Reply via email to