[
https://issues.apache.org/jira/browse/HUDI-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Y Ethan Guo updated HUDI-8467:
------------------------------
Priority: Blocker (was: Critical)
> Deprecate Auto commit enabled flow in write client
> --------------------------------------------------
>
> Key: HUDI-8467
> URL: https://issues.apache.org/jira/browse/HUDI-8467
> Project: Apache Hudi
> Issue Type: Improvement
> Components: writer-core
> Reporter: sivabalan narayanan
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> We can either auto commit automatically or not while writing via write
> client.
> [https://github.com/apache/hudi/blob/b216d794c0d902c10106704ddacff775c83f64bb/hudi-client/hudi-client-common/src/main/java/org/apache/hudi/table/action/commit/BaseCommitActionExecutor.java#L179]
>
>
> This has caused some divergence b/w two flows. Most production use cases are
> using auto commit "disabled" flow like spark batch writers and streaming
> writers. Auto commit enabled flow was introduced in the beginning when some
> early adopters were using write client directly. But we have come a long way
> from there.
>
> Its better we get rid of the auto commit enabled flow and have just 1 way of
> committing using write client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
