[HUDI-7955] Account for WritableTimestampObjectInspector#getPrimitive… #11576
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…JavaObject discrepancies in Hive3 and Hive2
The invocation of
getPrimitiveJavaObject
returns a different implementation of timestamp in Hive3 and Hive2.java.sql.Timestamp
org.apache.hadoop.hive.common.type.Timestamp
Hudi common is compiled with Hive2, but Trino is using Hive3, causing the discrepancy between compile and runtime. When execution flow falls into this section of the code where the trigger conditions are listed below:
Error below will be thrown:
For more details on screenshots + SQL to reproduce, please refer to the JIRA ticket HUDI-7955.
Hive3
Hive2
Change Logs
Added Hive shim for
WritableTimestampObjectInspector#getPrimitiveJavaObject
.Impact
None
Risk level (write none, low medium or high below)
None
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".
ticket number here and follow the instruction to make
changes to the website.
Contributor's checklist