You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/11/03 15:31:00 UTC

[jira] [Commented] (AMBARI-22362) Specify the Correct HIVE_BIN In Hive Scripts

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

Hadoop QA commented on AMBARI-22362:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12895681/AMBARI-22362.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12611//console

This message is automatically generated.

> Specify the Correct HIVE_BIN In Hive Scripts
> --------------------------------------------
>
>                 Key: AMBARI-22362
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22362
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.6.1
>
>         Attachments: AMBARI-22362.patch
>
>
> The Hive scripts pass in a parameter called {{HIVE_BIN}}. Hive uses this to determine where {{hdp.version}} and {{HADOOP_HOME}} should be sourced from. In many cases, the binary chosen is:
> {{/usr/bin/hive -> /usr/hdp/current/hive-client}}
> This can lead to problems during an upgrade scenario where {{hive-client}} has not yet moved forward. It should be chosen based on the component being restarted...



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