phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriel Reid (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-966) Phoenix needs to be on the main classpath of SQL tools
Date Fri, 02 May 2014 20:26:14 GMT
Gabriel Reid created PHOENIX-966:
------------------------------------

             Summary: Phoenix needs to be on the main classpath of SQL tools
                 Key: PHOENIX-966
                 URL: https://issues.apache.org/jira/browse/PHOENIX-966
             Project: Phoenix
          Issue Type: Bug
            Reporter: Gabriel Reid
            Assignee: Gabriel Reid


The Phoenix client jar currently needs to be put on the boot classpath of external SQL tools
in order to function correctly, while most JDBC drivers do not have this requirement.

For example, in SQuirreL there is an option to provide the path to the JDBC driver jar file
when defining a JDBC driver. This approach doesn't work with Phoenix due to it dependence
on loading classes and the hbase-default.xml file via the context classloader.

For installations of external tools where users don't have the rights/abilities/knowledge
necessary to add an external jar file to the boot classpath, this causes a genuine issue for
using Phoenix.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message