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/12/13 18:53:52 UTC

[GitHub] [flink] bowenli86 commented on a change in pull request #10543: [FLINK-15128][hive][doc] Document support for Hive timestamp type

bowenli86 commented on a change in pull request #10543: [FLINK-15128][hive][doc] Document support for Hive timestamp type
URL: https://github.com/apache/flink/pull/10543#discussion_r357784169
 
 

 ##########
 File path: docs/dev/table/hive/index.md
 ##########
 @@ -303,5 +303,6 @@ Currently `HiveCatalog` supports most Flink data types with the following mappin
 Note that:
 
 * Flink doesn't support Hive's `UNION` type is not supported
+* Hive's `TIMESTAMP` always has precision 9 and doesn't support other precisions. As a result, `HiveCatalog` cannot store `TIMESTAMP` columns whose precisions are not 9. Hive UDFs, on the other hand, can process `TIMESTAMP` values with a precision <= 9.
 
 Review comment:
   > As a result, `HiveCatalog` cannot store `TIMESTAMP` columns whose precisions are not 9
   
   sorry if I misunderstand it as the conversation has been quite complex so far - should be ok to store precision less or equal to 9, right? if it's say 6, users don't loose any data, we can just append more units to the original data, no?

----------------------------------------------------------------
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