[
https://issues.apache.org/jira/browse/FLINK-12256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17092215#comment-17092215
]
Jark Wu commented on FLINK-12256:
---------------------------------
Hi [~zhuguangbin86], thanks for the research.
Regarding to the CSR Avro, yes you are right. There is also an issue to track
this problem FLINK-16048. I think we should introduce a format for
"confluent-schema-registery-avro".
Regarding to the catalog, I think we can have a default startup-mode and
group-id when registering these tables in catalog. And yes, users can override
them using dynamc table options.
> 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)
