amogh-jahagirdar commented on code in PR #13879:
URL: https://github.com/apache/iceberg/pull/13879#discussion_r2289474477
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -3260,6 +3260,28 @@ components:
additionalProperties:
type: string
+ FineGrainedDataProtectionRules:
Review Comment:
How about simply `ProtectionPolicy`? It's a bit broad, but at the same time
I'm not sure we necessarily need to include "FineGrained" in the name and I
don't think we need to include "data" in the name either. The layer this
structre is embedded at, along with its fields indicate the granularity already
imo.
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -3260,6 +3260,28 @@ components:
additionalProperties:
type: string
+ FineGrainedDataProtectionRules:
+ 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.
Review Comment:
If we go with the above proposed name,
"Protection policy for a table including fields and row filter expressions.
The client should use these rules to project the specified columns and filter
the rows based on the expression"
>as result of fine grained policy evaluation at the catalog end based on the
clients access rights.
IMO this feels a bit overspecified and is implicit since it's the response
from a server
--
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]
