[jira] [Commented] (AMBARI-17732) 'Advanced hive-atlas-application.properties' is not opened by default upon using properties filter

2016-07-15 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-17732:
-

SUCCESS: Integrated in Ambari-trunk-Commit #5316 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5316/])
AMBARI-17732 'Advanced hive-atlas-application.properties' is not opened 
(ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0458940b9308c2c95f14be59da974700894bf991])
* ambari-web/app/views/common/configs/service_configs_by_category_view.js


> 'Advanced hive-atlas-application.properties' is not opened by default upon 
> using properties filter
> --
>
> Key: AMBARI-17732
> URL: https://issues.apache.org/jira/browse/AMBARI-17732
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17732.patch
>
>
> - Navigate to Hive configs page
> - In the Properties filter, add 'false' to filter all the properties whose 
> name,value or description has false. As in the screenshot attached 'Advanced 
> hive-atlas-application.properties' is not opened by default. It contains the 
> property 'atlas.hook.hive.synchronous'.
> Same behavior in falcon configs as well.



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


[jira] [Commented] (AMBARI-17732) 'Advanced hive-atlas-application.properties' is not opened by default upon using properties filter

2016-07-15 Thread Andrii Babiichuk (JIRA)

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

Andrii Babiichuk commented on AMBARI-17732:
---

tested manually

> 'Advanced hive-atlas-application.properties' is not opened by default upon 
> using properties filter
> --
>
> Key: AMBARI-17732
> URL: https://issues.apache.org/jira/browse/AMBARI-17732
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17732.patch
>
>
> - Navigate to Hive configs page
> - In the Properties filter, add 'false' to filter all the properties whose 
> name,value or description has false. As in the screenshot attached 'Advanced 
> hive-atlas-application.properties' is not opened by default. It contains the 
> property 'atlas.hook.hive.synchronous'.
> Same behavior in falcon configs as well.



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


[jira] [Commented] (AMBARI-17732) 'Advanced hive-atlas-application.properties' is not opened by default upon using properties filter

2016-07-15 Thread Hadoop QA (JIRA)

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

Hadoop QA commented on AMBARI-17732:


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

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

This message is automatically generated.

> 'Advanced hive-atlas-application.properties' is not opened by default upon 
> using properties filter
> --
>
> Key: AMBARI-17732
> URL: https://issues.apache.org/jira/browse/AMBARI-17732
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17732.patch
>
>
> - Navigate to Hive configs page
> - In the Properties filter, add 'false' to filter all the properties whose 
> name,value or description has false. As in the screenshot attached 'Advanced 
> hive-atlas-application.properties' is not opened by default. It contains the 
> property 'atlas.hook.hive.synchronous'.
> Same behavior in falcon configs as well.



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


[jira] [Commented] (AMBARI-17732) 'Advanced hive-atlas-application.properties' is not opened by default upon using properties filter

2016-07-15 Thread Andrii Tkach (JIRA)

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

Andrii Tkach commented on AMBARI-17732:
---

+1 for the patch

> 'Advanced hive-atlas-application.properties' is not opened by default upon 
> using properties filter
> --
>
> Key: AMBARI-17732
> URL: https://issues.apache.org/jira/browse/AMBARI-17732
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17732.patch
>
>
> - Navigate to Hive configs page
> - In the Properties filter, add 'false' to filter all the properties whose 
> name,value or description has false. As in the screenshot attached 'Advanced 
> hive-atlas-application.properties' is not opened by default. It contains the 
> property 'atlas.hook.hive.synchronous'.
> Same behavior in falcon configs as well.



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