You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Anil Gupta (JIRA)" <ji...@apache.org> on 2014/07/28 06:49:39 UTC

[jira] [Comment Edited] (PHOENIX-19) Enhance JDBC connection of Phoenix to support connecting to a Secure HBase cluster.

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

Anil Gupta edited comment on PHOENIX-19 at 7/28/14 4:48 AM:
------------------------------------------------------------

[~jamestaylor]: As per my implementation, following connection string "jdbc:phoenix:vampire7:shorttest" is invalid. Hence, the exception. I check that the keytab argument should end with a ".keytab". So, that should take care of differentiating whether it is RootNode or keytab filename. 
However, the order doesnt really matter. If you want to keep the order "jdbc:phoenix:<quorom>:<port>:<rootNode>:<principal>:<keytab>" then also it is fine. 
I am wondering why would this string is a valid connection string "jdbc:phoenix:vampire7:shorttest"?


was (Author: anilgupta84):
[~jamestaylor]: As per my implementation, following connection string "jdbc:phoenix:vampire7:shorttest" is invalid. Hence, the exception. I check that the keytab argument should end with a ".keytab". So, that should take care of differentiating whether it is hbase_root_dir or keytab filename. 
However, the order doesnt really matter. If you want to keep the order "jdbc:phoenix:<quorom>:<port>:<rootNode>:<principal>:<keytab>" then also it is fine. 
I am wondering why would this string is a valid connection string "jdbc:phoenix:vampire7:shorttest"?

> 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)