[ 
https://issues.apache.org/jira/browse/BEAM-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123048#comment-17123048
 ] 

Beam JIRA Bot commented on BEAM-5849:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it 
has been labeled "stale-P2". If this issue is still affecting you, we care! 
Please comment and remove the label. Otherwise, in 14 days the issue will be 
moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed 
explanation of what these priorities mean.


> allow the users to anticipate the support of features in the targeted runner
> ----------------------------------------------------------------------------
>
>                 Key: BEAM-5849
>                 URL: https://issues.apache.org/jira/browse/BEAM-5849
>             Project: Beam
>          Issue Type: Wish
>          Components: beam-model
>            Reporter: Etienne Chauchot
>            Priority: P2
>              Labels: stale-P2
>
> 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. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to