[GitHub] [iceberg] rdblue commented on issue #1908: Circular dependency when FileIO depends on table properties

[GitBox <gi...@apache.org>]

rdblue commented on issue #1908:
URL: https://github.com/apache/iceberg/issues/1908#issuecomment-744833410


   I'm not sure I consider those use cases valid.
   
   > use a different encryption mechanism for metadata and data, with encryption key stored as a table property
   
   Does this require a different `FileIO` and not different key metadata? Would the actual encryption scheme be different or just the keys? If so, isn't that a problem with the `EncryptionManager` and not the `FileIO`?
   
   > check permissions for read and write access based on an access control list stored in table properties
   
   This seems suspicious to me. Is this a scheme where the Iceberg library decides not to read a file because it doesn't  authorize itself?


----------------------------------------------------------------
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.

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