tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aihua Xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEZ-3853) Binary incompatibility caused by DEFAULT_LOG_LEVEL
Date Thu, 19 Oct 2017 19:55:00 GMT

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

Aihua Xu commented on TEZ-3853:
-------------------------------

[~aplusplus] I have a question on the change. I  only see that we removed toString() call
but should we update the pom.xml to point to hadoop3? I guess tez binary may still try to
find {{Level DEFAULT_LOG_LEVEL;}} rather than {{String DEFAULT_LOG_LEVEL;}}? Will you be able
to verify tez jar against hadoop3 jar? Thanks.

> Binary incompatibility caused by DEFAULT_LOG_LEVEL
> --------------------------------------------------
>
>                 Key: TEZ-3853
>                 URL: https://issues.apache.org/jira/browse/TEZ-3853
>             Project: Apache Tez
>          Issue Type: Sub-task
>    Affects Versions: 0.9.0
>            Reporter: Aihua Xu
>            Assignee: Zhiyuan Yang
>             Fix For: 0.9.1
>
>         Attachments: TEZ-3853.1.patch
>
>
> Hive is moving to support hadoop 3.0 in HIVE-15016. As we find out that hadoop introduced
some incompatible changes in 3.0 which requires Tez to support hadoop 3.0 as well in order
for hive to integrate with Tez. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message