-
Notifications
You must be signed in to change notification settings - Fork 3.3k
feat(iceberg): add namespace permissions #13414
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
feat(iceberg): add namespace permissions #13414
Conversation
d4f850e to
2ed08e4
Compare
Codecov ReportAttention: Patch coverage is 📢 Thoughts on this report? Let us know! |
9edf2b8 to
239a4b9
Compare
239a4b9 to
e9e7a30
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two optimizations that could be done if feasible.
I did not review the front end code, someone with that expertise should review it
| warehouse, | ||
| renameTableRequest.destination().namespace(), | ||
| DataOperation.MANAGE_TABLES, | ||
| false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion -- an exception that reports both privileges missing may be more useful if the user intends to fix it by adding the missing privileges. This may cause them to see one error at a time, the the second one will show up only after the first privilege is fixed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chakru-r incorporated this, could you please review?
...g/src/main/java/io/datahubproject/iceberg/catalog/rest/secure/AbstractIcebergController.java
Show resolved
Hide resolved
07ad6c9 to
508cb46
Compare
5f268c0 to
0ec0cdd
Compare
fc5766d to
0ec0cdd
Compare
933be93 to
63fa3b9
Compare
63fa3b9 to
6a8000d
Compare
a6f473e to
6a8000d
Compare
chriscollins3456
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the UI work here looks solid, no real concerns about that.
however, I want to make sure we've run this by the whole team since this is a pretty big change and could lead to some performance concerns.
also, right now we're just checking the direct container on the entity itself, but I think we should probably be consistent with domains and check parent containers of containers to see if a user has permission to do something
metadata-service/auth-impl/src/test/java/com/datahub/authorization/DataHubAuthorizerTest.java
Show resolved
Hide resolved
...ain/java/com/datahub/authorization/fieldresolverprovider/ContainerFieldResolverProvider.java
Show resolved
Hide resolved
Co-authored-by: Hyejin Yoon <[email protected]>
No description provided.