[
https://issues.apache.org/jira/browse/HUDI-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019818#comment-17019818
]
Vinoth Chandar commented on HUDI-538:
-------------------------------------
>Otherwise, where the records wait to be writen come from?
Flink should have existing sources right.. for e.g Kafka, Pulsar.. Those would
continue to work. A good analogy is to think of the first integration with
Flink as similar to hudi-spark. you can write Spark programs consuming any
spark datasource today and write out hudi datasets, without using
deltastreamer, right?
> Restructuring hudi client module for multi engine support
> ---------------------------------------------------------
>
> Key: HUDI-538
> URL: https://issues.apache.org/jira/browse/HUDI-538
> Project: Apache Hudi (incubating)
> Issue Type: Wish
> Components: Code Cleanup
> Reporter: vinoyang
> Priority: Major
>
> Hudi is currently tightly coupled with the Spark framework. It caused the
> integration with other computing engine more difficult. We plan to decouple
> it with Spark. This umbrella issue used to track this work.
> Some thoughts wrote here:
> https://docs.google.com/document/d/1Q9w_4K6xzGbUrtTS0gAlzNYOmRXjzNUdbbe0q59PX9w/edit?usp=sharing
> The feature branch is {{restructure-hudi-client}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
