phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4677) Commons-cli needs to be listed as dependency.
Date Wed, 28 Mar 2018 19:25:00 GMT

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

Josh Elser commented on PHOENIX-4677:
-------------------------------------

.001 is only for the 5.x branch at this point.

After commons-cli was moved into hbase-thirdparty, we need to update our use of AbstractHBaseTool
to account for this.

Additionally, we should have an explicit dependency on commons-cli as we use it for other
(Hadoop) Tool implementations in our codebase. The Phoenix-client jar shading prevents us
from hitting the same problem which HBase did with conflicting commons-cli jars on Hadoop
3 (see HBASE-20201 for more details on that "conflict").

> Commons-cli needs to be listed as dependency.
> ---------------------------------------------
>
>                 Key: PHOENIX-4677
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4677
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 4.14.0, 5.0.0
>
>         Attachments: PHOENIX-4677.001.patch
>
>
> After HBase upgraded to hbase-thirdparty 2.1.0 via HBASE-20223, it shaded its dependency
on commons-cli. Phoenix has apparently be transitively using this dependency without explicitly
declaring it.
> We need to own the dependencies that we require.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message