[
https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158117#comment-15158117
]
Sergey Soldatov commented on PHOENIX-2535:
------------------------------------------
Do we need to shade all clients? At the moment we have regular, minimal, spark,
without-hbase.
Should they all be shaded?
Another question whether we want to shade most of the dependencies like it was
done in hbase or we want to shade just some of them (guava/jackson/something
else)?
[~enis] I'm not 100% sure, but it seems that in this case we need to build
phoenix-core against shaded artifacts, so both server and client will depends
on them.
> 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
>
>
> 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)
