Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
From: <benedict.whittamsmith@thomsonreuters.com>
To: <user@hbase.apache.org>
Subject: Append Visibility Labels?
Thread-Topic: Append Visibility Labels?
Thread-Index: AdGVhpPJYoJgp5qJQfmT7ButEOezXAAEDZmA
Date: Wed, 13 Apr 2016 15:12:54 +0000
Message-ID: 
 <4C86198BF10EF549BC496C7F215A9CC70CBC6679@C111MFBLMBX07.ERF.thomson.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_4C86198BF10EF549BC496C7F215A9CC70CBC6679C111MFBLMBX07ER_"
MIME-Version: 1.0

--_000_4C86198BF10EF549BC496C7F215A9CC70CBC6679C111MFBLMBX07ER_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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 impleme=
nting 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 applyin=
g it to the relevant cells we've overwritten all the existing labels on tho=
se cells, destroying the permissioning of our older products. What to do?

One answer would be to append the new visibility label to the existing labe=
l 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 info=
rmation that may be privileged and/or confidential. If you are not an inten=
ded 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/>

--_000_4C86198BF10EF549BC496C7F215A9CC70CBC6679C111MFBLMBX07ER_--