kbuci commented on code in PR #18302:
URL: https://github.com/apache/hudi/pull/18302#discussion_r2943872647
##########
hudi-client/hudi-client-common/src/main/java/org/apache/hudi/config/HoodieWriteConfig.java:
##########
@@ -674,6 +675,35 @@ public class HoodieWriteConfig extends HoodieConfig {
.markAdvanced()
.withDocumentation("Number of heartbeat misses, before a writer is
deemed not alive and all pending writes are aborted.");
+ public static final ConfigProperty<Boolean> ROLLBACK_FAILED_CLUSTERING =
ConfigProperty
Review Comment:
Sure I can use that config name.
In our clustering table service runner, we currently want to rollback any
(potentially conflicting) clustering instant with an expired heartbeat,
regardless of how recent it is. So currently with our internal setup/build, we
in clustering runner we enable the config to allow rollback of failed
clustering writes, but we set hoodie.clustering.expiration.time.mins to 0
--
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]
