phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Soldatov (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2535) Create shaded clients (thin + thick)
Date Fri, 08 Apr 2016 06:52:25 GMT


Sergey Soldatov commented on PHOENIX-2535:

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:
1. rename {{phoenix-server}} module to {{phoenix-query-server}} and keep hbase server side
jar in {{phoenix-server}}
2. rename {{phoenix-server.jar}} to {{phoenix-hbase-something}} 
It would be nice to do that, so hbase side jar can be located in its own module and can be
published to the artifactory.  

[~jamestaylor], [~elserj] what do you think?

> Create shaded clients (thin + thick) 
> -------------------------------------
>                 Key: PHOENIX-2535
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message