[ https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232444#comment-15232444 ]
Nick Dimiduk commented on PHOENIX-2535: --------------------------------------- bq. +1 to rename query server jar yeah, this should have been fixed before the first release. Whatever you call the PQS server jar, be sure the client jar matches so it's super-duper clear what's what. And thanks for cleaning up all these thick client jars too, it's confusing to see. Once the dust settles here, it would be great to re-evaluate publishing client jars to maven central. It's a real PITA to tell folks doing maven dev to drop a jar into their resources manually. > 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)