[
https://issues.apache.org/jira/browse/PHOENIX-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17794075#comment-17794075
]
ASF GitHub Bot commented on PHOENIX-6053:
-----------------------------------------
stoty commented on PR #1690:
URL: https://github.com/apache/phoenix/pull/1690#issuecomment-1844885690
So I have confirmed that the hang is caused by this patch. The test ran fine
more than five times in a row without the patch, but failed every time I tried
with the patch.
It doesn't seem to be a problem with the test code itself, so the patch must
have introduced some other error, which causes the hang.
Now we just need to figure out which one of the 1300 changed files went
wrong.
> 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)
