phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriel Reid (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-966) Phoenix needs to be on the main classpath of SQL tools
Date Sat, 03 May 2014 20:40:14 GMT


Gabriel Reid updated PHOENIX-966:

    Attachment: PHOENIX-966b-4.0.patch

Patch for 4.0 and master, with no prerequisites for other patches. Passes full test suite,
and has been tested for basic functionality with both SQuirreL and [DbVisualizer|]
for basic functionality (create table, add data, various queries) while not adding the Phoenix
jar to the installation lib directory (or equivalent) of the tool itself, and all seems fine
(apart from some issues in SQuirreL that are present regardless of this patch).

> Phoenix needs to be on the main classpath of SQL tools
> ------------------------------------------------------
>                 Key: PHOENIX-966
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Gabriel Reid
>            Assignee: Gabriel Reid
>         Attachments: PHOENIX-966a.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

View raw message