In addition to the above, in our 3.1/4.1 release, you can pass through
the principal and keytab file on the connection URL to connect to
different secure clusters, like this:
DriverManager.getConnection("jdbc:phoenix:h1,h2,h3:2181:user/principal:/user.keytab");
The full URL is now of the form
jdbc:phoenix:<quorom>:<port>:<rootNode>:<principal>:<keytabFile>
where <port> and <rootNode> may be absent. We determine that <port> is
present if it's a number and <rootNode> if it begins with a '/'.
One other useful feature from this work, not related to connecting to
a secure cluster, you may specify only the <principal> which would
cause a different HConnection to be used (per unique principal per
cluster). In this way, you can pass through different HBase properties
that apply to the HConnection (such as timeout parameters).
For example:
DriverManager.getConnection("jdbc:phoenix:h1:longRunning", props);
where props would contain the HBase config parameters and values for
timeouts in a "longRunning" connection which could be completely
different than connection gotten through this URL:
DriverManager.getConnection("jdbc:phoenix:h1:shortRunning", props);
Thanks,
James
On Mon, Sep 1, 2014 at 2:13 PM, Alex Kamil <alex.ka...@gmail.com> wrote:
> see
> http://bigdatanoob.blogspot.com/2013/09/connect-phoenix-to-secure-hbase-cluster.html
>
> and
> http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/latest/CDH5-Security-Guide/CDH5-Security-Guide.html
>
>
> On Mon, Sep 1, 2014 at 5:02 PM, <deepak_gatt...@dell.com> wrote:
>>
>> Hi all,
>>
>>
>>
>> Any one has success doing a Phoenix connection to a secure Hbase Hadoop
>> cluster, if yes can you please kindly let me know the steps taken, I am on
>> the recent version of phoenix and using Cloudera CDH 5.1 with hbase 0.98.
>>
>>
>>
>> Appreciate your help.
>>
>>
>>
>> Thanks
>>
>> Deepak Gattala
>
>
