[
https://issues.apache.org/jira/browse/PHOENIX-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940291#comment-13940291
]
Gabriel Reid commented on PHOENIX-876:
--------------------------------------
It looks like there are indeed a lot of dependencies pull into the mapreduce
jar that aren't necessary (it currently just pulls in all the transitive
dependencies of Phoenix). I think that there are two main options we can either
try to use the client jar, or keep the mapreduce jar while blacklisting the
transitive dependencies that aren't needed (which will make it a lot smaller).
I'm 100% sure that shrinking the mapreduce jar will work, and only partially
sure about the client jar approach working. I'll take a look and see if I can
get it to work.
> Remove phoenix-*-mapreduce.jar if not necessary
> -----------------------------------------------
>
> Key: PHOENIX-876
> URL: https://issues.apache.org/jira/browse/PHOENIX-876
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0, 4.0.0
> Reporter: James Taylor
> Assignee: Gabriel Reid
>
> Do we need the
> phoenix-assembly/target/phoenix-3.0.0-incubating-SNAPSHOT-mapreduce.jar to be
> produced, as it pulls in a ton of stuff? Can our standard client jar be used
> plus the hadoop.jar instead? If we don't need it, we should update the
> pom/build stuff to not produce it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
