[
https://issues.apache.org/jira/browse/PHOENIX-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989057#comment-13989057
]
James Taylor commented on PHOENIX-966:
--------------------------------------
+1. Looks like you wrapped all the necessary code paths. Thanks [~gabriel.reid]
- this is a big improvement. Would you mind updating the documentation on our
website too sometime over the next couple of weeks?
> 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, PHOENIX-966b-3.0.patch,
> PHOENIX-966b-4.0.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)
