You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2015/01/29 16:42:34 UTC

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

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

Gabriel Reid resolved PHOENIX-1612.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 4.3
                   5.0.0
         Assignee: Gabriel Reid

Pushed to 4.x and master branches

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