[
https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232287#comment-15232287
]
Josh Elser commented on PHOENIX-2535:
-------------------------------------
bq. I have a suggestion. At the moment there is an ambiguous naming for query
server and the hbase side jar. They both are phoenix-server and it doesn't look
good. There is a couple options:
Yeah, this was something that [~apurtell] had pointed out a while back. Let me
see if I can find it.
It's definitely misleading. Making the PQS jar be "phoenix-queryserver" would
help. Including "hbase" somewhere in the HBase server-side jar would be
logical. Both would cause some breakages though. I'm not sure which would be
better (probably renaming the PQS jar since it's "newer").
> 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)
