singhpk234 commented on code in PR #13879:
URL: https://github.com/apache/iceberg/pull/13879#discussion_r2407491089
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -3260,6 +3260,71 @@ components:
additionalProperties:
type: string
+ ReadRestrictions:
+ type: object
+ description: >
+ Read restrictions for a table, including projection and row filter
expressions, according to the current schema.
+
+ A client MUST enforce the restrictions defined in this object when
reading data
+ from the table.
+
+ These restrictions apply only to the authenticated principal, user,
or account
+ associated with the client. They MUST NOT be interpreted as global
policy and
+ MUST NOT be applied beyond the entity identified by the
Authentication header
+ (or other applicable authentication mechanism).
+ properties:
+ required-projection:
Review Comment:
Thank you for the feedbacks Alex,
- The intentions was to make this like the project node of a typical query
planner hence the word required projection
- Intention was to make them as close as alias, later down the line (when
UDF's are ratified) we want to reference them here as well, transforms are a
bit overloded in iceberg in general tbh hence this
- IMHO array is a bit easy to reason as it's the projectList of the Project
node, the column name => Term is a bit tricky with cases like timetravel and
specially on a schema evolved columns, specially after this
https://github.com/apache/iceberg/pull/13879#issuecomment-3336612163 hence i
would say projectList
Please let me know your thoughts considering above.
--
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]
