You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2022/08/15 08:41:29 UTC

[GitHub] [iceberg] justusrk opened a new issue, #5527: Access Control in Iceberg

justusrk opened a new issue, #5527:
URL: https://github.com/apache/iceberg/issues/5527

   ### Query engine
   
   Spark
   
   ### Question
   
   I see that Iceberg is designed to be invisible. But I wanted to clarify this.
   
   Thinking about Access Control features - like users being allowed to access tables, columns, and rows.
   These features would be useful for GDPR Audits or maybe understanding data lineage.
   
   Should Iceberg ideally care about this? Or should this be handled by something else?
   
   If something else, then can you suggest what it could be? Like the query engine or something like Presto?
   
   I am curious where Data Governance features would be fitting.  Are there Iceberg implementations that do this already?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


[GitHub] [iceberg] github-actions[bot] closed issue #5527: Access Control in Iceberg

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #5527: Access Control in Iceberg
URL: https://github.com/apache/iceberg/issues/5527


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


[GitHub] [iceberg] github-actions[bot] commented on issue #5527: Access Control in Iceberg

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #5527:
URL: https://github.com/apache/iceberg/issues/5527#issuecomment-1452820876

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


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


[GitHub] [iceberg] github-actions[bot] commented on issue #5527: Access Control in Iceberg

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #5527:
URL: https://github.com/apache/iceberg/issues/5527#issuecomment-1426904726

   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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org


[GitHub] [iceberg] nastra commented on issue #5527: Access Control in Iceberg

Posted by GitBox <gi...@apache.org>.
nastra commented on issue #5527:
URL: https://github.com/apache/iceberg/issues/5527#issuecomment-1215072867

   Generally speaking, access control is something that engines should be implementing on top of Iceberg. Every engine has its own way of defining access control rules and enforcing them (even beyond Iceberg tables), so I think handling this in Iceberg across all engines might be quite difficult to achieve


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org