RE: Append Visibility Labels?

--Original Message- > From: Andrew Purtell [mailto:andrew.purt...@gmail.com] > Sent: 14 April 2016 19:12 > To: Whittam Smith, Benedict (TR Technology & Ops) > Cc: user@hbase.apache.org > Subject: Re: Append Visibility Labels? > > > > ​Actually the old product data does

Re: Append Visibility Labels?

essions. > > I guess we'd always use an 'OR' operator to add them. But what if we > wanted to remove a product/visibility label? > > -Original Message- > From: Andrew Purtell [mailto:andrew.purt...@gmail.com] > Sent: 13 April 2016 17:23 > To: user@hbase.apach

RE: Append Visibility Labels?

Subject: Re: Append Visibility Labels? I think Benedict was asking if it would be possible to add the capability. Actually the old product data doesn't have to die, Benedict. Set VERSIONS > 1 in your schema. The old cell version(s) carrying the old label set will still be there, accessi

Re: Append Visibility Labels?

I think Benedict was asking if it would be possible to add the capability. Actually the old product data doesn't have to die, Benedict. Set VERSIONS > 1 in your schema. The old cell version(s) carrying the old label set will still be there, accessible with a Scan that asks for N versions

Re: Append Visibility Labels?

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, wrote: > We sell data. A product can be defined as a permission to access data (at > a cell level).

Append Visibility Labels?

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