[
https://issues.apache.org/jira/browse/PHOENIX-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated PHOENIX-2032:
----------------------------------
Attachment: PHOENIX-2032.00.patch
Why this change breaks things is completely beyond me; I've had no success
debugging into static initializers today. It appears that _either_
{{PhoenixDriver}} is no longer available on the classpath of the classloader
selected by {{DriverManager}}'s invocation of {{ServiceLoader}} _or_
{{PhoenixRuntime}}'s static initializer is prevented from being run.
Either way, this change fixes it.
> psql.py is broken after PHOENIX-2013
> ------------------------------------
>
> Key: PHOENIX-2032
> URL: https://issues.apache.org/jira/browse/PHOENIX-2032
> Project: Phoenix
> Issue Type: Bug
> Reporter: Nick Dimiduk
> 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)
