Subramanya-Veeregowda commented on issue #18064: URL: https://github.com/apache/beam/issues/18064#issuecomment-4273853842
I started looking into this issue and noticed that changing class names like "DataflowPipelineJob" or "FlinkRunnerResult" could introduce breaking API changes. Before proceeding, could you please clarify: - Should we avoid renaming public classes and instead focus on internal consistency? - Or is a broader refactor (including API changes) acceptable here? I’m happy to proceed once the expected scope is clarified. -- 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]
