[jira] [Commented] (HIVE-16860) HostUtil.getTaskLogUrl change between hadoop 2.3 and 2.4 breaks at runtime.

["Sushanth Sowmyan (JIRA)" <ji...@apache.org>]

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

Sushanth Sowmyan commented on HIVE-16860:
-----------------------------------------

Actually, nvm - please ignore - that was based on looking at the code for .1.patch for HIVE-6900. The .2.patch with HIVE-6900 makes it so this should never happen. However, I saw that happening in a user's log and assumed that was still the problem. Clearly, though, that user has a weird hive version.

Closing this as invalid.


> HostUtil.getTaskLogUrl change between hadoop 2.3 and 2.4 breaks at runtime.
> ---------------------------------------------------------------------------
>
>                 Key: HIVE-16860
>                 URL: https://issues.apache.org/jira/browse/HIVE-16860
>             Project: Hive
>          Issue Type: Bug
>          Components: Shims
>    Affects Versions: 0.14.0
>            Reporter: Chris Drome
>            Assignee: Jason Dere
>
> Original issue in HIVE-6900 : 
> {noformat}
> The signature for HostUtil.getTaskLogUrl has changed between Hadoop-2.3 and Hadoop-2.4.
> Code in shims/0.23/src/main/java/org/apache/hadoop/hive/shims/Hadoop23Shims.java works with Hadoop-2.3 method and causes compilation failure with Hadoop-2.4.
> {noformat}
> The issue with HIVE-6900 is still not completely fixed, in that compilation succeeds, but this fails now at runtime because https://issues.apache.org/jira/secure/attachment/12651497/MAPREDUCE-5830.patch was committed in hadoop - The result is that our reflection check to see if the 23_METHOD exists succeeds, which means 23_METHOD will not be null, and 24_METHOD will be null, and thus, at runtime, we will wind up calling 23_METHOD. If hadoop had not "fixed" this bug, with this fix, our shim works, but with their fix, it looks like we still have a runtime problem. :)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)