[ https://issues.apache.org/jira/browse/PHOENIX-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769082#comment-17769082 ]
Istvan Toth commented on PHOENIX-6053: -------------------------------------- I have checked my old POC. The problem with the mapreduce code is that the snapshot support depends on hbase-server, and I do not see a way to work around that, apart from factoring out the snapshot support from phoenix-mapreduce. For this reason, I suggest that we leave the mapreduce code in phoenix-coprocessors (or whatever we end up calling it) for now, and not make a separate module for it. We can revisit this later if needed. > Use shaded hadoop-client and hbase-shaded-client in phoenix-client > ------------------------------------------------------------------ > > Key: PHOENIX-6053 > URL: https://issues.apache.org/jira/browse/PHOENIX-6053 > Project: Phoenix > Issue Type: Improvement > Components: core > Affects Versions: 5.1.0 > Reporter: Istvan Toth > Assignee: Istvan Toth > Priority: Major > Attachments: Phoenix_separation.pdf > > > The phoenix client is built with the unshaded Hadoop and HBase dependencies, > and then relocates some (a lot) of those to declutter the client classpath. > Try to use hadoop-client and hbase-shaded-client-byo-hadoop instead. (And > keep relocating our direct dependecies) > While this will likely further bloat the thick client JAR, it should > * clean up the classpath further > * Would decouple most of the dependencies that Phoenix shares with > Hbase/Hadoop from them. -- This message was sent by Atlassian Jira (v8.20.10#820010)