bowenli86 opened a new pull request #8645: Support mapping BinaryType, 
VarBinaryType, CharType, VarCharType, and DecimalType between Flink and Hive in 
HiveCatalog
URL: https://github.com/apache/flink/pull/8645
 
 
   ## What is the purpose of the change
   
   This PR enables mapping BinaryType, VarBinaryType, CharType, VarCharType, 
and DecimalType between Flink and Hive in HiveCatalog, such that HiveCatalog 
can persist tables of these types in Hive metastore and later read them.
   
   This PR bases on https://github.com/apache/flink/pull/8639
   
   I will document the exact type mappings between Flink and Hive later on.
   
   ## Brief change log
   
   - added mapping for BinaryType, VarBinaryType, CharType, VarCharType, and 
DecimalType in HiveTypeUtil
   - added CharType, VarCharType, and DecimalType existing `testDataTypes()` 
unit test
   - added `testNonExactlyMatchedDataTypes()` for  BinaryType, VarBinaryType
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
   - added CharType, VarCharType, and DecimalType existing `testDataTypes()` 
unit test
   - added `testNonExactlyMatchedDataTypes()` for  BinaryType, VarBinaryType
   
   ## 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? (yes )
     - If yes, how is the feature documented? (docs)
   
   I will document the exact type mappings between Flink and Hive later on.
   

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

Reply via email to