hudi-bot opened a new issue, #15377:
URL: https://github.com/apache/hudi/issues/15377
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)
#
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-4692
- Type: Improvement
- Epic: https://issues.apache.org/jira/browse/HUDI-1297
--
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]
