[
https://issues.apache.org/jira/browse/PHOENIX-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584376#comment-14584376
]
Hudson commented on PHOENIX-2032:
---------------------------------
SUCCESS: Integrated in Phoenix-master #784 (See
[https://builds.apache.org/job/Phoenix-master/784/])
PHOENIX-2032 psql.py is broken after PHOENIX-2013 (ndimiduk: rev
d1934afbe6230e823b9009950fe721165e98cc7c)
* phoenix-assembly/src/build/client.xml
* phoenix-assembly/pom.xml
> 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.opt2a.diff, 2032.opt2a.diff, 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 [[email protected]] for tracking down the breaking change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
