amoro icon indicating copy to clipboard operation
amoro copied to clipboard

[Bug]: Can't load metadata from HMS with unmatched hive version

Open tcodehuber opened this issue 2 years ago • 3 comments

What happened?

We can not get metadata from hive metastore when using unmatched hive version. In addition, there are no extra error/exception logs we can find. screenshot-20231122-104403 screenshot-20231122-104428

Affects Versions

master

What engines are you seeing the problem on?

AMS

How to reproduce

a. build from source code: mvn clean package -DskipTests -pl core,hive,ams,dist -am -Dcheckstyle.skip=true b. configure config.yaml, then bin/ams.sh start c. login ams, click related pages

hadoop stack version as belows: 111

Relevant log output

No response

Anything else

No response

Are you willing to submit a PR?

  • [ ] Yes I am willing to submit a PR!

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct

tcodehuber avatar Nov 22 '23 08:11 tcodehuber

Facing the same issue. HMS version: 2.3.6 https://github.com/apache/amoro/blob/master/amoro-core/src/main/java/org/apache/amoro/formats/iceberg/IcebergCatalog.java#L56

This functions is giving out empty namespaces. Thus, list_databases and list_tables is giving empty results.

The metastore does contain a lot of tables. However, I don't see any errors in the logs.

palash-goel avatar Aug 07 '24 13:08 palash-goel

Facing the same issue. HMS version: 2.3.6 https://github.com/apache/amoro/blob/master/amoro-core/src/main/java/org/apache/amoro/formats/iceberg/IcebergCatalog.java#L56

This functions is giving out empty namespaces. Thus, list_databases and list_tables is giving empty results.

The metastore does contain a lot of tables. However, I don't see any errors in the logs.

@palash-goel Can you build the binary release using mvn clean package -DskipTests -Phadoop2 and try to deploy the AMS again?

tcodehuber avatar Aug 07 '24 14:08 tcodehuber

This worked. Thank you so much!

palash-goel avatar Aug 13 '24 09:08 palash-goel

This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.

github-actions[bot] avatar Feb 10 '25 00:02 github-actions[bot]

This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale'

github-actions[bot] avatar Feb 25 '25 00:02 github-actions[bot]