singhpk234 commented on code in PR #13879:
URL: https://github.com/apache/iceberg/pull/13879#discussion_r2292134030
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -3260,25 +3260,25 @@ components:
additionalProperties:
type: string
- FineGrainedDataProtectionRules:
+ ReadRestrictions:
type: object
description: >
- Fine-grained data protection rules for a table as result of fine
grained policy evaluation at the catalog end based on the clients access rights.
-
- The client SHOULD use these rules to enforce fine-grained data
protection like column and row level access when reading data from the table.
+ Read Restrictions for a table including projection and row filter
expressions.
+ The client MUST enforce these rules to read data from the table.
Review Comment:
is this more from like capability POV like when catalog has a policy defined
but it doesn't know if the user's engine is trusted or not, or simply is
unaware of this field ?
in that case may be catalog can exercise 403 if there are finer grained
policies ? thoughts
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
