[ 
https://issues.apache.org/jira/browse/KAFKA-8163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16841564#comment-16841564
 ] 

Marc Löhe commented on KAFKA-8163:
----------------------------------

I experience the same problem with Connect 2.2 and Debezium 0.9.5.

Not sure if this is implemented Connect or Debezium, though?

> SetSchemaMetadata SMT does not apply to nested types
> ----------------------------------------------------
>
>                 Key: KAFKA-8163
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8163
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: pierre bouvret
>            Priority: Minor
>
> In a schema, I want to replace the pg.public.foufou namespace by the 
> pg.other_public.foufou namespace.
> The schema (Envelope from Debezium) has an inner definition for Value also 
> belonging to the pg.public.foufou namespace
> Using a SetSchemaMetadata SMT, the inner namespace is not updated.
> {quote}{
>     "type": "record",
>     "name": "Envelope",
>     "namespace": "pg.other_public.foufou",
>     "fields": [
>         {
>             "name": "before",
>             "type": [
>                 "null",
>                 {
>                     "type": "record",
>                     "name": "Value",
>                     "namespace": "pg.public.foufou",
>                     "fields": [
>                         {
>                             "name": "id",
>                             "type": "int"
>                         },
>                         {
>                             "name": "lib",
>                             "type": [
>                                 "null",
>                                 "string"
>                             ],
>                             "default": null
>                         }
>                     ],
>                     "connect.name": "pg.public.foufou.Value"
>                 }
>             ],
>             "default": null
>         },{quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to