Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <4C86198BF10EF549BC496C7F215A9CC70CBC6679@C111MFBLMBX07.ERF.thomson.com>
References: 
 <4C86198BF10EF549BC496C7F215A9CC70CBC6679@C111MFBLMBX07.ERF.thomson.com>
Date: Wed, 13 Apr 2016 08:58:30 -0700
Message-ID: 
 <CALte62zaFjKDK8PM6emTK5aMy_gqH0pEUwvNYiLR-QxSkWcGFg@mail.gmail.com>
Subject: Re: Append Visibility Labels?
From: Ted Yu <yuzhihong@gmail.com>
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a114e58426006cb05305fd99a

--001a114e58426006cb05305fd99a
Content-Type: text/plain; charset=UTF-8

There is currently no API for appending Visibility Labels.

checkAndPut() only allows you to compare value, not labels.

On Wed, Apr 13, 2016 at 8:12 AM, <benedict.whittamsmith@thomsonreuters.com>
wrote:

> We sell data. A product can be defined as a permission to access data (at
> a cell level). Visibility Labels look like a very good candidate for
> implementing this model.
>
> The implementation works well until we create a new product over old data.
> We can set the visibility label for the new product but, whoops, by
> applying it to the relevant cells we've overwritten all the existing labels
> on those cells, destroying the permissioning of our older products. What to
> do?
>
> One answer would be to append the new visibility label to the existing
> label expressions on the cells with an 'OR'. But I'm not sure that's
> possible .. yet?
>
> Thanks,
>
> Ben
>
> ________________________________
>
> This e-mail is for the sole use of the intended recipient and contains
> information that may be privileged and/or confidential. If you are not an
> intended recipient, please notify the sender by return e-mail and delete
> this e-mail and any attachments. Certain required legal entity disclosures
> can be accessed on our website.<
> http://site.thomsonreuters.com/site/disclosures/>
>

--001a114e58426006cb05305fd99a--