[jira] [Commented] (AMBARI-8680) Incorrect hive.metastore.uris value after adding Hive Metastore via Service Actions

2014-12-12 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-8680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14243928#comment-14243928
 ] 

Hadoop QA commented on AMBARI-8680:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12686815/AMBARI-8680.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 .

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

This message is automatically generated.

 Incorrect hive.metastore.uris value after adding Hive Metastore via Service 
 Actions
 ---

 Key: AMBARI-8680
 URL: https://issues.apache.org/jira/browse/AMBARI-8680
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.0.0

 Attachments: AMBARI-8680.patch


 After cluster deploy, one more Hive Metastore component was added via Service 
 Actions menu. hive.metastore.uris was updated incorrectly (containing null 
 instead of second Metastore host name): 
 {noformat}host.name1:9083,null:9083{noformat}
 Cannot be reproduced after visiting Host Details Page.



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


[jira] [Commented] (AMBARI-8680) Incorrect hive.metastore.uris value after adding Hive Metastore via Service Actions

2014-12-12 Thread Oleg Nechiporenko (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-8680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14243962#comment-14243962
 ] 

Oleg Nechiporenko commented on AMBARI-8680:
---

+1 for patch

 Incorrect hive.metastore.uris value after adding Hive Metastore via Service 
 Actions
 ---

 Key: AMBARI-8680
 URL: https://issues.apache.org/jira/browse/AMBARI-8680
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.0.0

 Attachments: AMBARI-8680.patch


 After cluster deploy, one more Hive Metastore component was added via Service 
 Actions menu. hive.metastore.uris was updated incorrectly (containing null 
 instead of second Metastore host name): 
 {noformat}host.name1:9083,null:9083{noformat}
 Cannot be reproduced after visiting Host Details Page.



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


[jira] [Commented] (AMBARI-8680) Incorrect hive.metastore.uris value after adding Hive Metastore via Service Actions

2014-12-12 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-8680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14244010#comment-14244010
 ] 

Hudson commented on AMBARI-8680:


SUCCESS: Integrated in Ambari-trunk-Commit #1187 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1187/])
AMBARI-8680. Incorrect hive.metastore.uris value after adding Hive Metastore 
via Service Actions (alexantonenko) (hiveww: 
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=01d898529e5f2cf33fd4ba14b1839eb7043c133b)
* ambari-web/app/controllers/main/host/details.js


 Incorrect hive.metastore.uris value after adding Hive Metastore via Service 
 Actions
 ---

 Key: AMBARI-8680
 URL: https://issues.apache.org/jira/browse/AMBARI-8680
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.0.0

 Attachments: AMBARI-8680.patch


 After cluster deploy, one more Hive Metastore component was added via Service 
 Actions menu. hive.metastore.uris was updated incorrectly (containing null 
 instead of second Metastore host name): 
 {noformat}host.name1:9083,null:9083{noformat}
 Cannot be reproduced after visiting Host Details Page.



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


[jira] [Commented] (AMBARI-8680) Incorrect hive.metastore.uris value after adding Hive Metastore via Service Actions

2014-12-12 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/AMBARI-8680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14244017#comment-14244017
 ] 

Hudson commented on AMBARI-8680:


SUCCESS: Integrated in Ambari-trunk-Commit-docker #463 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/463/])
AMBARI-8680. Incorrect hive.metastore.uris value after adding Hive Metastore 
via Service Actions (alexantonenko) (hiveww: 
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=01d898529e5f2cf33fd4ba14b1839eb7043c133b)
* ambari-web/app/controllers/main/host/details.js


 Incorrect hive.metastore.uris value after adding Hive Metastore via Service 
 Actions
 ---

 Key: AMBARI-8680
 URL: https://issues.apache.org/jira/browse/AMBARI-8680
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.0.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.0.0

 Attachments: AMBARI-8680.patch


 After cluster deploy, one more Hive Metastore component was added via Service 
 Actions menu. hive.metastore.uris was updated incorrectly (containing null 
 instead of second Metastore host name): 
 {noformat}host.name1:9083,null:9083{noformat}
 Cannot be reproduced after visiting Host Details Page.



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