[
https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083444#comment-15083444
]
Josh Mahonin commented on PHOENIX-2535:
---------------------------------------
This is definitely a continuing problem with getting Phoenix and Spark playing
nice, which they're equally guilty of on their side.
I think this is the right solution, and I might be able to spend some time on
it this week, but Maven's definitely not my strong suit. I'm still trying to
figure out how and why the existing artifacts get built the way they do!
> 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
> Fix For: 4.7.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)
