[
https://issues.apache.org/jira/browse/PHOENIX-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid updated PHOENIX-966:
---------------------------------
Attachment: PHOENIX-966a.patch
Initial patch for 3.0 that temporarily sets the current thread's context
classloader on calls that require calling HBaseConfiguration.create or
accessing coprocessor endpoint classes.
Assuming there are no objections to going in this direction, the work to still
be done is:
* add testing
* make a 4.0 patch (which would probably be a subset of this patch)
This change is also dependent on PHOENIX-962 being in place.
> 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
> Attachments: PHOENIX-966a.patch
>
>
> 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)
