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 Wed, 06 Apr 2016 23:31:25 GMT


Sergey Soldatov commented on PHOENIX-2535:

I want just to confirm that the stuff I'm doing is correct:
* new {{phoenix-client}} module with the {{phoenix-client}} artifact (full shaded client)
and update for command line utils to use it
* no more {{client-spark}} jar since there is no problems with different versions of libraries
* {{phoenix-server}} jar file will be created in the existing {{phoenix-server}} module
* {{phoenix-assemble}} will contains only tarball 

Open questions:
Why we need {{client-without-hbase}} and {{client-minimal}} jars if we do not ship it in the
tarball  nor publish them in the artifactory?
If we want them published, whether it's ok to create a separate modules for them?

[~jamestaylor], [~enis], [~elserj], [~jmahonin] any comments/suggestions?


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