[
https://issues.apache.org/jira/browse/PHOENIX-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519820#comment-14519820
]
Geoffrey Jacoby commented on PHOENIX-1880:
------------------------------------------
Testing's still in progress I'm afraid. I tried to build a small app that just
exercised this one use case on a secure cluster, but since I'd never built a
kerberos-aware Phoenix/HBase app from scratch before, underestimated how long
it would take. Once I got it working, it turned out that I couldn't reproduce
the original problem with it. Today I'm going to do a deploy of the real
application where we detected the issue in the first place with a custom
Phoenix build with the patch, and verify that way.
> Connections from QueryUtil.getConnection don't work on secure clusters
> ----------------------------------------------------------------------
>
> Key: PHOENIX-1880
> URL: https://issues.apache.org/jira/browse/PHOENIX-1880
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.3.0, 4.4.0
> Reporter: Geoffrey Jacoby
> Labels: patch
> Fix For: 4.4.0
>
> Attachments: PHOENIX-1880.patch
>
>
> QueryUtil.getConnection(Configuration) and
> QueryUtil.getConnection(Properties, Configuration) both only take the
> zookeeper quorum from the Configuration, and drop any other properties on the
> config object. In order to connect to secure HBase clusters, more properties
> are needed. This is a similar problem to PHOENIX-1078, and the likely fix is
> similar: copy the configuration parameters into the Properties object before
> using it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
