flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From medcv <...@git.apache.org>
Subject [GitHub] flink issue #6259: [FLINK-9679] Implement AvroSerializationSchema
Date Wed, 18 Jul 2018 21:26:08 GMT
Github user medcv commented on the issue:

    https://github.com/apache/flink/pull/6259
  
    @dawidwys  Thanks!
    
    As far as I dog on Confluent code, their api needs `subject` to retrieve the Schema Id
and version and it should be provided by consumer. 
    
    https://github.com/confluentinc/schema-registry/blob/master/client/src/main/java/io/confluent/kafka/schemaregistry/client/SchemaRegistryClient.java#L30
    
    Purpose of new commit is to address your first comments by removing `topic` name in the
serialization constructor and replace it with `subject`. So this way serializer doesn't need
to know about the `topic` name.
    
    If you still see issues with this approach I would appreciate it if you help me to find
a better solution.
    
    
     



---

Mime
View raw message