kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Roesler (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-9925) Non-key KTable Joining may result in duplicate schema name in confluence schema registry
Date Wed, 29 Apr 2020 22:36:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-9925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

John Roesler resolved KAFKA-9925.
---------------------------------
    Resolution: Fixed

> Non-key KTable Joining may result in duplicate schema name in confluence schema registry
> ----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9925
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9925
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.4.1
>            Reporter: Kin Siu
>            Assignee: John Roesler
>            Priority: Major
>             Fix For: 2.6.0, 2.4.2, 2.5.1
>
>
> The second half of issue Andy Bryant reported in KAFKA-9390 looks like still exist.
> When testing non-key join method without passing in "Named", I noticed that there are
schema subjects registered in confluent schema registry without consumer group Id still, 
> e.g. 
> {noformat}
> "KTABLE-FK-JOIN-SUBSCRIPTION-REGISTRATION-0000000005-topic-pk-key",
> "KTABLE-FK-JOIN-SUBSCRIPTION-REGISTRATION-0000000005-topic-fk-key",
> "KTABLE-FK-JOIN-SUBSCRIPTION-REGISTRATION-0000000005-topic-vh-value",
> "KTABLE-FK-JOIN-SUBSCRIPTION-REGISTRATION-0000000025-topic-pk-key",
> "KTABLE-FK-JOIN-SUBSCRIPTION-REGISTRATION-0000000025-topic-fk-key",
> "KTABLE-FK-JOIN-SUBSCRIPTION-REGISTRATION-0000000025-topic-vh-value"
> {noformat}
> Code in KTableImpl which constructed above naming :
> https://github.com/apache/kafka/blob/2.4.1/streams/src/main/java/org/apache/kafka/streams/kstream/internals/KTableImpl.java#L959
> When we have multiple topologies using foreignKey join and registered to same schema
registry, we can have a name clash, and fail to register schema. 
> In order to clean up these schema subjects, we will need to know the internal naming
of a consumer group's topology, which is not straightforward and error prone.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message