[
https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235727#comment-15235727
]
Josh Elser commented on PHOENIX-2535:
-------------------------------------
{noformat}
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
phoenix-queryserver-client ---
[INFO]
org.apache.phoenix:phoenix-queryserver-client:jar:4.8.0-HBase-1.1-SNAPSHOT
[INFO] +- org.apache.calcite.avatica:avatica:jar:1.7.1:compile
[INFO] | +- com.google.protobuf:protobuf-java:jar:2.5.0:compile (version
managed from 3.0.0-beta-1)
{noformat}
Ok, this is probably why. I think we'll automatically get in the right protobuf
from o.a.c.avatica:avatica anyways, so we can just exclude protobuf.
> Create shaded clients (thin + thick)
> -------------------------------------
>
> Key: PHOENIX-2535
> URL: https://issues.apache.org/jira/browse/PHOENIX-2535
> Project: Phoenix
> Issue Type: Bug
> Reporter: Enis Soztutar
> Assignee: Sergey Soldatov
> Fix For: 4.8.0
>
> Attachments: PHOENIX-2535-1.patch, PHOENIX-2535-2.patch,
> PHOENIX-2535-3.patch, PHOENIX-2535-4.patch, PHOENIX-2535-5.patch
>
>
> Having shaded client artifacts helps greatly in minimizing the dependency
> conflicts at the run time. We are seeing more of Phoenix JDBC client being
> used in Storm topologies and other settings where guava versions become a
> problem.
> I think we can do a parallel artifact for the thick client with shaded
> dependencies and also using shaded hbase. For thin client, maybe shading
> should be the default since it is new?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
