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

Hadoop QA commented on AMBARI-7229:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12674028/AMBARI-7229_1.7.0.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 1 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:green}+1 core tests{color}.  The patch passed unit tests in .

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

This message is automatically generated.

> Stack version must start with 2. to be considered Hadoop-2.x compatible
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-7229
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7229
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.6.1
>            Reporter: Alexander Denissov
>            Assignee: Jaimin D Jetly
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7229.patch, AMBARI-7229_1.7.0.patch, 
> screenshot-1.png
>
>
> We have defined BIGTOP 0.8 stack based on upcoming BigTop 0.8 release. Stack 
> definition is similar to HDP-2.1 merged with HDP-2.0.6. When this stack is 
> configured for deployment a few of HDFS property defaults are missing as 
> indicated by red boxes.
> Looking at JavaScript logic is seems these properties are processed only for 
> Hadoop 2.x compatible stacks and App.js checks if the stack version starts 
> with 2 to consider it Hadoop 2.x compatible, which is not the case with 0.8 
> version of BIGTOP stack.
> PROPOSAL: the fact that a given stack is Hadoop 2.x compatible should not be 
> tied to the vendor stack version number, but rather explicitly defined as a 
> property either in the stack definition or the service definition. 
> Alternatively,  looking at the actual version of the HDFS service included in 
> the stack will be able to reveal if the stack is Hadoop 2.x compliant.



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

Reply via email to