You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2019/06/06 23:06:00 UTC
[jira] [Updated] (BEAM-7312) SchemaProvider can't be used with
dynamic types
[ https://issues.apache.org/jira/browse/BEAM-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismaël Mejía updated BEAM-7312:
-------------------------------
Status: Open (was: Triage Needed)
> SchemaProvider can't be used with dynamic types
> -----------------------------------------------
>
> Key: BEAM-7312
> URL: https://issues.apache.org/jira/browse/BEAM-7312
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Alex Van Boxel
> Assignee: Alex Van Boxel
> Priority: Major
>
> Looking at the java doc comment of SchemaProvider it hints at getting schema's from external system. But as the provider only access type this is in general impossible:
> Say you have 2 dynamic types, say Avro, as a java type they have both GenericRecord. Using the current interface it's impossible to make the difference between both dynamic types.
> As getting information from an external system I propose extending the Provider interface by adding an extra parameter to the interface. It would be a string with a URN.
> The URN could indicated for example
> * Pub/Sub subscription/topic
> * Kafka topic
> * whatever...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)