[
https://issues.apache.org/jira/browse/HBASE-11039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059584#comment-14059584
]
Andrew Purtell edited comment on HBASE-11039 at 7/12/14 1:50 AM:
-----------------------------------------------------------------
As soon as the 'mvn verify' case can work, we are good to go I think.
Here is some documentation on how the test cluster should be set up and
configured, and how the test should be executed, so it completes successfully.
Relevant part of my hbase-site:
{noformat}
<property>
<name>hbase.coprocessor.master.classes</name>
<value>org.apache.hadoop.hbase.security.access.AccessController,org.apache.hadoop.hbase.security.visibility.VisibilityController</value>
</property>
<property>
<name>hbase.coprocessor.regionserver.classes</name>
<value>org.apache.hadoop.hbase.security.access.AccessController</value>
</property>
<property>
<name>hbase.coprocessor.region.classes</name>
<value>org.apache.hadoop.hbase.security.access.AccessController,org.apache.hadoop.hbase.security.visibility.VisibilityController,org.apache.hadoop.hbase.security.token.TokenProvider</value>
</property>
{noformat}
I'm running the daemons under the 'hbase' user, so the superuser is 'hbase'.
The available test user account is 'apurtell'.
The test needs to be run as the superuser user, 'hbase'.
Then I run the test, following the example provided in an earlier comment on
this issue:
{noformat}
./bin/hbase
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedListWithVisibility -u
apurtell Loop 1 1 20000 /tmp 1 10000
{noformat}
was (Author: apurtell):
As soon as the 'mvn verify' case can work, we are good to go I think.
Here is some documentation on how the test cluster should be set up and
configured, and how the test should be executed, so it completes successfully.
Relevant part of my hbase-site:
{noformat}
<property>
<name>hbase.coprocessor.master.classes</name>
<value>org.apache.hadoop.hbase.security.access.AccessController,org.apache.hadoop.hbase.security.visibility.VisibilityController</value>
</property>
<property>
<name>hbase.coprocessor.regionserver.classes</name>
<value>org.apache.hadoop.hbase.security.access.AccessController</value>
</property>
<property>
<name>hbase.coprocessor.region.classes</name>
<value>org.apache.hadoop.hbase.security.access.AccessController,org.apache.hadoop.hbase.security.visibility.VisibilityController,org.apache.hadoop.hbase.security.token.TokenProvider</value>
</property>
{noformat}
I'm running the daemons under the 'hbase' user, so the superuser is 'hbase'.
I run the test as the user 'apurtell':
First I grant 'apurtell' all global privs because I don't want to be a problem:
{noformat}
Version 0.98.4-SNAPSHOT, raa7a0ce8395cf9ad5c99028463c619df952e14b8, Fri Jul 11
17:49:11 PDT 2014
hbase(main):001:0> grant 'apurtell', 'RWXCA'
0 row(s) in 1.5130 seconds
{noformat}
Then I run the test, following the example provided in an earlier comment on
this issue:
{noformat}
./bin/hbase
org.apache.hadoop.hbase.test.IntegrationTestBigLinkedListWithVisibility -u
apurtell Loop 1 1 20000 /tmp 1 10000
{noformat}
> [VisibilityController] Integration test for labeled data set mixing and
> filtered excise
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-11039
> URL: https://issues.apache.org/jira/browse/HBASE-11039
> Project: HBase
> Issue Type: Test
> Affects Versions: 0.98.1
> Reporter: Andrew Purtell
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 0.99.0, 1.0.0, 0.98.4
>
> Attachments: HBASE-11039_ITBLL_v1.patch, HBASE-11039_v3_0.98.patch,
> HBASE-11039_v4_0.98.patch
>
>
> Create an integration test for the VisibilityController that:
> 1. Create several tables of test data
> 2. Assign a set of auths to each table. Label all entries in the table with
> appropriate visibility expressions. Insure that some data in every table
> overlaps with data in other tables at common row/family/qualifier
> coordinates. Generate data like ITBLL so we can verify all data present later.
> 3. Mix the data from the different tables into a new common table
> 4. Verify for each set of auths defined in step #2 that all entries found in
> the source table can be found in the common table. Like the ITBLL
> verification step but done N times for each set of auths defined in step #2.
> 5. Choose one of the source tables. Get its set of auths. Perform a deletion
> with visibility expression from the common table using those auths.
> 6. Verify that no data in the common table with the auth set chosen in #5
> remains. A simple row count with the set of auths chosen in #5 that should
> return 0.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
