[
https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253006#comment-15253006
]
Enis Soztutar commented on PHOENIX-2535:
----------------------------------------
It seems that we are ending with two jars now, one is coming from the main
phoenix-client pom, and the other from the phoenix-assembly.
under {{phoenix-client/target/}}
{code}
89M -rw-r--r-- 1 enis staff 89M Apr 21 16:30
phoenix-4.8.0-HBase-1.1-SNAPSHOT-client.jar
87M -rw-r--r-- 1 enis staff 87M Apr 21 16:28
phoenix-client-4.8.0-HBase-1.1-SNAPSHOT.jar
{code}
I am not sure whether we actually still need the assembly to contain
{{phoenix-assembly/src/build/components/all-common-jars.xml}} etc. It seems
that if we are building the jars from the modules, the assembly's job can be
just simply to gather these into the tarball.
> 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)
