[jira] [Commented] (AMBARI-18897) HBase conf directory should not have a copy of core-site.xml and hdfs-site.xml

2016-11-16 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-18897:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6031 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6031/])
AMBARI-18897. HBase conf directory should not have a copy of (vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b5779fe6dca4db7df15abd905ef4b3dfae9d2c03])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json
* (edit) 
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py
* (edit) 
ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_regionserver.py
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/constants.py
* (edit) 
ambari-server/src/test/python/stacks/2.0.6/HBASE/test_phoenix_queryserver.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_client.py


> HBase conf directory should not have a copy of core-site.xml and hdfs-site.xml
> --
>
> Key: AMBARI-18897
> URL: https://issues.apache.org/jira/browse/AMBARI-18897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18897.patch
>
>
> /etc/hbase/conf/ contains core-site.xml and hdfs-site.xml which should not be 
> needed at all. But more importantly, when we change a setting in Ambari, they 
> do not get reflected in the hdfs-site.xml that is under the hbase conf 
> directory. Since there are more than 1 core-site.xml in the classpath, this 
> obviously causes issues since the changed configs are not picked up.



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


[jira] [Commented] (AMBARI-18897) HBase conf directory should not have a copy of core-site.xml and hdfs-site.xml

2016-11-16 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-18897:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #348 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/348/])
AMBARI-18897. HBase conf directory should not have a copy of (vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3c3d3d23d4713954e0ac487c87c3f1283a34b284])
* (edit) 
ambari-common/src/main/python/resource_management/libraries/functions/constants.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_client.py
* (edit) 
ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_regionserver.py
* (edit) 
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/hbase.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json
* (edit) ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py
* (edit) 
ambari-server/src/test/python/stacks/2.0.6/HBASE/test_phoenix_queryserver.py


> HBase conf directory should not have a copy of core-site.xml and hdfs-site.xml
> --
>
> Key: AMBARI-18897
> URL: https://issues.apache.org/jira/browse/AMBARI-18897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18897.patch
>
>
> /etc/hbase/conf/ contains core-site.xml and hdfs-site.xml which should not be 
> needed at all. But more importantly, when we change a setting in Ambari, they 
> do not get reflected in the hdfs-site.xml that is under the hbase conf 
> directory. Since there are more than 1 core-site.xml in the classpath, this 
> obviously causes issues since the changed configs are not picked up.



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


[jira] [Commented] (AMBARI-18897) HBase conf directory should not have a copy of core-site.xml and hdfs-site.xml

2016-11-15 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-18897:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12838998/AMBARI-18897.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 4 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 
ambari-server.

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

This message is automatically generated.

> HBase conf directory should not have a copy of core-site.xml and hdfs-site.xml
> --
>
> Key: AMBARI-18897
> URL: https://issues.apache.org/jira/browse/AMBARI-18897
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18897.patch
>
>
> /etc/hbase/conf/ contains core-site.xml and hdfs-site.xml which should not be 
> needed at all. But more importantly, when we change a setting in Ambari, they 
> do not get reflected in the hdfs-site.xml that is under the hbase conf 
> directory. Since there are more than 1 core-site.xml in the classpath, this 
> obviously causes issues since the changed configs are not picked up.



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