Thanks for the response
I'm pretty much tied to Phoenix 4.14.2-HBase-1.4 as we are using Amazon
EMR.
Looks like I can get the table using the same deprecated method that
Phoenix does:
tablename comes from the Mutation kvPair in the original fragment
HTableInterface hTable =
I ran into this too with other code. Make sure you’re on the same API.
HBase 2’s APIs changed heavily so you may have to do some googling for docs
to convert the above code into something usable in your version of the
HBase API.
Also for your original problem, I’m not sure if Apache Ranger
Hi Ankit
Getting stuck into this, but I am having trouble finding out how to
persist the ACL mutations
The updates to the mutations aren't being persisted as far as I can
tell. I see in your code you are using htable.batch().
I'm struggling to find a way to that object, I can get a PTable
>>would it be best to
use the HBase API for creating the data.
yes, you can use HBase API but you need to ensure that Phoenix Data type
APIs are used to
convert your column values into bytes and also while creating a composite
key(if applicable).
otherwise you would not be able to read data from
Hi Ankit
Thats very useful, many thanks.
Before I dive into using Phoenix (which has given me a torrid time over
the last few days!), is using Phoenix the best option given that I'm
doing some low level access to Cell information, or would it be best to
use the HBase API for creating the data.
>> If not possible I guess we have to look at doing something at the HBase
level.
As Josh said, it's not yet supported in Phoenix, Though you may try using
cell-level security of HBase with some Phoenix internal API and let us know
if it works for you.
Sharing a sample code if you wanna try.
/**
Hi Josh
Thought as much, thanks very much for taking the time to respond.
Appreciated
Simon
On Tue, 2019-09-03 at 11:19 -0400, Josh Elser wrote:
> Hi Simon,
>
> Phoenix does not provide any authorization/security layers on top of
> what HBase does (the thread on user@hbase has a suggestion
Hi Simon,
Phoenix does not provide any authorization/security layers on top of
what HBase does (the thread on user@hbase has a suggestion on cell ACLs
which is good).
I think the question you're ultimately asking is: no, the TenantID is
not an authorization layer. In a nut-shell, the
Hi
I'm working on a project where we have a combination of very sparse
data columns with added headaches of multi-tenancy. Hbase looks great
for the back end but I need to check that we can support the customer's
multi-tenancy requirements.
There are 2 that I'm struggling to find a definitive
