You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/05/20 15:34:12 UTC

[jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick)

    [ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293554#comment-15293554 ] 

James Taylor commented on PHOENIX-2535:
---------------------------------------

Where we at with this one, [~sergey.soldatov]? Would be great if we could get this into 4.8.0.  FYI, I just ran into an issue with the transaction manager needing guava 13 while when used in local mode, it has guava 12 since that's what is in the hbase/lib dir (PHOENIX-2921). Would this help with that?

> 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)