[
https://issues.apache.org/jira/browse/AMBARI-14620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093311#comment-15093311
]
Hadoop QA commented on AMBARI-14620:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12781701/AMBARI-14620-trunk.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:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4865//console
This message is automatically generated.
> HAWQ master components start should show ERROR or WARNING if
> dfs.allow.truncate is set to false
> -----------------------------------------------------------------------------------------------
>
> Key: AMBARI-14620
> URL: https://issues.apache.org/jira/browse/AMBARI-14620
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Reporter: Matt
> Assignee: Matt
> Priority: Minor
> Fix For: trunk, 2.2.1
>
> Attachments: AMBARI-14620-trunk.patch
>
>
> dfs.allow.truncate should be set to true for optimal conditions for HAWQ.
> If dfs.allow.truncate is not set to true or does not exist as a
> configuration, HAWQMASTER and HAWQSTANDBY start should throw a warning or
> error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
