kennknowles opened a new issue, #19153: URL: https://github.com/apache/beam/issues/19153
As part of our user experience improvement to attract new Beam users, I would like to suggest something: Today we only have the capability matrix to inform users about features support among runners. But, they might discover only when the pipeline runs, when they receive an exception, that a given feature is not supported by the targeted runner. I would like to suggest to translate the capability matrix into the API with annotations for example, so that, while coding, the user could know that, for now, a given feature is not supported on the runner he targets. =\> Eventually, the runner will need to decide if it can run a given pipeline so we need a validation process in the build process to inform the user if the pipeline is runable. Also it would require to specify the targeted runner. To avoid specifying it in the code (which is against Beam portability effort) we could specify it as a CLI parameter of the validation process. =\> As a complement having a IDE plugin to give surface information to the user will be good also. Imported from Jira [BEAM-5849](https://issues.apache.org/jira/browse/BEAM-5849). Original Jira may contain additional context. Reported by: echauchot. -- 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]
