singhpk234 commented on code in PR #13810:
URL: https://github.com/apache/iceberg/pull/13810#discussion_r2301586926
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -960,6 +960,15 @@ paths:
schema:
type: string
enum: [ all, refs ]
+ - in: query
+ name: referenced-by
+ description:
+ The fully qualified name of the view (i.e namespace name and view
name) that referenced the table.
+
+ nested namespaces are separated by a unit separator (`0x1F`) byte.
Review Comment:
Thanks for the feedbacks and interest Sun !
My understanding on these are following :
> exposing row-filters or column masks securely depends on the assumption
that the client is trusted to apply them faithfully and not leak security
context
> What are your thoughts on introducing the concept of “trust”
It would be great if we could add this to the specification, specially not
leak security context, as for example my security predicate was country != USA
now if I do `EXPLAIN` i can now see there is country USA in the table and its
not ideal, from what I have researched commercial offerings such as SNOW / DBx
support plan redaction when security predicates are involved but what i am
aware TRINO doesn't. So for uniform experience it would be great if we could
define something and **_know the take of community_** on this ! Looking forward
to your proposal and discussion.
> we have the concept agreed on by the community, perhaps we could reference
it in the OPEN API yaml
Sure thing ! Though not for this particular proposal (for adding
referenced-by), but definitely something to look forward to for the FGAC
discussion !
Thank you again for raising this discussions !
--
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]
