[
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_ITBLL_v1.patch
Integration test case that verifies the description
-> Extends IntegrationTestBigLinkedList to verify the above scenario
-> Creates 3 tables and one common table with max versions = 3. Each table is
associated with a set of labels.
-> Loads data into the 3 tables (Note that the rowkeys are same in these 3
tables)
-> All the data is copied into the common table using the Copier MR utitility.
Here we ensure that from the table from where the data is copied we add that
table's visibility to the common table (thus forming 3 entries for the same
rowkey but different visibility exp)
-> The verification step verifies if the data in the 3 tables and the common
table is viewable passing corresponding auths.
-> We select one table's vis expression and issue a delete with that exp on the
common table. And ensure that after the delete, the rows corresponding to the
vis exp that was used for delete are not visible where as the rows with other
vis exp are visible.
We do this verification step by making deletes with all the set of vis exp and
finally ensuring that none of the rows are visible.
> [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, 0.98.4
>
> Attachments: HBASE-11039_ITBLL_v1.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)
