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]
