[
https://issues.apache.org/jira/browse/HUDI-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17395012#comment-17395012
]
ASF GitHub Bot commented on HUDI-1771:
--------------------------------------
danny0405 edited a comment on pull request #3285:
URL: https://github.com/apache/hudi/pull/3285#issuecomment-894056174
> > For existing tables, this will cause issues with schema evol? or we only
do. it for new tables?
>
> Then it will break if someone upgrades from 0.8.0 to 0.9.0 on an existing
table with Flink? I understand the criticality of the feature. but wondering
how the upgrade process looks. Should we check with users and see?
To be more conservative, i add an option in the Flink options, and by
default, we do not add the operation metadata field, the streaming read of
flink only keeps the `UPSERT` semantics, if the option turns on, flink
streaming reader would emit all the changes.
--
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]
> Propagate CDC format for hoodie
> -------------------------------
>
> Key: HUDI-1771
> URL: https://issues.apache.org/jira/browse/HUDI-1771
> Project: Apache Hudi
> Issue Type: New Feature
> Components: Flink Integration
> Reporter: Danny Chen
> Assignee: Zheng yunhong
> Priority: Major
> Labels: pull-request-available, sev:normal
> Fix For: 0.9.0
>
>
> Like what we discussed in the dev mailing list:
> https://lists.apache.org/thread.html/r31b2d1404e4e043a5f875b78105ba6f9a801e78f265ad91242ad5eb2%40%3Cdev.hudi.apache.org%3E
> Keep the change flags make new use cases possible: using HUDI as the unified
> storage format for DWD and DWS layer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
