[
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-6.patch
rebased on the master
[~elserj] Had to move all transfers, etc out of the parent pom. I have no idea
why, but once we use pluginManagement in parent, shading plugin brings all
dependencies from parent pom to childs. Regardless whether I override artifacts
set using combine.self/combine.children it includes in shaded jar everything.
Moreover it looks even strange than it sounds. Using mvn -X tried to check what
is included for the module that according to shading configuration was supposed
to include only phoenix-core. In log there is only one line "Including
phoenix-core.jar", but the artifact was 95Mb. So, I moved all this stuff to
childs.
> 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,
> PHOENIX-2535-6.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)
