Re: [PROPOSAL] allow the users to anticipate the support of features in the targeted runner.
it sounds like a good idea to me.
I would allow us to "automatize" our features coverage and give more
vision to our users.
On 04/10/2018 11:43, Etienne Chauchot wrote:
> Hi guys,
> 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.
> I know that the runner is only specified at pipeline runtime, and that
> adding code would be a leak of runner implementation and against
> portability. So it could be just informative annotations
> like @Experimental for example with no annotation processor.
Talend - http://www.talend.com