phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Mahonin (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2032) is broken after PHOENIX-2013
Date Sat, 13 Jun 2015 14:52:00 GMT


Josh Mahonin commented on PHOENIX-2032:

It would be nice if Spark users could just use the regular client JAR with phoenix-spark included
in it, by simply adding it to the Spark classpath, although a spark-specific JAR wouldn't
be too terrible either if that's the only option.

However, JAR size issue I think is my fault. Looking at the phoenix-spark pom.xml,  scala-library,
spark-core or spark-sql should all be marked as scope 'provided', since Spark offers these
it in its own classpath.

The other dependencies not marked as test or provided, hadoop-client, hadoop-common, hbase-client,
I think are all included in the client JAR anyway, so I don't think those would matter, but
I may be wrong.

On Monday, I'll try adjust those provided settings and see if everything is working for me.
If that reduces the JAR size, would we be able to get phoenix-spark back in the client JAR?

> is broken after PHOENIX-2013
> ------------------------------------
>                 Key: PHOENIX-2032
>                 URL:
>             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/ localhost examples/WEB_STAT.sql                                     
> java.sql.SQLException: No suitable driver found for jdbc:phoenix:localhost
>         at java.sql.DriverManager.getConnection(
>         at java.sql.DriverManager.getConnection(
>         at org.apache.phoenix.util.PhoenixRuntime.main(
> {noformat}
> Hat-tip to [] for tracking down the breaking change.

This message was sent by Atlassian JIRA

View raw message