[
https://issues.apache.org/jira/browse/KAFKA-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391536#comment-17391536
]
Jorge Machado edited comment on KAFKA-7883 at 8/2/21, 11:58 AM:
----------------------------------------------------------------
Hey, I think this should not be marked as workaround. Currently if we use this
it will replace the whole name of the table. If we are using this SMT together
on the jdbc connector and we have multiple tables it will generate the same
name for all tables :(
in teory we should only append to the current name. Example:
Avro Object name: "MaterialRaw"
Avro Namespace: "io.dmesh.avro"
on the transform imho we should have:
"transforms.AddNamespace.schema.name": "io.dmesh.avro" which it should generate
(io.dmesh.avro.MaterialRaw) instead of "io.dmesh.avro"
was (Author: jomach):
Hey, I think this should not be marked as workaround. Currently if we use this
it will replace the whole name of the table. If we are using this SMT together
on the jdbc connector and we have multiple tables it will generate the same
name for all tables :(
in teory we should only append to the current name. Example:
Avro Object name: "MaterialRaw"
Avro Namespace: "io.dmesh.avro"
on the transform imho we should have:
"transforms.AddNamespace.schema.name": "io.dmesh.avro" which it should generate
(io.dmesh.avro.MaterialRaw)
> Add schema.namespace support to SetSchemaMetadata SMT in Kafka Connect
> ----------------------------------------------------------------------
>
> Key: KAFKA-7883
> URL: https://issues.apache.org/jira/browse/KAFKA-7883
> Project: Kafka
> Issue Type: New Feature
> Components: KafkaConnect
> Affects Versions: 2.1.0
> Reporter: Jérémy Thulliez
> Priority: Minor
> Labels: features
>
> When using a connector with AvroConverter & SchemaRegistry, users should be
> able to specify the namespace in the SMT.
> Currently, only "schema.version" and "schema.name" can be specified.
> This is needed because if not specified, generated classes (from avro schema)
> are in the default package and not accessible.
> Currently, the workaround is to add a Transformation implementation to the
> connect classpath.
> It should be native.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
