[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes
[ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ethan Guo updated HUDI-677: --- Fix Version/s: 1.1.0 > Abstract/Refactor all transaction management logic into a set of classes > - > > Key: HUDI-677 > URL: https://issues.apache.org/jira/browse/HUDI-677 > Project: Apache Hudi > Issue Type: Improvement > Components: code-quality >Reporter: Vinoth Chandar >Assignee: Vinoth Chandar >Priority: Major > Labels: help-requested > Fix For: 1.1.0 > > > Hudi's timeline management code sits in HoodieActiveTimeline and > HoodieDefaultTimeline classes, taking action through the four stages : > REQUESTED, INFLIGHT, COMPLETED, INVALID. > For sake of better readability and maintenance, we should look into > reimplementing these as a state machine. > Note that this is better done after organizing the action execution classes > (as in HUDI-756) in hudi-client -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes
[ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-677: Labels: help-requested (was: ) > Abstract/Refactor all transaction management logic into a set of classes > - > > Key: HUDI-677 > URL: https://issues.apache.org/jira/browse/HUDI-677 > Project: Apache Hudi > Issue Type: Improvement > Components: Code Cleanup >Reporter: Vinoth Chandar >Assignee: Vinoth Chandar >Priority: Major > Labels: help-requested > > Hudi's timeline management code sits in HoodieActiveTimeline and > HoodieDefaultTimeline classes, taking action through the four stages : > REQUESTED, INFLIGHT, COMPLETED, INVALID. > For sake of better readability and maintenance, we should look into > reimplementing these as a state machine. > Note that this is better done after organizing the action execution classes > (as in HUDI-756) in hudi-client -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes
[ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-677: Labels: (was: help-requested help-wanted) > Abstract/Refactor all transaction management logic into a set of classes > - > > Key: HUDI-677 > URL: https://issues.apache.org/jira/browse/HUDI-677 > Project: Apache Hudi > Issue Type: Improvement > Components: Code Cleanup >Reporter: Vinoth Chandar >Assignee: Vinoth Chandar >Priority: Major > > Hudi's timeline management code sits in HoodieActiveTimeline and > HoodieDefaultTimeline classes, taking action through the four stages : > REQUESTED, INFLIGHT, COMPLETED, INVALID. > For sake of better readability and maintenance, we should look into > reimplementing these as a state machine. > Note that this is better done after organizing the action execution classes > (as in HUDI-756) in hudi-client -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes
[ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-677: Labels: help-requested help-wanted (was: help-wanted) > Abstract/Refactor all transaction management logic into a set of classes > - > > Key: HUDI-677 > URL: https://issues.apache.org/jira/browse/HUDI-677 > Project: Apache Hudi (incubating) > Issue Type: Improvement > Components: Code Cleanup >Reporter: Vinoth Chandar >Assignee: Vinoth Chandar >Priority: Major > Labels: help-requested, help-wanted > > Hudi's timeline management code sits in HoodieActiveTimeline and > HoodieDefaultTimeline classes, taking action through the four stages : > REQUESTED, INFLIGHT, COMPLETED, INVALID. > For sake of better readability and maintenance, we should look into > reimplementing these as a state machine. > Note that this is better done after organizing the action execution classes > (as in HUDI-756) in hudi-client -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes
[ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-677: Parent: (was: HUDI-408) Issue Type: Improvement (was: Sub-task) > Abstract/Refactor all transaction management logic into a set of classes > - > > Key: HUDI-677 > URL: https://issues.apache.org/jira/browse/HUDI-677 > Project: Apache Hudi (incubating) > Issue Type: Improvement > Components: Code Cleanup >Reporter: Vinoth Chandar >Assignee: Vinoth Chandar >Priority: Major > Labels: help-wanted > > Hudi's timeline management code sits in HoodieActiveTimeline and > HoodieDefaultTimeline classes, taking action through the four stages : > REQUESTED, INFLIGHT, COMPLETED, INVALID. > For sake of better readability and maintenance, we should look into > reimplementing these as a state machine. > Note that this is better done after organizing the action execution classes > (as in HUDI-756) in hudi-client -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes
[ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-677: Fix Version/s: (was: 0.6.0) > Abstract/Refactor all transaction management logic into a set of classes > - > > 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: Vinoth Chandar >Priority: Major > Labels: help-wanted > > Hudi's timeline management code sits in HoodieActiveTimeline and > HoodieDefaultTimeline classes, taking action through the four stages : > REQUESTED, INFLIGHT, COMPLETED, INVALID. > For sake of better readability and maintenance, we should look into > reimplementing these as a state machine. > Note that this is better done after organizing the action execution classes > (as in HUDI-756) in hudi-client -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes
[ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balaji Varadarajan updated HUDI-677: Labels: help-wanted (was: ) > Abstract/Refactor all transaction management logic into a set of classes > - > > 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: Vinoth Chandar >Priority: Major > Labels: help-wanted > Fix For: 0.6.0 > > > Hudi's timeline management code sits in HoodieActiveTimeline and > HoodieDefaultTimeline classes, taking action through the four stages : > REQUESTED, INFLIGHT, COMPLETED, INVALID. > For sake of better readability and maintenance, we should look into > reimplementing these as a state machine. > Note that this is better done after organizing the action execution classes > (as in HUDI-756) in hudi-client -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes
[ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-677: Description: Hudi's timeline management code sits in HoodieActiveTimeline and HoodieDefaultTimeline classes, taking action through the four stages : REQUESTED, INFLIGHT, COMPLETED, INVALID. For sake of better readability and maintenance, we should look into reimplementing these as a state machine. Note that this is better done after organizing the action execution classes (as in HUDI-756) in hudi-client was: 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.. > Abstract/Refactor all transaction management logic into a set of classes > - > > 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: Vinoth Chandar >Priority: Major > Fix For: 0.6.0 > > > Hudi's timeline management code sits in HoodieActiveTimeline and > HoodieDefaultTimeline classes, taking action through the four stages : > REQUESTED, INFLIGHT, COMPLETED, INVALID. > For sake of better readability and maintenance, we should look into > reimplementing these as a state machine. > Note that this is better done after organizing the action execution classes > (as in HUDI-756) in hudi-client -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes
[ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-677: Summary: Abstract/Refactor all transaction management logic into a set of classes (was: Abstract/Refactor all transaction management logic into a set of classes from HoodieWriteClient) > Abstract/Refactor all transaction management logic into a set of classes > - > > 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: Vinoth Chandar >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.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HUDI-677) Abstract/Refactor all transaction management logic into a set of classes from HoodieWriteClient
[ https://issues.apache.org/jira/browse/HUDI-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar updated HUDI-677: Description: 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.. > 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.. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
