[
https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068035#comment-17068035
]
Vinoth Chandar commented on HUDI-677:
-------------------------------------
[~hongdongdong] We cannot break any existing APIs on the HoodieWriteClient, the
change has to be internal to this class..
How about I write up a concrete proposal, given I have context into the various
usage patterns/dependencies and you can add your thoughts on top and drive the
implementation?
> Abstract/Refactor all transaction management logic into a set of classes from
> HoodieWriteClient
> -----------------------------------------------------------------------------------------------
>
> Key: HUDI-677
> URL: https://issues.apache.org/jira/browse/HUDI-677
> Project: Apache Hudi (incubating)
> Issue Type: Sub-task
> Components: Code Cleanup
> Reporter: Vinoth Chandar
> Assignee: hong dongdong
> Priority: Major
> Fix For: 0.6.0
>
>
> Over time a lot of the core transaction management code has been split
> across various files in hudi-client.. We want to clean this up and present a
> nice interface..
> Some notes and thoughts and suggestions..
> <WIP>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
