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 2016/04/26 23:34:12 UTC

[jira] [Commented] (AMBARI-16099) Modify WEBHCAT_SERVER START command to create hive-site.conf

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

Hadoop QA commented on AMBARI-16099:
------------------------------------

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

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 2 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6667//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6667//console

This message is automatically generated.

> Modify WEBHCAT_SERVER START command to create hive-site.conf
> ------------------------------------------------------------
>
>                 Key: AMBARI-16099
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16099
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: 2.2.1.1
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>             Fix For: 2.2-next
>
>         Attachments: AMBARI-16099.patch
>
>
> Make sure hive-site.xml is created before WEBHCAT_SERVER component is started. This is already done in case of an upgrade of a secure cluster, however this is not executed in case of a Blueprint deployment first start-up. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)