[
https://issues.apache.org/jira/browse/AMBARI-14752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118006#comment-15118006
]
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/12784445/AMBARI-14752.branch22.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/5067//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.branch22.patch, 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)
