singhpk234 commented on PR #2048:
URL: https://github.com/apache/polaris/pull/2048#issuecomment-3097321676
> Managing FGAC rules and exposing protection instructions are two different
domains.
@snazy i understand that and in my design i want to leverage existing policy
store implementation to manage FGAC rules and then what you are calling as
protection instructions which is the result of policy evaluation is my view SQL
> The first is defined by the catalog and won't be part of Iceberg, the
latter (to be) defined by Iceberg.
I think we should not restrict our users to the limitations of Iceberg
expressions.
I am bit confused about your conclusion here, as in one place you are
suggesting iceberg needs to set standard for policy evaluation result but at
the same time we are discarding **_iceberg expression_** which are first class
citizens of iceberg world (which are portable and are used in different
language like iceberg rust / iceberg python ...) ? IMHO we should not go into
dialect specific SQL as it makes the evaluation harder and specially given that
we already have path forward with iceberg expressions and UDF's
--
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]
