[
https://issues.apache.org/jira/browse/HBASE-11384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072908#comment-14072908
]
Anoop Sam John commented on HBASE-11384:
----------------------------------------
bq.The intention was that we would definitely get exception so wanted to
validate the type of error alone. Fine in adding a fail() also.
Ya. If we dont have the fail() then the test won't fail even with out this
patch !!
bq.but allowing HTD.setValue() then we have to expose that config outside.
I think mostly one want the setting to be same for all tables in a cluster.
That is why I would +1 a config setting. Even if one need table level setting,
now from 0.96 we have a way. So see whether we really want a setter in HTD
> [Visibility Controller]Check for users covering authorizations for every
> mutation
> ---------------------------------------------------------------------------------
>
> Key: HBASE-11384
> URL: https://issues.apache.org/jira/browse/HBASE-11384
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 0.98.3
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Fix For: 0.99.0, 0.98.5
>
> Attachments: HBASE-11384.patch, HBASE-11384_1.patch,
> HBASE-11384_2.patch, HBASE-11384_3.patch, HBASE-11384_4.patch
>
>
> As part of discussions, it is better that every mutation either Put/Delete
> with Visibility expressions should validate if the expression has labels for
> which the user has authorization. If not fail the mutation.
> Suppose User A is assoicated with A,B and C. The put has a visibility
> expression A&D. Then fail the mutation as D is not associated with User A.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
