flaming-archer commented on issue #7046: URL: https://github.com/apache/gravitino/issues/7046#issuecomment-2833277769
> The following figure shows the components related to processing timestamps: <img alt="Image" width="659" src="https://private-user-images.githubusercontent.com/24897598/437897638-4572bf47-9af3-4f41-b364-6db1b085662a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDU3NDA1ODYsIm5iZiI6MTc0NTc0MDI4NiwicGF0aCI6Ii8yNDg5NzU5OC80Mzc4OTc2MzgtNDU3MmJmNDctOWFmMy00ZjQxLWIzNjQtNmRiMWIwODU2NjJhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA0MjclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNDI3VDA3NTEyNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE4ZDhhZWI3MjE4NDEwZTdlMTlhZDRkYWZmOTM0YWY0MWJjOWVhMjA1MjMyNTI2OTcxMTU1MTQxMWQ4NjA3N2MmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.DbO2KzY_lylLTkosqE_P00kbNd1zHQ9qLozMkYxZkFA"> > > From a usage perspective, the behavior of `Spark Gravitino Connector` should be consistent with `Spark Hive Connector`, as they are targeting Spark users; there should exist a type in Gravitino that has the same semantics as the `timestamp` type in HMS because Hive only supports `timestamp without timezone` (see details at[ the doc](https://hive.apache.org/docs/latest/languagemanual-types_27838462/#timestamps)), so the `timestamp without time zone` type in Gravitino should correspond to the `timestamp` type in HMS. When users attempt to use `timestamp with time zone` through Gravitino in the Hive catalog, an exception should be thrown. Testing has found that Spark SQL uses Spark Hive Catalog to create timestamp filed, and the type of Hive is displayed as timestamp. It's a bit difficult to accept if the Spark Gravitino connector doesn't support the spark timestamp type. The evns : Spark 3.3, hive3.x. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
