-
Notifications
You must be signed in to change notification settings - Fork 400
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
Iceberg Rest Unable to list tables for Hive Metastore with mixed Hive and Iceberg #6382
Comments
Seems Trino treat both Iceberg table and view to Trino tables. Hive catalog doesn't support view operations until 1.7.0 in apache/iceberg#9852, while Gravitino still uses Iceberg 1.5.2. There may be two solutions:
|
For solution one, suggest solution in IcebergCatalogWrapper, and welcome contribute.
|
another more general way is to export Iceberg server capabilities in Iceberg REST config endpoint, but this works in Iceberg 1.7 in apache/iceberg#10929. |
Thanks for the info. Seems like path to iceberg 1.7 is best for a long term approach. Somehow, if Gravitino needs to update JDK and make it work. |
Yes, this means Gravitino drops the support for JDK 8. |
@metalshanked , should you share the Trino version and Iceberg version you are using? Iceberg library does some compatibility works to avoid the unexcepted exceptions when listing views. |
Hi @FANNG1 . I was using the latest Trino version (469). I also tried with older version (459). Trino currently uses https://github.com/trinodb/trino/blob/3b53eee3c4cef19ea7c0aa8a20ca5987a7cd313e/pom.xml#L201 Future --> trinodb/trino#24713 |
Version
main branch
Describe what's wrong
I am using Trino to connect to Gravitino Iceberg Rest Server backed by a Hive Metastore.
The hive metastore can have native hive and iceberg tables both.
Below is the error in Trino and similar error in Gravitino logs too " Unable to process: hive is not support view"
Error message and/or stacktrace
How to reproduce
0.8.0
Additional context
No response
The text was updated successfully, but these errors were encountered: