[
https://issues.apache.org/jira/browse/PHOENIX-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582392#comment-14582392
]
Gabriel Reid commented on PHOENIX-2032:
---------------------------------------
Aha, I just read all the stuff you put in MASSEMBLY-773, I missed the before. I
see that ticket is resolved now, so I guess there's an option to use the fixed
version of the plugin (although I'm assuming it'll be a while before it's
released).
Of the three options you outlined before, I don't think that option #1 (ship
the broken jar, but add a {{Class.forName}} call in main methods) is viable --
the current jar won't work via SPI in a client that relies on SPI working
without first calling {{Class.forName}} (and I assume that there are clients
that do that).
Option #2 (include the queryserver, or at least queryserver-client) in the fat
phoenix client actually doesn't sound too bad. The fact that the thin client is
included in the fat client uberjar doesn't sound all that crazy. Any idea how
much extra bloat that would add to the fat client jar? Other than that, any
major reason not to do this?
> 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
> Fix For: 5.0.0, 4.5.0, 4.4.1
>
> Attachments: 2032.patch, 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 [~chrajeshbab...@gmail.com] for tracking down the breaking change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
