[jira] [Commented] (BEAM-12047) Create a URN convention for cross-language transforms

["Kenneth Knowles (Jira)" <ji...@apache.org>]

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

Kenneth Knowles commented on BEAM-12047:
----------------------------------------

I know there was a design doc about this, but why not just {{beam:kafka:read:v1}}?

> Create a URN convention for cross-language transforms
> -----------------------------------------------------
>
>                 Key: BEAM-12047
>                 URL: https://issues.apache.org/jira/browse/BEAM-12047
>             Project: Beam
>          Issue Type: New Feature
>          Components: beam-model, cross-language
>            Reporter: Chamikara Madhusanka Jayalath
>            Priority: P2
>
> Transform authors have to define URNs when defining new cross-language transforms.
> See here for documentation related to this: [https://beam.apache.org/documentation/programming-guide/#create-x-lang-transforms]
>  
> Some example URNs used today.
> Kafka read: "beam:external:java:kafka:read:v1"
> Kafka write: "beam:external:java:kafka:write:v1"
> SQL: "beam:external:java:sql:v1"
>  
> Currently this URN is defined by the cross-language transform author (or whoever coverts a given transform to a cross-language transform). They can choose arbitrary URNs.
>  
> This is OK as long as we only have few cross-language transforms and as long as we do not deploy transforms with conflicting URNs in the same expansion service but as usage of cross-language transforms increase we could run into conflicts due to this.
>  
> We should define a convention so that a cross-language transform author can define a URN that will not run into URNs selected by other cross-language transform authors. 
>  
>  
>  



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