[
https://issues.apache.org/jira/browse/CASSANDRA-9927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14680714#comment-14680714
]
Aleksey Yeschenko commented on CASSANDRA-9927:
----------------------------------------------
This is the desired logic, thank you.
That said, it doesn't build when applied to current cassandra-3.0 (can you fix
and rebase?)
Also the tests don't build. {{CQLAuthTester}} is missing, and, in general,
{{MaterializedViewAuthorizationTest}} doesn't belong where it was put.
All auth test currently belong to dtests,
[here|https://github.com/riptano/cassandra-dtest/blob/master/auth_test.py]. Can
you please convert the tests to dtests, where the other auth tests are?
> Security for MaterializedViews
> ------------------------------
>
> Key: CASSANDRA-9927
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9927
> Project: Cassandra
> Issue Type: Task
> Reporter: T Jake Luciani
> Assignee: Paulo Motta
> Labels: materializedviews
> Fix For: 3.0 beta 1
>
>
> We need to think about how to handle security wrt materialized views. Since
> they are based on a source table we should possibly inherit the same security
> model as that table.
> However I can see cases where users would want to create different security
> auth for different views. esp once we have CASSANDRA-9664 and users can
> filter out sensitive data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
