[
https://issues.apache.org/jira/browse/AMBARI-14752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112351#comment-15112351
]
Hadoop QA commented on AMBARI-14752:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12783497/AMBARI-14752.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5027//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5027//console
This message is automatically generated.
> hawq_profile script conflicts with HAWQ segment init
> ----------------------------------------------------
>
> Key: AMBARI-14752
> URL: https://issues.apache.org/jira/browse/AMBARI-14752
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk, 2.2.0
> Reporter: Lav Jain
> Assignee: Lav Jain
> Priority: Minor
> Attachments: AMBARI-14752.patch
>
>
> The problem seems to manifest when hawq_master and hawq_segment are deployed
> on the same host machine. Because of the PGPORT and PGHOST entries in
> .hawk-profile.sh, there seems to be some conflict during HAWQSEGMENT init
> phase.
> Similarily, bashrc script is unnecessary for HAWQ as it explicits sources
> greenplum.sh for all hawq commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
