[ 
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_1.patch

This patch does not do what is described here, but uses the 
IntegrationTestWithCellVisibilityLoadAndVerify to verify the deletes that 
happens.  May be we could make the deletes as configurable but in this patch 
the puts that are added are tracked and in between few deletes are added to the 
table.  The counters are retrieved based on the number of deletes that were 
performed while loading.

> [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_1.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