[
https://issues.apache.org/jira/browse/PHOENIX-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581163#comment-14581163
]
Nick Dimiduk commented on PHOENIX-2032:
---------------------------------------
Let's see if we get any attention from maven folks.
Mean time, I think we have a couple choices for working around this problem:
# ship a broken {{java.sql.Driver}} in {{client.jar}} but include the code
change I've attached here, manually registering the {{PhoenixDriver}} in any
path that involves a {{main()}} that uses {{jdbc:phoenix}}.
# add queryserver as a dependency in the phoenix-assembly module, thereby
including classes for all 3 drivers and allowing the {{loadInitialDrivers}}
loop to complete.
# hack up our build into pieces, with separate maven invocations (and thus
processes) for compilation of {{phoenix-client.jar}} and
{{phoenix-server-runnable.jar}}.
> psql.py is broken after PHOENIX-2013
> ------------------------------------
>
> Key: PHOENIX-2032
> URL: https://issues.apache.org/jira/browse/PHOENIX-2032
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.5.0, 4.4.1
> Reporter: Sergio Peleato
> Assignee: Nick Dimiduk
> Priority: Blocker
> Attachments: PHOENIX-2032.00.patch
>
>
> psql is no longer able to load the phoenix driver after PHOENIX-2013.
> {noformat}
> $ ./bin/psql.py localhost examples/WEB_STAT.sql
>
>
> java.sql.SQLException: No suitable driver found for jdbc:phoenix:localhost
> at java.sql.DriverManager.getConnection(DriverManager.java:596)
> at java.sql.DriverManager.getConnection(DriverManager.java:187)
> at
> org.apache.phoenix.util.PhoenixRuntime.main(PhoenixRuntime.java:183)
> {noformat}
> Hat-tip to [[email protected]] for tracking down the breaking change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
