[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232913#comment-15232913 ]
ASF GitHub Bot commented on PHOENIX-2535: ----------------------------------------- GitHub user ss77892 opened a pull request: https://github.com/apache/phoenix/pull/159 PHOENIX-2535 Create shaded clients (thin + thick) Shaded client + PHOENIX-2267 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ss77892/phoenix PHOENIX-2535 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/phoenix/pull/159.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #159 ---- commit a2d87d81a6bcf966f09c578e20569fbb0625d313 Author: Sergey Soldatov <sergey.solda...@gmail.com> Date: 2016-04-08T20:54:45Z PHOENIX-2535 Create shaded clients (thin + thick) ---- > 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)