-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Read manifest file Permission denied #10634
Comments
Hi,can you take a look at this issue for me! @nastra |
Could you provide more infomation? hive version and how do you config it to enable iceberg support |
The hive version is 3.1.3 |
How do you set accessing user , and have you ever switch user? |
jdbc use keytab, and i always use the same user if i create new table, it will show correct owner on table properties. |
when i restart hiveserver2, it will be normal, does it feel like a caching issue? |
This may be a issue of client pool in hive catalog. |
you can try to disable cache, set |
Hi, may I ask if reading the manifest file will use CachedClientPool? |
May I ask if this configuration is available in hive-site.xml? |
sorry, I confuse the problem. |
Hi, I find the ugi with a72f8bf5-5d93-405b-953e-a8fed8bfa6b6-m0.avro is B and other file is A |
Apache Iceberg version
1.4.3
Query engine
Hive3.1.3
Please describe the bug 馃悶
A user
execution queryselect * from iceberg_tb
and the error log is :
Caused by: org.apache.iceberg.exceptions.RuntimeIOException: Failed to open input stream for file: hdfs://hdfsHACluster/user/hive/warehouse/yc_iceberg.db/iceberg_tb/metadata/a72f8bf5-5d93-405b-953e-a8fed8bfa6b6-m0.avro at org.apache.hive.service.cli.operation.SQLOperation.getNextRowSet(SQLOperation.java:507) ... Caused by: org.apache.hadoop.security.AccessControlException: Permission denied: user=B, access=EXECUTE, inode="/user/hive/warehouse":hadoop:supergroup:drwx------
Strangely, the error message is that user B does not have permission.
Is it possible that it is related to ThreadPools.WORKER_POOL?
The text was updated successfully, but these errors were encountered: