[
https://issues.apache.org/jira/browse/BEAM-12047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435579#comment-17435579
]
Beam JIRA Bot commented on BEAM-12047:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Chamikara Madhusanka Jayalath
> Priority: P2
> Labels: stale-assigned
>
> 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)
