-
Notifications
You must be signed in to change notification settings - Fork 4.8k
HIVE-29383: Iceberg: [V3] Add support for timestamp with nanosecond precession #6242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
5740926 to
76ac1b7
Compare
|
On your latest changes, select * is working now in beeline ✅, but casting to string is not working ❌, you can check by adding |
|
fixed the cast query and added in the q file |
Any thoughts on this comments? This is what I meant: |
|
@ayushtkn , can you please check if these changes make sense addendum.patch |
|
|
@ayushtkn , i have found another issue with the join on nanosecond timestamp (specific to MapJoin). If you agree, can we create a new sub-JIRA to fix new issues? |
|
Let me know the issue & I can try fix it or we can create a followup once we merge this. Should get some review as well, if folks are ok with the approach as well. We created a bunch of empty classes. Will try ask someone next week. I need to test it myself as well post holidays. Was just trying as a POC. The idea was to keep the delta as low as possible and leverage TIMESTAMP mostly, I think have deviated bit from my initial plan. |
|



What changes were proposed in this pull request?
Add support for timestamp with nanosecond precession
Why are the changes needed?
To support the new timestamp types introduced as part of iceberg v3
Does this PR introduce any user-facing change?
Yes, users can leverage timestamp_ns & timestamptz_ns data types for iceberg v3 tables
How was this patch tested?
UT