[ 
https://issues.apache.org/jira/browse/PHOENIX-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075814#comment-14075814
 ] 

James Taylor commented on PHOENIX-19:
-------------------------------------

[~anilgupta84] - I found a few issues with this change. See PHOENIX-1125. To 
prevent a backwards compatibility issue, I had to switch the order of the 
keytab and principal information in the URL. Otherwise, we wouldn't know if the 
third argument was a rootNode or a keytabFile. I fixed some other miscellaneous 
issues too (i.e. the hash code calculation was wrong and the general parsing of 
the url was too restrictive).

Net/net, the URL is now of the form 
jdbc:phoenix:<quorom>:<port>:<rootNode>:<principal>:<keytab>

where <port> and <rootNode> may be absent. We determine that <port> is present 
if it's a number and <rootNode> is it begins with a '/'. These changes will 
appear in our 3.1/4/1 release.

> Enhance JDBC connection of Phoenix to support connecting to a Secure HBase 
> cluster.
> -----------------------------------------------------------------------------------
>
>                 Key: PHOENIX-19
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-19
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Anil Gupta
>              Labels: hbase, jdbc, secure
>             Fix For: 5.0.0, 3.1, 4.1
>
>         Attachments: SecureClusterConnectTest.java, phoenix-19-four.patch, 
> phoenix-19-master-apache.patch, phoenix-19-master.patch, 
> phoenix-19-three.patch, phoenix-19.patch
>
>
> This is being moved from github 
> https://github.com/forcedotcom/phoenix/issues/550 to JIRA.
> As per my discussion with James Taylor over here 
> https://groups.google.com/forum/#!searchin/phoenix-hbase-user/secure$20cluster/phoenix-hbase-user/XHg2wXK4Hqo/qVTm92WLxUkJ
> and some other email exchanges. This ticket is to enhance the JDBC driver of 
> phoenix so that user can pass keytab and principal to connect to a secure 
> cluster.
> As per our discussion over email, could you please outline the changes 
> required to make this enhancement?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to