danny0405 opened a new pull request #13033:
URL: https://github.com/apache/flink/pull/13033


   ## What is the purpose of the change
   
   Supports a catalog that can read the kafka topics flexibly.
   The demo code:
   ```java
           String schemaRegistryURL = ...;
           Map<String, String> kafkaProps = ...;
           SchemaRegistryCatalog catalog = SchemaRegistryCatalog.builder()
                   .schemaRegistryURL(schemaRegistryURL)
                   .kafkaOptions(kafkaProps)
                   .dbName("myDB")
                   .build();
           tEnv.registerCatalog("myCatalog", catalog);
    
           // ---------- Consume stream from Kafka -------------------
    
           // Assumes there is a topic named 'transactions'
           String query = "SELECT\n" +
               " id, amount\n" +
               "FROM myCatalog.myDB.transactions";
   ```
   
   ## Brief change log
   
     - Add a new Catalog named `SchemaRegistryCatalog`
     - Add tests for the table attributes
   
   
   ## Verifying this change
   Added UTs.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): yes, schema registry 
client 5.4.2 -> 5.5.1
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? yes
     - If yes, how is the feature documented? not documented
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to