[
https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168271#comment-15168271
]
Enis Soztutar commented on PHOENIX-2535:
----------------------------------------
bq. My vote is, at the very least, the regular and Spark client should be
shaded. I'm not sure the use case for minimal and without-hbase.
Agreed.
bq. Enis Soztutar 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.
Good question. If Phoenix also uses shaded jars on the server side, it might be
good since then Phoenix can use its own version of guava, etc without depending
on Hadoop's or HBase's versions.
> 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)
