You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Chamikara Madhusanka Jayalath (Jira)" <ji...@apache.org> on 2021/03/24 17:52:00 UTC
[jira] [Created] (BEAM-12047) Create aa URN convention for
cross-language transforms
Chamikara Madhusanka Jayalath created BEAM-12047:
----------------------------------------------------
Summary: Create aa 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: cross-language
Reporter: Chamikara Madhusanka Jayalath
Users have to define a URN when defining new cross-language transform.
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)