[
https://issues.apache.org/jira/browse/PHOENIX-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014933#comment-14014933
]
James Taylor commented on PHOENIX-19:
-------------------------------------
Yes, you need to apply your changes to 3.0, 4.0, and master branches to produce
a separate patch for each. It's likely that the 4.0 and master patch will be
identical. Our source repo is at
https://git-wip-us.apache.org/repos/asf/incubator-phoenix.git and mirrored on
github at https://github.com/apache/incubator-phoenix.
Go through the methods on KeyValueBuilder instead of using methods on KeyValue
directly, that's prevent those kind of errors. The reason is that the APIs
changed in HBase between 0.94 and 0.98 and this class abstracts that away.
> 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: 3.0.0
>
> Attachments: SecureClusterConnectTest.java,
> phoenix-19-master-apache.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)
