-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Query fails while masking table columns with different schema order #10370
Comments
Column masks should not be used as a replacement for generated columns. cc @kokosing |
@findepi maybe the There are cases that some attributes in the payload (that are not masked in the json) should be used to determine if other columns need to be masked.
|
It's actually intentional, and sometimes necessary, as the mask may depend on various dynamic conditions (e.g., you might need to mask some column based on whether the row contains data for some country -- indicated by some other column). However, it should only be able to see columns before masking is applied, and should not be able to generate columns that don't exist in the table. I believe both of these are true today. |
@findepi, there's no syntax change proposed here. What syntax needs to be reviewed (or was the label applied by mistake)? |
I don't find anything wrong in the examples above. It looks like a bug. Order of columns in the table should not matter here. |
etc/access_control-rules.json
GOOD:
BAD: (INTERNAL_ERROR)
The text was updated successfully, but these errors were encountered: