You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Artsem Semianenka (JIRA)" <ji...@apache.org> on 2019/04/19 15:47:00 UTC

[jira] [Commented] (FLINK-12256) Implement KafkaReadableCatalog

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

Artsem Semianenka commented on FLINK-12256:
-------------------------------------------

I've created the first draft of the[ design document|https://docs.google.com/document/d/14thwgV2RY1AA9KgYztv_kLYSz4K1TckJ-YiGfkB5650/edit?usp=sharing]. Please let's continue the discussion in this ticket or in comments in Google Docs 

> Implement KafkaReadableCatalog
> ------------------------------
>
>                 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: Artsem Semianenka
>            Priority: Major
>
>  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
(v7.6.3#76005)