You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/06/13 04:56:53 UTC

[GitHub] [flink] dianfu opened a new pull request #8719: [FLINK-12767][python] Support user defined connectors/format

dianfu opened a new pull request #8719: [FLINK-12767][python] Support user defined connectors/format
URL: https://github.com/apache/flink/pull/8719
 
 
   ## What is the purpose of the change
   
   *Currently, only built-in connectors such as FileSystem/Kafka/ES are supported and only built-in formats such as OldCSV/JSON/Avro/CSV/ are supported. There is no way provided for users to use other connectors or formats in Python Table API. We should provide a convenient way for the connectors/formats that are not built-in supported. This pull request adds this support.*
   
   ## Brief change log
   
     - *Add CustomFormatDescriptor and CustomConnectorDescriptor in flink-table-common*
     - *Add the corresponding CustomFormatDescriptor and CustomConnectorDescriptor in flink-python*
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
     - *Added tests CustomFormatDescriptorTests and CustomConnectorDescriptorTests*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - 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, Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable)
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services