[
https://issues.apache.org/jira/browse/HBASE-11039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated HBASE-11039:
-------------------------------------------
Attachment: HBASE-11039_v3_0.98.patch
Attaching a patch which would help to pass the user as a param using -u as the
arg followed by user name.
This would work in a cluster that has both ACL CP and VC together.
Still mvn verify part is not solved due to the issue already mentioned. Using
the IntegrationTestsDriver
{code}
./hbase org.apache.hadoop.hbase.IntegrationTestsDriver -r
.*IntegrationTestBigLinkedListWithVisibility.*
{code}
and
{code}
./hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedListWithVisibility
-u user3 Loop 1 1 20000 /tmp 1 10000
{code}
This IT would work. If both VC and ACL are not configured in the site.xml then
we may get errors as ACL table would not be available.
> [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
>
>
> 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)
