[
https://issues.apache.org/jira/browse/PHOENIX-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-6053.
----------------------------------
Fix Version/s: 5.2.0
Release Note:
The previous phoenix-core maven module (and artifacts) have been split into
phoenix-core-client for the client (JDBC driver) side code, and into the server
(Hbase server classpath and mapreduce) modules.
The old phoenix-core module and aritfact now only includes tests.
As phoenix-core depends on both now artifacts, and acts as a backwards
compatibility feature, it is expected that consumers of those maven artifacts
will not be affected by this change. (But other changes in 5.2 are likely to to
require changes)
Resolution: Fixed
Committed to master.
Thanks a lot for seeing this through [~ameszaros].
> Split Server Side Code into a Separate Module
> ---------------------------------------------
>
> Key: PHOENIX-6053
> URL: https://issues.apache.org/jira/browse/PHOENIX-6053
> Project: Phoenix
> Issue Type: Improvement
> Components: core
> Affects Versions: 5.1.0
> Reporter: Istvan Toth
> Assignee: Aron Attila Meszaros
> Priority: Major
> Fix For: 5.2.0
>
> Attachments: Phoenix_separation.pdf
>
>
> The phoenix client is built with the unshaded Hadoop and HBase dependencies,
> and then relocates some (a lot) of those to declutter the client classpath.
> Try to use hadoop-client and hbase-shaded-client-byo-hadoop instead. (And
> keep relocating our direct dependecies)
> While this will likely further bloat the thick client JAR, it shouldÂ
> * clean up the classpath further
> * Would decouple most of the dependencies that Phoenix shares with
> Hbase/Hadoop from them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
