[ https://issues.apache.org/jira/browse/HUDI-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Kudinkin updated HUDI-4692: ---------------------------------- Sprint: (was: 0.13.0 Final Sprint) > Clean up HoodieSparkSqlWriter > ----------------------------- > > Key: HUDI-4692 > URL: https://issues.apache.org/jira/browse/HUDI-4692 > Project: Apache Hudi > Issue Type: Improvement > Components: writer-core > Reporter: Alexey Kudinkin > Assignee: Alexey Kudinkin > Priority: Critical > > HoodieSparkSqlWriter has evolved over the years w/ layer on layers of logic > being stacked in it. It's reaching a point where it's virtually impossible to > understand interactions and number of permutations b/w different features. > One recent example is HUDI-4472. > We need to make sure that it's in a state where: > # Writing logic is easily traceable, and it's possible to understand how > different features might impact the write-path. > # Make sure that it's structured in a way allowing plugging in new > features/revisiting existing logic (for ex, allowing different path for > row-writing not only for bulk-insert but other operations as well, etc) > # -- This message was sent by Atlassian Jira (v8.20.10#820010)