[
https://issues.apache.org/jira/browse/PHOENIX-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297239#comment-14297239
]
Hudson commented on PHOENIX-1612:
---------------------------------
FAILURE: Integrated in Phoenix-master #573 (See
[https://builds.apache.org/job/Phoenix-master/573/])
PHOENIX-1612 Avoid context classloader issue (gabrielr: rev
d058a41c52c6a68c1581eff520c1f9e12486b89c)
*
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
> Phoenix can't be used from an external jar in SQL tools
> -------------------------------------------------------
>
> Key: PHOENIX-1612
> URL: https://issues.apache.org/jira/browse/PHOENIX-1612
> Project: Phoenix
> Issue Type: Bug
> Reporter: Gabriel Reid
> Assignee: Gabriel Reid
> Fix For: 5.0.0, 4.3
>
> Attachments: PHOENIX-1612.patch
>
>
> This is a regression to some of the behavior that was resolved in PHOENIX-966
> and a few others. If the phoenix-client jar is not in the lib directory of
> tools like SquirrelSQL and DBVisualizer, then it's not possible to connect to
> Phoenix with those tools.
> This current regression is due to a static HColumnDescriptor in
> ConnectionQueryServicesImpl. Initializing an HColumnDescriptor executes
> HBaseConfiguration.create, which then fails due to the hbase-defaults check
> (because the Phoenix-bundled hbase-default.xml isn't found via the context
> classloader).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
