Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 702D21029D for ; Thu, 3 Apr 2014 08:41:20 +0000 (UTC) Received: (qmail 2549 invoked by uid 500); 3 Apr 2014 08:41:19 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 2476 invoked by uid 500); 3 Apr 2014 08:41:18 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 2465 invoked by uid 99); 3 Apr 2014 08:41:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 08:41:18 +0000 Date: Thu, 3 Apr 2014 08:41:18 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10854) Multiple Row/VisibilityLabels visible while in the memstore MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-10854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958632#comment-13958632 ] Andrew Purtell commented on HBASE-10854: ---------------------------------------- bq. Tested all the above cases and the results are as expected. Great, +1 for commit > Multiple Row/VisibilityLabels visible while in the memstore > ----------------------------------------------------------- > > Key: HBASE-10854 > URL: https://issues.apache.org/jira/browse/HBASE-10854 > Project: HBase > Issue Type: Bug > Components: security > Affects Versions: 0.98.0 > Reporter: Matteo Bertozzi > Assignee: Anoop Sam John > Fix For: 0.99.0, 0.98.2 > > Attachments: HBASE-10854.patch > > > If we update the row multiple times with different visibility labels > we are able to get the "old version" of the row until is flushed > {code} > $ sudo -u hbase hbase shell > hbase> add_labels 'A' > hbase> add_labels 'B' > hbase> create 'tb', 'f1' > hbase> put 'tb', 'row', 'f1:q', 'v1', {VISIBILITY=>'A'} > hbase> put 'tb', 'row', 'f1:q', 'v1all' > hbase> put 'tb', 'row', 'f1:q', 'v1aOrB', {VISIBILITY=>'A|B'} > hbase> put 'tb', 'row', 'f1:q', 'v1aAndB', {VISIBILITY=>'A&B'} > hbase> scan 'tb' > row column=f1:q, timestamp=1395948168154, value=v1aAndB > 1 row > $ sudo -u testuser hbase shell > hbase> scan 'tb' > row column=f1:q, timestamp=1395948168102, value=v1all > 1 row > {code} > When we flush the memstore we get a single row (the last one inserted) > so the testuser get 0 rows now. > {code} > $ sudo -u hbase hbase shell > hbase> flush 'tb' > hbase> scan 'tb' > row column=f1:q, timestamp=1395948168154, value=v1aAndB > 1 row > $ sudo -u testuser hbase shell > hbase> scan 'tb' > 0 row > {code} -- This message was sent by Atlassian JIRA (v6.2#6252)