shunping commented on PR #33414: URL: https://github.com/apache/beam/pull/33414#issuecomment-2557956733
> I don't think we want to introduce a new flag. The point of the `update_compatibility_version` is so that we don't have to make a new option (that both we have to handle and our users have to know about) for every update incompatible change, all you need to know is what version you used to originally launch your pipeline. I am fine with using a flag like that to avoid adding more options, as I also don't like too many options to remember too. However, I cannot deny that both the naming and where it is defined are a little bit confusing to me. We are somehow overloading "update" to both streaming and batch in this context. For batch, cx may only want to "create" a pipeline with existed code that works as before. There is no "update" on the pipeline from their perspective, only an update of Beam version. :) -- 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]
