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

ASF subversion and git services commented on IMPALA-14504:
----------------------------------------------------------

Commit 7fb986e47aaabb781876575e5897f56c10769dc0 in impala's branch 
refs/heads/master from Michael Smith
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=7fb986e47 ]

IMPALA-14504: Use shaded hbase, protobuf from Hadoop

Switches to shaded Hbase so it can include its own versions of
dependencies. Note that hbase-client includes hbase-common,
hbase-protocol.

Excludes older protobuf-java from mysql-connector so we get it from
Hadoop.

Allows orc-format 1.0, which is a dependency in future ORC releases.

Change-Id: I386d03c3123ce1159abc54c505f60e0ae619f5fe
Reviewed-on: http://gerrit.cloudera.org:8080/23553
Reviewed-by: Joe McDonnell <[email protected]>
Reviewed-by: Riza Suminto <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Use hbase shaded jars to avoid dependency conflicts
> ---------------------------------------------------
>
>                 Key: IMPALA-14504
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14504
>             Project: IMPALA
>          Issue Type: Task
>          Components: Frontend
>    Affects Versions: Impala 5.0.0
>            Reporter: Michael Smith
>            Assignee: Michael Smith
>            Priority: Major
>
> hbase-protocol has a direct dependency on protobuf-java and other 
> dependencies. Other projects are starting to update to protobuf-java 3.x, but 
> hbase still depends on 2.5.0.
> HBase provides shaded jars we can use to isolate their dependencies. We 
> should also be more deliberate about how we import protobuf-java so we get it 
> from Hadoop.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to