[
https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235955#comment-15235955
]
Josh Elser commented on PHOENIX-2535:
-------------------------------------
bq. Josh Elser We used tephra as is (so we run
co.cask.tephra.TransactionServiceMain without any wrapper) and it uses
com.google.common
So the solution for that is to address at the Tephra level then?
bq. what is the reason to shade hadoop and hbase if we build phoenix against
the specific versions?
Just a question, i'm not sure tbqh. I see that HBase doesn't shade Hadoop. I
wasn't sure what a reasonable expectation on Hadoop/HBase would be for Phoenix.
If it's been thought about already, good enough for me -- just curious :)
> 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)
