[
https://issues.apache.org/jira/browse/KYLIN-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201375#comment-16201375
]
jiatao.tao commented on KYLIN-2761:
-----------------------------------
Here's the commits:
https://github.com/apache/kylin/commit/a5a8def893644ca2b0bcdd8e34ef251d3c028455
https://github.com/apache/kylin/commit/06138f51b19a9b23b2fbb1665e5bae5f31e8f2b1
https://github.com/apache/kylin/commit/7640c946c7d9fbb5dac49c939b993030e5f90063
https://github.com/apache/kylin/commit/9af6a3f0cd2788b9df412c10c1ac237ff8b6d0ef
https://github.com/apache/kylin/commit/555617cb07362dbe80e53fdfc317d641acc25e19
https://github.com/apache/kylin/commit/2e845c21343e4143bfa5a3d6bb54842808c57275
> Table Level ACL
> ---------------
>
> Key: KYLIN-2761
> URL: https://issues.apache.org/jira/browse/KYLIN-2761
> Project: Kylin
> Issue Type: New Feature
> Affects Versions: v2.0.0
> Reporter: Joanna He
> Assignee: jiatao.tao
> Priority: Blocker
> Fix For: v2.2.0
>
>
> We are planning to introduce table level ACL to kylin. Table level ACL
> control whether user can query data from a table.
> Table will go under project so that table level ACL will be set at project by
> project basis. When an instance starts for the first time or upgrades from
> lower version, every user by default has access to all tables that have been
> loaded to the project. Admin can modify table level ACL. by removing user
> from a table’s access list, admin can disable user’s query access to the
> table.
> In several cases, a user’s table level ACL will be checked to ensure ACL
> integrity
> 1. When user visit insight page and browse tables, table that user has no
> access to under current project, will not be visible to the user.
> 2. When user’s query hit on a cube, the table level ACL on dependent
> tables for that user will be checked, if user has no access to any dependent
> table, query will be refused on that cube.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
