phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anil Gupta (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-19) Enhance JDBC connection of Phoenix to support connecting to a Secure HBase cluster.
Date Wed, 04 Jun 2014 07:27:01 GMT


Anil Gupta commented on PHOENIX-19:

[~jamestaylor]: Sorry for delay. As, I have a learning curve in Git. And, i had to setup 3
new workspace for 3 branches and do rework to apply patch on all 3 branches since Git was
not applying some of the changes from my old patch. I have applied patch on master, 3.0, 4.0.
I also successfully built and ran unit tests for master, 3.0 and 4.0 branch.

Please suggest me what to do when we are unable to login to cluster? Previously, i was doing
catch (IOException e) {
      "Exception while trying to login to secure cluster!!");
                throw new SQLExceptionInfo.Builder(SQLExceptionCode.CANNOT_ESTABLISH_CONNECTION)
But due to recent code changes i cannot throw an exception. Please have a look at the code
and share your opinions.

> Enhance JDBC connection of Phoenix to support connecting to a Secure HBase cluster.
> -----------------------------------------------------------------------------------
>                 Key: PHOENIX-19
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Anil Gupta
>              Labels: hbase, jdbc, secure
>             Fix For: 3.0.0
>         Attachments:, 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 to
> As per my discussion with James Taylor over here!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

View raw message