[jira] [Updated] (PHOENIX-1612) Phoenix can't be used from an external jar in SQL tools

["Gabriel Reid (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PHOENIX-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabriel Reid updated PHOENIX-1612:
----------------------------------
    Attachment: PHOENIX-1612.patch

Patch which removes static construction of an HColumnDescriptor. This fix has been verified with [DBVisualizer|http://www.dbvis.com].

This also fixes the same issue when working with SquirrelSQL, although the next issue that comes up is an incompatibility with commons-collections versions (as outlined here: http://sourceforge.net/p/squirrel-sql/mailman/message/33039278/)

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