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

Guangbin Zhu commented on FLINK-12256:
--------------------------------------

I skimed over the KafkaReadableCatalog design document.

I think when registering a kafka  catalog , two parts of param are required:
 * kafka connection params (zookeeper.connect, bootstrap.servers, 
security.protocol etc) for connecting kafka cluster
 * CSR related (CSR address, subject etc) for describing schema and converting 
to Flink Table Data Type

I have a question:

How the consumer group.id/startup-mode stored in the catalog, is it static? I 
think group.id/startup-mode  are per application behavior params, each 
application has it's own group.id/startup-mode . How the catalog describe a 
table with group.id ? or the catalog does not store group.id/startup-mode , 
using as dynamic table options 
([FLIP-113|[https://cwiki.apache.org/confluence/display/FLINK/FLIP-113%3A+Supports+Dynamic+Table+Options+for+Flink+SQL]])?
  

 

> Implement Confluent Schema Registry Catalog
> -------------------------------------------
>
>                 Key: FLINK-12256
>                 URL: https://issues.apache.org/jira/browse/FLINK-12256
>             Project: Flink
>          Issue Type: New Feature
>          Components: Connectors / Kafka, Table SQL / Client
>    Affects Versions: 1.9.0
>            Reporter: Artsem Semianenka
>            Assignee: Bowen Li
>            Priority: Major
>             Fix For: 1.11.0
>
>         Attachments: Xnip2020-04-24_17-25-39.jpg
>
>
>  KafkaReadableCatalog is a special implementation of ReadableCatalog 
> interface (which introduced in 
> [FLIP-30|https://cwiki.apache.org/confluence/display/FLINK/FLIP-30%3A+Unified+Catalog+APIs]
>  )  to retrieve meta information such topic name/schema of the topic from 
> Apache Kafka and Confluent Schema Registry. 
> New ReadableCatalog allows a user to run SQL queries like:
> {code:java}
> Select * form kafka.topic_name  
> {code}
> without the need for manual definition of the table schema.



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

Reply via email to