[
https://issues.apache.org/jira/browse/PHOENIX-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Soldatov updated PHOENIX-2535:
-------------------------------------
Attachment: PHOENIX-2535-5.patch
Changes:
* added module phoenix-client
* due the bug in shading plugin (all resource transformers ignore
include/exclude for transorms. So even if we have exclude
{{org.apache.hadoop.**}} for {{org}} relocations, service file will have shaded
names) all relocations are done separately.
* {{org.eclipse}} is not shaded anymore since it's required for query server.
* tephra is not shaded
* phoenix-server.jar is located in the {{phoenix-server/target}} now. I'm not
sure whether we need to create a separate module for that. If so, need a name
for that .
* phoenix-assemble now has only tarball
Tested: sqlline, squirrel, tephra server, query server
> 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)
