[
https://issues.apache.org/jira/browse/KAFKA-16257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17851941#comment-17851941
]
Fan Yang commented on KAFKA-16257:
----------------------------------
Hi [~gharris1727] , I thought about the class loading issue you mentioned in
the PR. And I have a question.
Suppose we have such data flow:
Kafka -> Avro Converter -> File Sink Connector -> Avro file.
In converter, it implements projecting strategy for customized logical schema.
In Connector, it gets the logical schema and calls SchemaProjector.project(),
the SchemaProjector delegates to the projecting strategy.
Connector and converter are loaded by different PluginClassLoader.
It works good. But do you think there are any safety issues with the solution
above?
> SchemaProjector should be extensible to logical types
> -----------------------------------------------------
>
> Key: KAFKA-16257
> URL: https://issues.apache.org/jira/browse/KAFKA-16257
> Project: Kafka
> Issue Type: New Feature
> Components: connect
> Reporter: Greg Harris
> Assignee: Fan Yang
> Priority: Minor
> Labels: needs-kip
>
> The SchemaProjector currently only supports projecting primitive Number
> types, and cannot handle common logical types as have proliferated in the
> Connect ecosystem.
> The SchemaProjector or a replacement should have the ability to extend it's
> functionality to support these logical types.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
