[ 
https://issues.apache.org/jira/browse/HBASE-11039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059696#comment-14059696
 ] 

ramkrishna.s.vasudevan commented on HBASE-11039:
------------------------------------------------

Thanks for the update Andy.  The above steps are the ones needed to run the 
test in a cluster.
Regarding the mvn verfiy, Even specifying an existing user does not solve the 
MR issue that we get.  
1) if the user exists on a real test cluster,
Still does not work.
 and 2) if the environment mapreduce based tests is set up correctly to account 
for the fake users
How to do this?  I tried adding ACL CP and VC CP in the setUpCluster() code, 
still it did not work.

> [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)

Reply via email to