Tamas Mate has posted comments on this change. ( http://gerrit.cloudera.org:8080/18837 )
Change subject: IMPALA-11429: Set table owner after creating an Iceberg table ...................................................................... Patch Set 5: (3 comments) http://gerrit.cloudera.org:8080/#/c/18837/5/fe/src/main/java/org/apache/impala/service/CatalogOpExecutor.java File fe/src/main/java/org/apache/impala/service/CatalogOpExecutor.java: http://gerrit.cloudera.org:8080/#/c/18837/5/fe/src/main/java/org/apache/impala/service/CatalogOpExecutor.java@3626 PS5, Line 3626: it has : // hardcoded that the nit: this part was fuzzy for me, maybe something like: "however, the table owner is hardcoded to be the user running the Iceberg process" http://gerrit.cloudera.org:8080/#/c/18837/5/fe/src/main/java/org/apache/impala/service/CatalogOpExecutor.java@3633 PS5, Line 3633: throw new ImpalaRuntimeException("Failed to set table owner after creating " + : "Iceberg table but the table has been created successfully", e); With Ranger enabled and a failing alter operation this table would be inaccessible for the user right? http://gerrit.cloudera.org:8080/#/c/18837/5/tests/query_test/test_iceberg.py File tests/query_test/test_iceberg.py: http://gerrit.cloudera.org:8080/#/c/18837/5/tests/query_test/test_iceberg.py@130 PS5, Line 130: pytest.skip() Wouldn't a time.sleep(5) solve the issue after create? -- To view, visit http://gerrit.cloudera.org:8080/18837 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: Impala-ASF Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I5cac198a4a53be3599cb582864ee5f8c269202c0 Gerrit-Change-Number: 18837 Gerrit-PatchSet: 5 Gerrit-Owner: Gabor Kaszab <gaborkas...@cloudera.com> Gerrit-Reviewer: Gergely Fürnstáhl <gfurnst...@cloudera.com> Gerrit-Reviewer: Impala Public Jenkins <impala-public-jenk...@cloudera.com> Gerrit-Reviewer: Tamas Mate <tma...@apache.org> Gerrit-Comment-Date: Fri, 19 Aug 2022 13:48:34 +0000 Gerrit-HasComments: Yes
