[ 
https://issues.apache.org/jira/browse/PHOENIX-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793367#comment-17793367
 ] 

ASF GitHub Bot commented on PHOENIX-6053:
-----------------------------------------

stoty commented on PR #1690:
URL: https://github.com/apache/phoenix/pull/1690#issuecomment-1841277632

   As discussed ofline, we have found a more compatible module naming scheme:
   phoenix-core -> phoenix-core-client
   phoenix-coprocessors -> phoenix-core-server
   phoenix-test > phoenix-core (the original module)
   
   phoenix-core depends on phoenix-core-server and phoenix-server-client, and 
all the tests.
   
   This maximizes compatbility with existing maven consumers and downstream 
projects.




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

Reply via email to