[jira] [Commented] (AMBARI-20657) Usability: screen jumps when you scroll down

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20657:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1357 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1357/])
AMBARI-20657. Usability: screen jumps when you scroll down (pallavkul) 
(pallavkul: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cfb1bcc7e7d708465da68569abc2c0c765f11fa7])
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/styles/bootstrap-overrides.scss
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/application.hbs
* (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss


> Usability: screen jumps when you scroll down
> 
>
> Key: AMBARI-20657
> URL: https://issues.apache.org/jira/browse/AMBARI-20657
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.1
>
> Attachments: AMBARI-20657-trunk.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20660) HiveView2.0 scrolling in query tab does not work properly for a longer query

[Pallav Kulshreshtha (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pallav Kulshreshtha updated AMBARI-20660:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to trunk and branch-2.5

> HiveView2.0 scrolling in query tab does not work properly for a longer query
> 
>
> Key: AMBARI-20660
> URL: https://issues.apache.org/jira/browse/AMBARI-20660
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.1
>
> Attachments: AMBARI-20660-trunk.patch
>
>
> It does not scroll properly for a long query. Also when I press ENTER on the 
> last line and start typing in the new line, it does not show properly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20657) Usability: screen jumps when you scroll down

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20657:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7239 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7239/])
AMBARI-20657. Usability: screen jumps when you scroll down (pallavkul) 
(pallavkul: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b4fc47f5ea849a5e8fafea0842397fbb1d73272c])
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/application.hbs
* (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/styles/bootstrap-overrides.scss


> Usability: screen jumps when you scroll down
> 
>
> Key: AMBARI-20657
> URL: https://issues.apache.org/jira/browse/AMBARI-20657
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.1
>
> Attachments: AMBARI-20657-trunk.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20675) Repetitive operation in hdfs.py

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20675:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12862013/screenshot-1.png
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11302//console

This message is automatically generated.

> Repetitive operation in hdfs.py
> ---
>
> Key: AMBARI-20675
> URL: https://issues.apache.org/jira/browse/AMBARI-20675
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20675.patch, screenshot-1.png
>
>
> the method of install_snappy in hdfs.py is as follows:
> def install_snappy():
>   import params
>   Directory([params.so_target_dir_x86, params.so_target_dir_x64],
> create_parents = True,
>   )
>   Link(params.so_target_x86,
>to=params.so_src_x86,
>   )
>   Link(params.so_target_x64,
>to=params.so_src_x64,
>   )
>  is repetitived.
> so it's better remove one



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20657) Usability: screen jumps when you scroll down

[Pallav Kulshreshtha (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pallav Kulshreshtha updated AMBARI-20657:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

committed to trunk and branch-2.5

> Usability: screen jumps when you scroll down
> 
>
> Key: AMBARI-20657
> URL: https://issues.apache.org/jira/browse/AMBARI-20657
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.1
>
> Attachments: AMBARI-20657-trunk.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20657) Usability: screen jumps when you scroll down

[Pallav Kulshreshtha (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pallav Kulshreshtha updated AMBARI-20657:
-
Status: Patch Available  (was: Open)

> Usability: screen jumps when you scroll down
> 
>
> Key: AMBARI-20657
> URL: https://issues.apache.org/jira/browse/AMBARI-20657
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
> Fix For: 2.5.1
>
> Attachments: AMBARI-20657-trunk.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20675) Repetitive operation in hdfs.py

[zhangxiaolu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

zhangxiaolu updated AMBARI-20675:
-
Fix Version/s: trunk
   Status: Patch Available  (was: In Progress)

> Repetitive operation in hdfs.py
> ---
>
> Key: AMBARI-20675
> URL: https://issues.apache.org/jira/browse/AMBARI-20675
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20675.patch, screenshot-1.png
>
>
> the method of install_snappy in hdfs.py is as follows:
> def install_snappy():
>   import params
>   Directory([params.so_target_dir_x86, params.so_target_dir_x64],
> create_parents = True,
>   )
>   Link(params.so_target_x86,
>to=params.so_src_x86,
>   )
>   Link(params.so_target_x64,
>to=params.so_src_x64,
>   )
>  is repetitived.
> so it's better remove one



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20675) Repetitive operation in hdfs.py

[zhangxiaolu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

zhangxiaolu updated AMBARI-20675:
-
Attachment: screenshot-1.png

> Repetitive operation in hdfs.py
> ---
>
> Key: AMBARI-20675
> URL: https://issues.apache.org/jira/browse/AMBARI-20675
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Fix For: trunk
>
> Attachments: AMBARI-20675.patch, screenshot-1.png
>
>
> the method of install_snappy in hdfs.py is as follows:
> def install_snappy():
>   import params
>   Directory([params.so_target_dir_x86, params.so_target_dir_x64],
> create_parents = True,
>   )
>   Link(params.so_target_x86,
>to=params.so_src_x86,
>   )
>   Link(params.so_target_x64,
>to=params.so_src_x64,
>   )
>  is repetitived.
> so it's better remove one



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20675) Repetitive operation in hdfs.py

[zhangxiaolu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

zhangxiaolu updated AMBARI-20675:
-
Attachment: AMBARI-20675.patch

> Repetitive operation in hdfs.py
> ---
>
> Key: AMBARI-20675
> URL: https://issues.apache.org/jira/browse/AMBARI-20675
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
> Attachments: AMBARI-20675.patch
>
>
> the method of install_snappy in hdfs.py is as follows:
> def install_snappy():
>   import params
>   Directory([params.so_target_dir_x86, params.so_target_dir_x64],
> create_parents = True,
>   )
>   Link(params.so_target_x86,
>to=params.so_src_x86,
>   )
>   Link(params.so_target_x64,
>to=params.so_src_x64,
>   )
>  is repetitived.
> so it's better remove one



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20675) Repetitive operation in hdfs.py

[zhangxiaolu (JIRA)]

zhangxiaolu created AMBARI-20675:


 Summary: Repetitive operation in hdfs.py
 Key: AMBARI-20675
 URL: https://issues.apache.org/jira/browse/AMBARI-20675
 Project: Ambari
  Issue Type: Bug
Affects Versions: trunk
Reporter: zhangxiaolu
Assignee: zhangxiaolu


the method of install_snappy in hdfs.py is as follows:
def install_snappy():
  import params
  Directory([params.so_target_dir_x86, params.so_target_dir_x64],
create_parents = True,
  )
  Link(params.so_target_x86,
   to=params.so_src_x86,
  )
  Link(params.so_target_x64,
   to=params.so_src_x64,
  )
 is repetitived.
so it's better remove one







--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20551:
---
Attachment: AMBARI-20551.patch

> Blueprint export fails if config-type is not mapped to any service after 
> upgrade
> 
>
> Key: AMBARI-20551
> URL: https://issues.apache.org/jira/browse/AMBARI-20551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20551.patch
>
>
> 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - 
> Bad request:
> java.lang.IllegalArgumentException: Specified configuration type is not 
> associated with any service: storm-site
> at 
> org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141)
> at 
> org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839)
> at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223)
> at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91)
> at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20551:
---
Status: Open  (was: Patch Available)

> Blueprint export fails if config-type is not mapped to any service after 
> upgrade
> 
>
> Key: AMBARI-20551
> URL: https://issues.apache.org/jira/browse/AMBARI-20551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20551.patch
>
>
> 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - 
> Bad request:
> java.lang.IllegalArgumentException: Specified configuration type is not 
> associated with any service: storm-site
> at 
> org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141)
> at 
> org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839)
> at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223)
> at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91)
> at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20551:
---
Attachment: (was: AMBARI-20551.patch)

> Blueprint export fails if config-type is not mapped to any service after 
> upgrade
> 
>
> Key: AMBARI-20551
> URL: https://issues.apache.org/jira/browse/AMBARI-20551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20551.patch
>
>
> 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - 
> Bad request:
> java.lang.IllegalArgumentException: Specified configuration type is not 
> associated with any service: storm-site
> at 
> org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141)
> at 
> org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839)
> at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223)
> at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91)
> at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20551:
---
Status: Patch Available  (was: In Progress)

> Blueprint export fails if config-type is not mapped to any service after 
> upgrade
> 
>
> Key: AMBARI-20551
> URL: https://issues.apache.org/jira/browse/AMBARI-20551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20551.patch
>
>
> 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - 
> Bad request:
> java.lang.IllegalArgumentException: Specified configuration type is not 
> associated with any service: storm-site
> at 
> org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141)
> at 
> org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839)
> at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223)
> at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91)
> at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20366:
---
Status: Patch Available  (was: In Progress)

> Tokenize kerberos principal name appearing in kerberos rules in exported 
> blueprint
> --
>
> Key: AMBARI-20366
> URL: https://issues.apache.org/jira/browse/AMBARI-20366
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20366.patch
>
>
> If blueprint is exported from a kerberos enabled cluster Kerberos rules 
> export principal names which contain cluster name and Realm, this exports 
> existing cluster name and realm name as tokens and replaces those tokens with 
> new values of cluster name and realm during successive cluster deployments.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20366:
---
Attachment: AMBARI-20366.patch

> Tokenize kerberos principal name appearing in kerberos rules in exported 
> blueprint
> --
>
> Key: AMBARI-20366
> URL: https://issues.apache.org/jira/browse/AMBARI-20366
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20366.patch
>
>
> If blueprint is exported from a kerberos enabled cluster Kerberos rules 
> export principal names which contain cluster name and Realm, this exports 
> existing cluster name and realm name as tokens and replaces those tokens with 
> new values of cluster name and realm during successive cluster deployments.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20366:
---
Status: Open  (was: Patch Available)

> Tokenize kerberos principal name appearing in kerberos rules in exported 
> blueprint
> --
>
> Key: AMBARI-20366
> URL: https://issues.apache.org/jira/browse/AMBARI-20366
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
>
> If blueprint is exported from a kerberos enabled cluster Kerberos rules 
> export principal names which contain cluster name and Realm, this exports 
> existing cluster name and realm name as tokens and replaces those tokens with 
> new values of cluster name and realm during successive cluster deployments.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20366) Tokenize kerberos principal name appearing in kerberos rules in exported blueprint

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20366:
---
Attachment: (was: AMBARI-20366.patch)

> Tokenize kerberos principal name appearing in kerberos rules in exported 
> blueprint
> --
>
> Key: AMBARI-20366
> URL: https://issues.apache.org/jira/browse/AMBARI-20366
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
>
> If blueprint is exported from a kerberos enabled cluster Kerberos rules 
> export principal names which contain cluster name and Realm, this exports 
> existing cluster name and realm name as tokens and replaces those tokens with 
> new values of cluster name and realm during successive cluster deployments.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20651) When in Upgrade paused state, links should be disabled for less privileged user

[Richard Zang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zang updated AMBARI-20651:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and 2.5 174c0402f76abc88b08ad9a2b4b2cdf1653c4902

> When in Upgrade paused state, links should be disabled for less privileged 
> user
> ---
>
> Key: AMBARI-20651
> URL: https://issues.apache.org/jira/browse/AMBARI-20651
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.1
>
> Attachments: AMBARI-20651.patch
>
>
> When in Upgrade paused state, links should be disabled for less privileged 
> user



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20651) When in Upgrade paused state, links should be disabled for less privileged user

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20651:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1356 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1356/])
AMBARI-20651 - When in Upgrade paused state, links should be disabled (rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=174c0402f76abc88b08ad9a2b4b2cdf1653c4902])
* (edit) ambari-web/app/templates/application.hbs
* (edit) ambari-web/app/controllers/application.js


> When in Upgrade paused state, links should be disabled for less privileged 
> user
> ---
>
> Key: AMBARI-20651
> URL: https://issues.apache.org/jira/browse/AMBARI-20651
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.1
>
> Attachments: AMBARI-20651.patch
>
>
> When in Upgrade paused state, links should be disabled for less privileged 
> user



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20651) When in Upgrade paused state, links should be disabled for less privileged user

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20651:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7238 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7238/])
AMBARI-20651 - When in Upgrade paused state, links should be disabled (rzang: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b491509ab65353494d8660e2954c87c3a6f1abf4])
* (edit) ambari-web/app/controllers/application.js


> When in Upgrade paused state, links should be disabled for less privileged 
> user
> ---
>
> Key: AMBARI-20651
> URL: https://issues.apache.org/jira/browse/AMBARI-20651
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.1
>
> Attachments: AMBARI-20651.patch
>
>
> When in Upgrade paused state, links should be disabled for less privileged 
> user



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20672) Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20672:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7237 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7237/])
AMBARI-20672 - Cluster Merge At End Of Upgrade Creation Cascades (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8c2ff91c7c632d01c35dec160b0debdab730ca82])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java


> Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily
> ---
>
> Key: AMBARI-20672
> URL: https://issues.apache.org/jira/browse/AMBARI-20672
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20672.patch
>
>
> During the creation of an upgrade, an association is made between the 
> ClusterEntity and the UpgradeEntity so that determining if an upgrade is in 
> progress can be fast. 
> {code}
> upgradeEntity.setRequestId(request.getId());
> request.persist();
> s_upgradeDAO.create(upgradeEntity);
> cluster.setUpgradeEntity(upgradeEntity);
> {code}
> {code}
>   public void setUpgradeEntity(UpgradeEntity upgradeEntity) throws 
> AmbariException {
> try {
>   ClusterEntity clusterEntity = getClusterEntity();
>   clusterEntity.setUpgradeEntity(upgradeEntity);
>   clusterDAO.merge(clusterEntity);
> ...
> {code}
> The problem here is that the merge is propagated to the UpgradeEntity via a 
> {{CascadeType.ALL}} and it's not necessary. It seems like the only cascade 
> should be {{CascadeType.REMOVE}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20672) Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20672:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1355 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1355/])
AMBARI-20672 - Cluster Merge At End Of Upgrade Creation Cascades (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4bdcbb038c8d941f84681b45112f9df5dfca24ad])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java


> Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily
> ---
>
> Key: AMBARI-20672
> URL: https://issues.apache.org/jira/browse/AMBARI-20672
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20672.patch
>
>
> During the creation of an upgrade, an association is made between the 
> ClusterEntity and the UpgradeEntity so that determining if an upgrade is in 
> progress can be fast. 
> {code}
> upgradeEntity.setRequestId(request.getId());
> request.persist();
> s_upgradeDAO.create(upgradeEntity);
> cluster.setUpgradeEntity(upgradeEntity);
> {code}
> {code}
>   public void setUpgradeEntity(UpgradeEntity upgradeEntity) throws 
> AmbariException {
> try {
>   ClusterEntity clusterEntity = getClusterEntity();
>   clusterEntity.setUpgradeEntity(upgradeEntity);
>   clusterDAO.merge(clusterEntity);
> ...
> {code}
> The problem here is that the merge is propagated to the UpgradeEntity via a 
> {{CascadeType.ALL}} and it's not necessary. It seems like the only cascade 
> should be {{CascadeType.REMOVE}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20672) Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20672:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1354 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1354/])
AMBARI-20672 - Cluster Merge At End Of Upgrade Creation Cascades (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dde4e05cfc4106e2067e21b3593bb6609bd3407a])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeActionTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/services/RetryUpgradeActionServiceTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UpgradeEntity.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/UpgradeDAOTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertStateChangedListener.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/services/RetryUpgradeActionService.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UpgradeDAO.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterEntity.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceComponentTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/StackVersionListener.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/events/listeners/upgrade/StackVersionListenerTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeSummaryResourceProviderTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java


> Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily
> ---
>
> Key: AMBARI-20672
> URL: https://issues.apache.org/jira/browse/AMBARI-20672
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20672.patch
>
>
> During the creation of an upgrade, an association is made between the 
> ClusterEntity and the UpgradeEntity so that determining if an upgrade is in 
> progress can be fast. 
> {code}
> upgradeEntity.setRequestId(request.getId());
> request.persist();
> s_upgradeDAO.create(upgradeEntity);
> cluster.setUpgradeEntity(upgradeEntity);
> {code}
> {code}
>   public void setUpgradeEntity(UpgradeEntity upgradeEntity) throws 
> AmbariException {
> try {
>   ClusterEntity clusterEntity = getClusterEntity();
>   clusterEntity.setUpgradeEntity(upgradeEntity);
>   clusterDAO.merge(clusterEntity);
> ...
> {code}
> The problem here is that the merge is propagated to the UpgradeEntity via a 
> {{CascadeType.ALL}} and it's not necessary. It seems like the only cascade 
> should be {{CascadeType.REMOVE}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20672) Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20672:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7236 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7236/])
AMBARI-20672 - Cluster Merge At End Of Upgrade Creation Cascades (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fe0aa448bd16a225ccb0bab8315fd2b8b34fba75])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeActionTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/UpgradeDAO.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceComponentTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/StackVersionListener.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/services/RetryUpgradeActionService.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/alerts/AlertStateChangedListener.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/UpgradeEntity.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeSummaryResourceProviderTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/UpgradeDAOTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/events/listeners/upgrade/StackVersionListenerTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterEntity.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/services/RetryUpgradeActionServiceTest.java


> Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily
> ---
>
> Key: AMBARI-20672
> URL: https://issues.apache.org/jira/browse/AMBARI-20672
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20672.patch
>
>
> During the creation of an upgrade, an association is made between the 
> ClusterEntity and the UpgradeEntity so that determining if an upgrade is in 
> progress can be fast. 
> {code}
> upgradeEntity.setRequestId(request.getId());
> request.persist();
> s_upgradeDAO.create(upgradeEntity);
> cluster.setUpgradeEntity(upgradeEntity);
> {code}
> {code}
>   public void setUpgradeEntity(UpgradeEntity upgradeEntity) throws 
> AmbariException {
> try {
>   ClusterEntity clusterEntity = getClusterEntity();
>   clusterEntity.setUpgradeEntity(upgradeEntity);
>   clusterDAO.merge(clusterEntity);
> ...
> {code}
> The problem here is that the merge is propagated to the UpgradeEntity via a 
> {{CascadeType.ALL}} and it's not necessary. It seems like the only cascade 
> should be {{CascadeType.REMOVE}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20673) For sort/partition operator, if there is only 1 reducer, display just "sort" rather than "sort/partition"

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20673:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12861916/AMBARI-20673-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:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 core tests{color}.  The test build failed in 
contrib/views/hive20 

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

This message is automatically generated.

> For sort/partition operator, if there is only 1 reducer, display just "sort" 
> rather than "sort/partition"
> -
>
> Key: AMBARI-20673
> URL: https://issues.apache.org/jira/browse/AMBARI-20673
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.5.1
>
> Attachments: AMBARI-20673-trunk.patch
>
>
> For sort/partition operator, if there is only 1 reducer, display just "sort" 
> rather than "sort/partition" in visual explain graph



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20672) Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily

[Jonathan Hurley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Hurley updated AMBARI-20672:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily
> ---
>
> Key: AMBARI-20672
> URL: https://issues.apache.org/jira/browse/AMBARI-20672
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20672.patch
>
>
> During the creation of an upgrade, an association is made between the 
> ClusterEntity and the UpgradeEntity so that determining if an upgrade is in 
> progress can be fast. 
> {code}
> upgradeEntity.setRequestId(request.getId());
> request.persist();
> s_upgradeDAO.create(upgradeEntity);
> cluster.setUpgradeEntity(upgradeEntity);
> {code}
> {code}
>   public void setUpgradeEntity(UpgradeEntity upgradeEntity) throws 
> AmbariException {
> try {
>   ClusterEntity clusterEntity = getClusterEntity();
>   clusterEntity.setUpgradeEntity(upgradeEntity);
>   clusterDAO.merge(clusterEntity);
> ...
> {code}
> The problem here is that the merge is propagated to the UpgradeEntity via a 
> {{CascadeType.ALL}} and it's not necessary. It seems like the only cascade 
> should be {{CascadeType.REMOVE}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20672) Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20672:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12861921/AMBARI-20672.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 8 new 
or modified test files.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  
org.apache.ambari.server.state.alerts.AlertStateChangedEventTest

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

This message is automatically generated.

> Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily
> ---
>
> Key: AMBARI-20672
> URL: https://issues.apache.org/jira/browse/AMBARI-20672
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20672.patch
>
>
> During the creation of an upgrade, an association is made between the 
> ClusterEntity and the UpgradeEntity so that determining if an upgrade is in 
> progress can be fast. 
> {code}
> upgradeEntity.setRequestId(request.getId());
> request.persist();
> s_upgradeDAO.create(upgradeEntity);
> cluster.setUpgradeEntity(upgradeEntity);
> {code}
> {code}
>   public void setUpgradeEntity(UpgradeEntity upgradeEntity) throws 
> AmbariException {
> try {
>   ClusterEntity clusterEntity = getClusterEntity();
>   clusterEntity.setUpgradeEntity(upgradeEntity);
>   clusterDAO.merge(clusterEntity);
> ...
> {code}
> The problem here is that the merge is propagated to the UpgradeEntity via a 
> {{CascadeType.ALL}} and it's not necessary. It seems like the only cascade 
> should be {{CascadeType.REMOVE}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20551:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12861922/AMBARI-20551.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler 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/11299//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11299//console

This message is automatically generated.

> Blueprint export fails if config-type is not mapped to any service after 
> upgrade
> 
>
> Key: AMBARI-20551
> URL: https://issues.apache.org/jira/browse/AMBARI-20551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20551.patch
>
>
> 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - 
> Bad request:
> java.lang.IllegalArgumentException: Specified configuration type is not 
> associated with any service: storm-site
> at 
> org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141)
> at 
> org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839)
> at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223)
> at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91)
> at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20674) About to hide the Delete menu item from UI for a given service

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20674:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12861937/AMBARI-20674.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 3 new 
or modified test files.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server ambari-web.

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

This message is automatically generated.

> About to hide the Delete menu item from UI for a given service 
> ---
>
> Key: AMBARI-20674
> URL: https://issues.apache.org/jira/browse/AMBARI-20674
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server, ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20674.patch
>
>
> Stack driven approach to have UI show/hide Delete service menu item for a 
> given service.
> A service's metainfo.xml can have 
> false set at the service level to 
> indicate UI should hide the menu item. Directly going thru REST API calls are 
> always supported and non-restricted. 
> If the section is missing, it will be treated as "support" UI delete service 
> operation. In other words, UI only hides the menu item if metainfo.xml has 
> explicitly set the flag to false.
> Example.
> "" +
> "  2.0" +
> "  " +
> "" +
> "  HDFS" +
> "  HDFS" +
> "  false" +
> "" +
> "  " +
> "";



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20592) ServicePresences check should also check for services dropped from a release

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20592:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7235 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7235/])
AMBARI-20592 ServicePresences check should also check for services (dili: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3ca41f26205de3ac6c316dde749abcedf4082509])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/ServicePresenceCheck.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicePresenceCheckTest.java


> ServicePresences check should also check for services dropped from a release
> 
>
> Key: AMBARI-20592
> URL: https://issues.apache.org/jira/browse/AMBARI-20592
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20592.patch, AMBARI-20592-v2.patch, 
> AMBARI-20592-v3-rebase.patch
>
>
> ServicePresence check currently checks the following two cases
> 1. services that do not support upgrade, and must be reinstalled post EU/RU
> 2. services replaced by other services in the new release, where the old 
> service must be dropped before EU/RU, and the replacement can be added post 
> the stack upgrade.
> The JIRA is to add one more use case to the check, that;s to check for 
> services dropped from the new release (end of life)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20674) About to hide the Delete menu item from UI for a given service

[Di Li (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Di Li updated AMBARI-20674:
---
Status: Patch Available  (was: Open)

> About to hide the Delete menu item from UI for a given service 
> ---
>
> Key: AMBARI-20674
> URL: https://issues.apache.org/jira/browse/AMBARI-20674
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server, ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20674.patch
>
>
> Stack driven approach to have UI show/hide Delete service menu item for a 
> given service.
> A service's metainfo.xml can have 
> false set at the service level to 
> indicate UI should hide the menu item. Directly going thru REST API calls are 
> always supported and non-restricted. 
> If the section is missing, it will be treated as "support" UI delete service 
> operation. In other words, UI only hides the menu item if metainfo.xml has 
> explicitly set the flag to false.
> Example.
> "" +
> "  2.0" +
> "  " +
> "" +
> "  HDFS" +
> "  HDFS" +
> "  false" +
> "" +
> "  " +
> "";



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20674) About to hide the Delete menu item from UI for a given service

[Di Li (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Di Li updated AMBARI-20674:
---
Attachment: AMBARI-20674.patch

> About to hide the Delete menu item from UI for a given service 
> ---
>
> Key: AMBARI-20674
> URL: https://issues.apache.org/jira/browse/AMBARI-20674
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server, ambari-web
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20674.patch
>
>
> Stack driven approach to have UI show/hide Delete service menu item for a 
> given service.
> A service's metainfo.xml can have 
> false set at the service level to 
> indicate UI should hide the menu item. Directly going thru REST API calls are 
> always supported and non-restricted. 
> If the section is missing, it will be treated as "support" UI delete service 
> operation. In other words, UI only hides the menu item if metainfo.xml has 
> explicitly set the flag to false.
> Example.
> "" +
> "  2.0" +
> "  " +
> "" +
> "  HDFS" +
> "  HDFS" +
> "  false" +
> "" +
> "  " +
> "";



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20674) About to hide the Delete menu item from UI for a given service

[Di Li (JIRA)]

Di Li created AMBARI-20674:
--

 Summary: About to hide the Delete menu item from UI for a given 
service 
 Key: AMBARI-20674
 URL: https://issues.apache.org/jira/browse/AMBARI-20674
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-server, ambari-web
Affects Versions: trunk
Reporter: Di Li
Assignee: Di Li
 Fix For: trunk


Stack driven approach to have UI show/hide Delete service menu item for a given 
service.

A service's metainfo.xml can have 

false set at the service level to 
indicate UI should hide the menu item. Directly going thru REST API calls are 
always supported and non-restricted. 

If the section is missing, it will be treated as "support" UI delete service 
operation. In other words, UI only hides the menu item if metainfo.xml has 
explicitly set the flag to false.

Example.
"" +
"  2.0" +
"  " +
"" +
"  HDFS" +
"  HDFS" +
"  false" +
"" +
"  " +
"";



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20592) ServicePresences check should also check for services dropped from a release

[Di Li (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Di Li updated AMBARI-20592:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> ServicePresences check should also check for services dropped from a release
> 
>
> Key: AMBARI-20592
> URL: https://issues.apache.org/jira/browse/AMBARI-20592
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20592.patch, AMBARI-20592-v2.patch, 
> AMBARI-20592-v3-rebase.patch
>
>
> ServicePresence check currently checks the following two cases
> 1. services that do not support upgrade, and must be reinstalled post EU/RU
> 2. services replaced by other services in the new release, where the old 
> service must be dropped before EU/RU, and the replacement can be added post 
> the stack upgrade.
> The JIRA is to add one more use case to the check, that;s to check for 
> services dropped from the new release (end of life)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20592) ServicePresences check should also check for services dropped from a release

[Di Li (JIRA)]

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

Di Li commented on AMBARI-20592:


pushed to trunk as 
https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=3ca41f26205de3ac6c316dde749abcedf4082509

> ServicePresences check should also check for services dropped from a release
> 
>
> Key: AMBARI-20592
> URL: https://issues.apache.org/jira/browse/AMBARI-20592
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20592.patch, AMBARI-20592-v2.patch, 
> AMBARI-20592-v3-rebase.patch
>
>
> ServicePresence check currently checks the following two cases
> 1. services that do not support upgrade, and must be reinstalled post EU/RU
> 2. services replaced by other services in the new release, where the old 
> service must be dropped before EU/RU, and the replacement can be added post 
> the stack upgrade.
> The JIRA is to add one more use case to the check, that;s to check for 
> services dropped from the new release (end of life)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20592) ServicePresences check should also check for services dropped from a release

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20592:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12861910/AMBARI-20592-v3-rebase.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler 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/11297//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11297//console

This message is automatically generated.

> ServicePresences check should also check for services dropped from a release
> 
>
> Key: AMBARI-20592
> URL: https://issues.apache.org/jira/browse/AMBARI-20592
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20592.patch, AMBARI-20592-v2.patch, 
> AMBARI-20592-v3-rebase.patch
>
>
> ServicePresence check currently checks the following two cases
> 1. services that do not support upgrade, and must be reinstalled post EU/RU
> 2. services replaced by other services in the new release, where the old 
> service must be dropped before EU/RU, and the replacement can be added post 
> the stack upgrade.
> The JIRA is to add one more use case to the check, that;s to check for 
> services dropped from the new release (end of life)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20671) Host checks: incorrect message for single host warnings

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20671:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7234 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7234/])
AMBARI-20671 Host checks: incorrect message for single host warnings. 
(ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6ee881bcf22016fa0213a11a13fc3b93356caabf])
* (edit) ambari-web/app/templates/wizard/step3/step3_host_warnings_popup.hbs
* (edit) ambari-web/app/controllers/wizard/step3_controller.js
* (edit) ambari-web/app/mixins/main/host/details/actions/check_host.js
* (edit) ambari-web/test/controllers/wizard/step3_test.js


> Host checks: incorrect message for single host warnings
> ---
>
> Key: AMBARI-20671
> URL: https://issues.apache.org/jira/browse/AMBARI-20671
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20671.patch, host-checks.jpg
>
>
> If there are some warnings for single host in [host checks 
> popup|^host-checks.jpg], messages for them are incorrect ('1 hosts' instead 
> of '1 host').



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20551:
---
Status: Patch Available  (was: In Progress)

> Blueprint export fails if config-type is not mapped to any service after 
> upgrade
> 
>
> Key: AMBARI-20551
> URL: https://issues.apache.org/jira/browse/AMBARI-20551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20551.patch
>
>
> 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - 
> Bad request:
> java.lang.IllegalArgumentException: Specified configuration type is not 
> associated with any service: storm-site
> at 
> org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141)
> at 
> org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839)
> at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223)
> at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91)
> at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20551:
---
Status: Open  (was: Patch Available)

> Blueprint export fails if config-type is not mapped to any service after 
> upgrade
> 
>
> Key: AMBARI-20551
> URL: https://issues.apache.org/jira/browse/AMBARI-20551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20551.patch
>
>
> 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - 
> Bad request:
> java.lang.IllegalArgumentException: Specified configuration type is not 
> associated with any service: storm-site
> at 
> org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141)
> at 
> org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839)
> at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223)
> at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91)
> at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20551:
---
Attachment: AMBARI-20551.patch

> Blueprint export fails if config-type is not mapped to any service after 
> upgrade
> 
>
> Key: AMBARI-20551
> URL: https://issues.apache.org/jira/browse/AMBARI-20551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-20551.patch
>
>
> 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - 
> Bad request:
> java.lang.IllegalArgumentException: Specified configuration type is not 
> associated with any service: storm-site
> at 
> org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141)
> at 
> org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839)
> at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223)
> at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91)
> at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20551) Blueprint export fails if config-type is not mapped to any service after upgrade

[Amruta Borkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amruta Borkar updated AMBARI-20551:
---
Attachment: (was: AMBARI-20551.patch)

> Blueprint export fails if config-type is not mapped to any service after 
> upgrade
> 
>
> Key: AMBARI-20551
> URL: https://issues.apache.org/jira/browse/AMBARI-20551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, blueprints
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
>
> 20 Mar 2017 11:39:57,948 ERROR [ambari-client-thread-8726] ReadHandler:99 - 
> Bad request:
> java.lang.IllegalArgumentException: Specified configuration type is not 
> associated with any service: storm-site
> at 
> org.apache.ambari.server.controller.internal.Stack.getServiceForConfigType(Stack.java:494)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor$StackPropertyTypeFilter.isPropertyIncluded(BlueprintConfigurationProcessor.java:2946)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.shouldPropertyBeExcludedForBlueprintExport(BlueprintConfigurationProcessor.java:939)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doFilterPriorToExport(BlueprintConfigurationProcessor.java:439)
> at 
> org.apache.ambari.server.controller.internal.BlueprintConfigurationProcessor.doUpdateForBlueprintExport(BlueprintConfigurationProcessor.java:416)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.createBlueprintResource(ClusterBlueprintRenderer.java:186)
> at 
> org.apache.ambari.server.api.query.render.ClusterBlueprintRenderer.finalizeResult(ClusterBlueprintRenderer.java:141)
> at 
> org.apache.ambari.server.api.query.QueryImpl.getResult(QueryImpl.java:839)
> at 
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:223)
> at 
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at 
> org.apache.ambari.server.api.services.ClusterService.getCluster(ClusterService.java:91)
> at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20672) Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily

[Jonathan Hurley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Hurley updated AMBARI-20672:
-
Attachment: AMBARI-20672.patch

> Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily
> ---
>
> Key: AMBARI-20672
> URL: https://issues.apache.org/jira/browse/AMBARI-20672
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20672.patch
>
>
> During the creation of an upgrade, an association is made between the 
> ClusterEntity and the UpgradeEntity so that determining if an upgrade is in 
> progress can be fast. 
> {code}
> upgradeEntity.setRequestId(request.getId());
> request.persist();
> s_upgradeDAO.create(upgradeEntity);
> cluster.setUpgradeEntity(upgradeEntity);
> {code}
> {code}
>   public void setUpgradeEntity(UpgradeEntity upgradeEntity) throws 
> AmbariException {
> try {
>   ClusterEntity clusterEntity = getClusterEntity();
>   clusterEntity.setUpgradeEntity(upgradeEntity);
>   clusterDAO.merge(clusterEntity);
> ...
> {code}
> The problem here is that the merge is propagated to the UpgradeEntity via a 
> {{CascadeType.ALL}} and it's not necessary. It seems like the only cascade 
> should be {{CascadeType.REMOVE}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20672) Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily

[Jonathan Hurley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Hurley updated AMBARI-20672:
-
Status: Patch Available  (was: Open)

> Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily
> ---
>
> Key: AMBARI-20672
> URL: https://issues.apache.org/jira/browse/AMBARI-20672
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20672.patch
>
>
> During the creation of an upgrade, an association is made between the 
> ClusterEntity and the UpgradeEntity so that determining if an upgrade is in 
> progress can be fast. 
> {code}
> upgradeEntity.setRequestId(request.getId());
> request.persist();
> s_upgradeDAO.create(upgradeEntity);
> cluster.setUpgradeEntity(upgradeEntity);
> {code}
> {code}
>   public void setUpgradeEntity(UpgradeEntity upgradeEntity) throws 
> AmbariException {
> try {
>   ClusterEntity clusterEntity = getClusterEntity();
>   clusterEntity.setUpgradeEntity(upgradeEntity);
>   clusterDAO.merge(clusterEntity);
> ...
> {code}
> The problem here is that the merge is propagated to the UpgradeEntity via a 
> {{CascadeType.ALL}} and it's not necessary. It seems like the only cascade 
> should be {{CascadeType.REMOVE}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20673) For sort/partition operator, if there is only 1 reducer, display just "sort" rather than "sort/partition"

[venkat (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

venkat updated AMBARI-20673:

Status: Patch Available  (was: Open)

> For sort/partition operator, if there is only 1 reducer, display just "sort" 
> rather than "sort/partition"
> -
>
> Key: AMBARI-20673
> URL: https://issues.apache.org/jira/browse/AMBARI-20673
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.5.1
>
> Attachments: AMBARI-20673-trunk.patch
>
>
> For sort/partition operator, if there is only 1 reducer, display just "sort" 
> rather than "sort/partition" in visual explain graph



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20673) For sort/partition operator, if there is only 1 reducer, display just "sort" rather than "sort/partition"

[venkat (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

venkat updated AMBARI-20673:

Attachment: AMBARI-20673-trunk.patch

> For sort/partition operator, if there is only 1 reducer, display just "sort" 
> rather than "sort/partition"
> -
>
> Key: AMBARI-20673
> URL: https://issues.apache.org/jira/browse/AMBARI-20673
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.5.1
>
> Attachments: AMBARI-20673-trunk.patch
>
>
> For sort/partition operator, if there is only 1 reducer, display just "sort" 
> rather than "sort/partition" in visual explain graph



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20673) For sort/partition operator, if there is only 1 reducer, display just "sort" rather than "sort/partition"

[venkat (JIRA)]

venkat created AMBARI-20673:
---

 Summary: For sort/partition operator, if there is only 1 reducer, 
display just "sort" rather than "sort/partition"
 Key: AMBARI-20673
 URL: https://issues.apache.org/jira/browse/AMBARI-20673
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.5.1
Reporter: venkat
Assignee: venkat
 Fix For: 2.5.1


For sort/partition operator, if there is only 1 reducer, display just "sort" 
rather than "sort/partition" in visual explain graph



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20672) Cluster Merge At End Of Upgrade Creation Cascades Unnecessarily

[Jonathan Hurley (JIRA)]

Jonathan Hurley created AMBARI-20672:


 Summary: Cluster Merge At End Of Upgrade Creation Cascades 
Unnecessarily
 Key: AMBARI-20672
 URL: https://issues.apache.org/jira/browse/AMBARI-20672
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.2
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
 Fix For: 2.5.1


During the creation of an upgrade, an association is made between the 
ClusterEntity and the UpgradeEntity so that determining if an upgrade is in 
progress can be fast. 

{code}
upgradeEntity.setRequestId(request.getId());

request.persist();

s_upgradeDAO.create(upgradeEntity);
cluster.setUpgradeEntity(upgradeEntity);
{code}

{code}
  public void setUpgradeEntity(UpgradeEntity upgradeEntity) throws 
AmbariException {
try {
  ClusterEntity clusterEntity = getClusterEntity();
  clusterEntity.setUpgradeEntity(upgradeEntity);
  clusterDAO.merge(clusterEntity);
...
{code}

The problem here is that the merge is propagated to the UpgradeEntity via a 
{{CascadeType.ALL}} and it's not necessary. It seems like the only cascade 
should be {{CascadeType.REMOVE}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20671) Host checks: incorrect message for single host warnings

[Andrii Babiichuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Babiichuk updated AMBARI-20671:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk

> Host checks: incorrect message for single host warnings
> ---
>
> Key: AMBARI-20671
> URL: https://issues.apache.org/jira/browse/AMBARI-20671
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20671.patch, host-checks.jpg
>
>
> If there are some warnings for single host in [host checks 
> popup|^host-checks.jpg], messages for them are incorrect ('1 hosts' instead 
> of '1 host').



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20671) Host checks: incorrect message for single host warnings

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20671:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12861908/AMBARI-20671.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler 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/11295//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11295//console

This message is automatically generated.

> Host checks: incorrect message for single host warnings
> ---
>
> Key: AMBARI-20671
> URL: https://issues.apache.org/jira/browse/AMBARI-20671
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20671.patch, host-checks.jpg
>
>
> If there are some warnings for single host in [host checks 
> popup|^host-checks.jpg], messages for them are incorrect ('1 hosts' instead 
> of '1 host').



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20592) ServicePresences check should also check for services dropped from a release

[Di Li (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Di Li updated AMBARI-20592:
---
Status: Patch Available  (was: In Progress)

> ServicePresences check should also check for services dropped from a release
> 
>
> Key: AMBARI-20592
> URL: https://issues.apache.org/jira/browse/AMBARI-20592
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20592.patch, AMBARI-20592-v2.patch, 
> AMBARI-20592-v3-rebase.patch
>
>
> ServicePresence check currently checks the following two cases
> 1. services that do not support upgrade, and must be reinstalled post EU/RU
> 2. services replaced by other services in the new release, where the old 
> service must be dropped before EU/RU, and the replacement can be added post 
> the stack upgrade.
> The JIRA is to add one more use case to the check, that;s to check for 
> services dropped from the new release (end of life)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20592) ServicePresences check should also check for services dropped from a release

[Di Li (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Di Li updated AMBARI-20592:
---
Attachment: AMBARI-20592-v3-rebase.patch

> ServicePresences check should also check for services dropped from a release
> 
>
> Key: AMBARI-20592
> URL: https://issues.apache.org/jira/browse/AMBARI-20592
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20592.patch, AMBARI-20592-v2.patch, 
> AMBARI-20592-v3-rebase.patch
>
>
> ServicePresence check currently checks the following two cases
> 1. services that do not support upgrade, and must be reinstalled post EU/RU
> 2. services replaced by other services in the new release, where the old 
> service must be dropped before EU/RU, and the replacement can be added post 
> the stack upgrade.
> The JIRA is to add one more use case to the check, that;s to check for 
> services dropped from the new release (end of life)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20592) ServicePresences check should also check for services dropped from a release

[Di Li (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Di Li updated AMBARI-20592:
---
Status: In Progress  (was: Patch Available)

> ServicePresences check should also check for services dropped from a release
> 
>
> Key: AMBARI-20592
> URL: https://issues.apache.org/jira/browse/AMBARI-20592
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-20592.patch, AMBARI-20592-v2.patch, 
> AMBARI-20592-v3-rebase.patch
>
>
> ServicePresence check currently checks the following two cases
> 1. services that do not support upgrade, and must be reinstalled post EU/RU
> 2. services replaced by other services in the new release, where the old 
> service must be dropped before EU/RU, and the replacement can be added post 
> the stack upgrade.
> The JIRA is to add one more use case to the check, that;s to check for 
> services dropped from the new release (end of life)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20671) Host checks: incorrect message for single host warnings

[Andrii Babiichuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Babiichuk updated AMBARI-20671:
--
Attachment: AMBARI-20671.patch

> Host checks: incorrect message for single host warnings
> ---
>
> Key: AMBARI-20671
> URL: https://issues.apache.org/jira/browse/AMBARI-20671
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20671.patch, host-checks.jpg
>
>
> If there are some warnings for single host in [host checks 
> popup|^host-checks.jpg], messages for them are incorrect ('1 hosts' instead 
> of '1 host').



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20671) Host checks: incorrect message for single host warnings

[Andrii Babiichuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Babiichuk updated AMBARI-20671:
--
Status: Patch Available  (was: Open)

> Host checks: incorrect message for single host warnings
> ---
>
> Key: AMBARI-20671
> URL: https://issues.apache.org/jira/browse/AMBARI-20671
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20671.patch, host-checks.jpg
>
>
> If there are some warnings for single host in [host checks 
> popup|^host-checks.jpg], messages for them are incorrect ('1 hosts' instead 
> of '1 host').



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20671) Host checks: incorrect message for single host warnings

[Andrii Babiichuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Babiichuk updated AMBARI-20671:
--
Attachment: host-checks.jpg

> Host checks: incorrect message for single host warnings
> ---
>
> Key: AMBARI-20671
> URL: https://issues.apache.org/jira/browse/AMBARI-20671
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: host-checks.jpg
>
>
> If there are some warnings for single host in [host checks 
> popup|^host-checks.jpg], messages for them are incorrect ('1 hosts' instead 
> of '1 host').



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20671) Host checks: incorrect message for single host warnings

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-20671:
-

 Summary: Host checks: incorrect message for single host warnings
 Key: AMBARI-20671
 URL: https://issues.apache.org/jira/browse/AMBARI-20671
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
 Fix For: 3.0.0


If there are some warnings for single host in [host checks 
popup|^host-checks.jpg], messages for them are incorrect ('1 hosts' instead of 
'1 host').



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20669) Enable values binding for data attribute helper

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20669:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7233 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7233/])
AMBARI-20669 Enable values binding for data attribute helper. (ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=36629d52bc5ed552f30a47bac625305db88aba57])
* (edit) ambari-web/app/utils/helper.js


> Enable values binding for data attribute helper
> ---
>
> Key: AMBARI-20669
> URL: https://issues.apache.org/jira/browse/AMBARI-20669
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20669.patch
>
>
> Binding for data attribute helper with dynamic argument should be implemented 
> (so that its output depends on changes of associated property value).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20668) Component identities is not updated in Add Service Wizard

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20668:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7232 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7232/])
AMBARI-20668 Component identities is not updated in Add Service Wizard 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dd2c2d0f0a64d8c64c74d370b4b7b0524d0f78d1])
* (edit) ambari-web/app/mixins/wizard/addSecurityConfigs.js


> Component identities is not updated in Add Service Wizard
> -
>
> Key: AMBARI-20668
> URL: https://issues.apache.org/jira/browse/AMBARI-20668
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20668.patch
>
>
> After enabling Kerberos go to Add Service Wizard and try to update some 
> component identity config, it will be ignored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20669) Enable values binding for data attribute helper

[Andrii Babiichuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Babiichuk updated AMBARI-20669:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk

> Enable values binding for data attribute helper
> ---
>
> Key: AMBARI-20669
> URL: https://issues.apache.org/jira/browse/AMBARI-20669
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20669.patch
>
>
> Binding for data attribute helper with dynamic argument should be implemented 
> (so that its output depends on changes of associated property value).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20669) Enable values binding for data attribute helper

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20669:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12861900/AMBARI-20669.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler 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/11294//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11294//console

This message is automatically generated.

> Enable values binding for data attribute helper
> ---
>
> Key: AMBARI-20669
> URL: https://issues.apache.org/jira/browse/AMBARI-20669
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20669.patch
>
>
> Binding for data attribute helper with dynamic argument should be implemented 
> (so that its output depends on changes of associated property value).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20668) Component identities is not updated in Add Service Wizard

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-20668:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Component identities is not updated in Add Service Wizard
> -
>
> Key: AMBARI-20668
> URL: https://issues.apache.org/jira/browse/AMBARI-20668
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20668.patch
>
>
> After enabling Kerberos go to Add Service Wizard and try to update some 
> component identity config, it will be ignored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20668) Component identities is not updated in Add Service Wizard

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko commented on AMBARI-20668:
--

committed to trunk

> Component identities is not updated in Add Service Wizard
> -
>
> Key: AMBARI-20668
> URL: https://issues.apache.org/jira/browse/AMBARI-20668
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20668.patch
>
>
> After enabling Kerberos go to Add Service Wizard and try to update some 
> component identity config, it will be ignored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20669) Enable values binding for data attribute helper

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander commented on AMBARI-20669:
--

+1 for the patch

> Enable values binding for data attribute helper
> ---
>
> Key: AMBARI-20669
> URL: https://issues.apache.org/jira/browse/AMBARI-20669
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20669.patch
>
>
> Binding for data attribute helper with dynamic argument should be implemented 
> (so that its output depends on changes of associated property value).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20669) Enable values binding for data attribute helper

[Andrii Babiichuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Babiichuk updated AMBARI-20669:
--
Status: Patch Available  (was: Open)

> Enable values binding for data attribute helper
> ---
>
> Key: AMBARI-20669
> URL: https://issues.apache.org/jira/browse/AMBARI-20669
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20669.patch
>
>
> Binding for data attribute helper with dynamic argument should be implemented 
> (so that its output depends on changes of associated property value).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20669) Enable values binding for data attribute helper

[Andrii Babiichuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Babiichuk updated AMBARI-20669:
--
Attachment: AMBARI-20669.patch

> Enable values binding for data attribute helper
> ---
>
> Key: AMBARI-20669
> URL: https://issues.apache.org/jira/browse/AMBARI-20669
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20669.patch
>
>
> Binding for data attribute helper with dynamic argument should be implemented 
> (so that its output depends on changes of associated property value).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20670) Node manager start extremely slow when YARN NM local dirs are very large

[Dmytro Grinenko (JIRA)]

Dmytro Grinenko created AMBARI-20670:


 Summary: Node manager start extremely slow when YARN NM local dirs 
are very large
 Key: AMBARI-20670
 URL: https://issues.apache.org/jira/browse/AMBARI-20670
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.1
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Priority: Critical
 Fix For: trunk, 2.5.1


On the cluster with the YARN NM, where local dirs are 100 GB+ with lot of small 
files - NM starts slow with timeouts

Reason could be in this specific call in  yarn.py

{code}
def create_local_dir(dir_name):
  import params
  Directory(dir_name,
create_parents = True,
cd_access="a",
mode=0755,
owner=params.yarn_user,
group=params.user_group,
ignore_failures=True,
recursive_mode_flags = {'f': 'a+rw', 'd': 'a+rwx'},
  )
{code}

was taking ~15 minutes per mount.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20668) Component identities is not updated in Add Service Wizard

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-20668:
---

+1 for the patch

> Component identities is not updated in Add Service Wizard
> -
>
> Key: AMBARI-20668
> URL: https://issues.apache.org/jira/browse/AMBARI-20668
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20668.patch
>
>
> After enabling Kerberos go to Add Service Wizard and try to update some 
> component identity config, it will be ignored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20629) Take Ambari Cluster Name as a property in Ranger plugin configs

[Mugdha Varadkar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mugdha Varadkar updated AMBARI-20629:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.5: 0a6dee67283a354e127a38b6d2cc5e1561fcd54b and trunk: 
d711d7a1f90074ab65431e6f58c6551e224df43b

> Take Ambari Cluster Name as a property in Ranger plugin configs
> ---
>
> Key: AMBARI-20629
> URL: https://issues.apache.org/jira/browse/AMBARI-20629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.1
>
> Attachments: AMBARI-20629.1.patch, AMBARI-20629.patch, 
> AMBARI-20629-trunk.1.patch, AMBARI-20629-trunk.patch
>
>
> In order to support cloud scenarios as well as Tagsync to capture Ambari 
> cluster name. Need to add a new property that is required by plugins as well 
> as tagsync for picking up Ambari cluster name. 
> For Plugins:  {code} ranger.plugin..ambari.cluster.name{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20669) Enable values binding for data attribute helper

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-20669:
-

 Summary: Enable values binding for data attribute helper
 Key: AMBARI-20669
 URL: https://issues.apache.org/jira/browse/AMBARI-20669
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
 Fix For: 3.0.0


Binding for data attribute helper with dynamic argument should be implemented 
(so that its output depends on changes of associated property value).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20668) Component identities is not updated in Add Service Wizard

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20668:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12861881/AMBARI-20668.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler 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/11293//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11293//console

This message is automatically generated.

> Component identities is not updated in Add Service Wizard
> -
>
> Key: AMBARI-20668
> URL: https://issues.apache.org/jira/browse/AMBARI-20668
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20668.patch
>
>
> After enabling Kerberos go to Add Service Wizard and try to update some 
> component identity config, it will be ignored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20629) Take Ambari Cluster Name as a property in Ranger plugin configs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20629:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1353 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1353/])
AMBARI-20629 Take Ambari Cluster Name as a property in Ranger plugin (mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0a6dee67283a354e127a38b6d2cc5e1561fcd54b])
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HBASE/configuration/ranger-hbase-audit.xml
* (edit) 
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/params.py
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/ranger-hive-audit.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/ranger-atlas-audit.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/KNOX/configuration/ranger-knox-audit.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER_KMS/configuration/ranger-kms-audit.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/KAFKA/configuration/ranger-kafka-audit.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration/ranger-yarn-audit.xml
* (edit) 
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/configuration/ranger-hdfs-audit.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/STORM/configuration/ranger-storm-audit.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml


> Take Ambari Cluster Name as a property in Ranger plugin configs
> ---
>
> Key: AMBARI-20629
> URL: https://issues.apache.org/jira/browse/AMBARI-20629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.1
>
> Attachments: AMBARI-20629.1.patch, AMBARI-20629.patch, 
> AMBARI-20629-trunk.1.patch, AMBARI-20629-trunk.patch
>
>
> In order to support cloud scenarios as well as Tagsync to capture Ambari 
> cluster name. Need to add a new property that is required by plugins as well 
> as tagsync for picking up Ambari cluster name. 
> For Plugins:  {code} ranger.plugin..ambari.cluster.name{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20629) Take Ambari Cluster Name as a property in Ranger plugin configs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20629:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7231 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7231/])
AMBARI-20629 Take Ambari Cluster Name as a property in Ranger plugin (mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d711d7a1f90074ab65431e6f58c6551e224df43b])
* (edit) 
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/params.py
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/ranger-atlas-audit.xml
* (edit) 
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/STORM/configuration/ranger-storm-audit.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/YARN/configuration/ranger-yarn-audit.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/KAFKA/configuration/ranger-kafka-audit.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/configuration/ranger-hdfs-audit.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration/ranger-yarn-audit.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/configuration/ranger-hdfs-audit.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HIVE/configuration/ranger-hive-audit.xml
* (edit) 
ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/configuration/ranger-hive-audit.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/KNOX/configuration/ranger-knox-audit.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HBASE/configuration/ranger-hbase-audit.xml
* (add) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/RANGER_KMS/configuration/ranger-kms-audit.xml


> Take Ambari Cluster Name as a property in Ranger plugin configs
> ---
>
> Key: AMBARI-20629
> URL: https://issues.apache.org/jira/browse/AMBARI-20629
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
> Fix For: 2.5.1
>
> Attachments: AMBARI-20629.1.patch, AMBARI-20629.patch, 
> AMBARI-20629-trunk.1.patch, AMBARI-20629-trunk.patch
>
>
> In order to support cloud scenarios as well as Tagsync to capture Ambari 
> cluster name. Need to add a new property that is required by plugins as well 
> as tagsync for picking up Ambari cluster name. 
> For Plugins:  {code} ranger.plugin..ambari.cluster.name{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20413) The Zoom feature in WFM, hides the WF completely either with Maximum and Min

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20413:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1352 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1352/])
AMBARI-20413.The Zoom feature in WFM, hides the WF completely either 
(padmapriyanitt: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ddec834f443ca35f3abff718de1eff73bb23d350])
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/domain/cytoscape-flow-renderer.js


> The Zoom feature in WFM, hides the WF completely either with Maximum and Min
> 
>
> Key: AMBARI-20413
> URL: https://issues.apache.org/jira/browse/AMBARI-20413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: 2.5.1
>
> Attachments: AMBARI-20413_trunk.patch
>
>
> Steps to repro:
> Create a WF and add a action
> Now use the Zoom feature and Maximize it completely and return to normal. You 
> will not be able to see the WF information.
> The same is applied for complete Minimize as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20668) Component identities is not updated in Add Service Wizard

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20668:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12861881/AMBARI-20668.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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler 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/11292//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11292//console

This message is automatically generated.

> Component identities is not updated in Add Service Wizard
> -
>
> Key: AMBARI-20668
> URL: https://issues.apache.org/jira/browse/AMBARI-20668
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20668.patch
>
>
> After enabling Kerberos go to Add Service Wizard and try to update some 
> component identity config, it will be ignored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20413) The Zoom feature in WFM, hides the WF completely either with Maximum and Min

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20413:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7230 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7230/])
AMBARI-20413.The Zoom feature in WFM, hides the WF completely either 
(padmapriyanitt: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e0e8a041be2fa8896ba429ad481be3935efe1e1e])
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/domain/cytoscape-flow-renderer.js


> The Zoom feature in WFM, hides the WF completely either with Maximum and Min
> 
>
> Key: AMBARI-20413
> URL: https://issues.apache.org/jira/browse/AMBARI-20413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: 2.5.1
>
> Attachments: AMBARI-20413_trunk.patch
>
>
> Steps to repro:
> Create a WF and add a action
> Now use the Zoom feature and Maximize it completely and return to normal. You 
> will not be able to see the WF information.
> The same is applied for complete Minimize as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20668) Component identities is not updated in Add Service Wizard

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-20668:
-
Status: Patch Available  (was: Open)

> Component identities is not updated in Add Service Wizard
> -
>
> Key: AMBARI-20668
> URL: https://issues.apache.org/jira/browse/AMBARI-20668
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20668.patch
>
>
> After enabling Kerberos go to Add Service Wizard and try to update some 
> component identity config, it will be ignored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20668) Component identities is not updated in Add Service Wizard

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-20668:
-
Attachment: AMBARI-20668.patch

> Component identities is not updated in Add Service Wizard
> -
>
> Key: AMBARI-20668
> URL: https://issues.apache.org/jira/browse/AMBARI-20668
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-20668.patch
>
>
> After enabling Kerberos go to Add Service Wizard and try to update some 
> component identity config, it will be ignored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20662) Need to auto populate the workflow parameters if its already defined in the global space

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20662:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7229 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7229/])
AMBARI-20662.Need to auto populate the workflow parameters if its 
(padmapriyanitt: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4004ee89c989241ac5c6d439f02a06ee0dd61f03])
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/job-config.js


> Need to auto populate the workflow parameters if its already defined in the 
> global space
> 
>
> Key: AMBARI-20662
> URL: https://issues.apache.org/jira/browse/AMBARI-20662
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: 2.5.1
>
> Attachments: AMBARI-20662_trunk.patch
>
>
> Need to auto populate the workflow parameters if its already defined in the 
> global space.
> ie If user has already specified workflow parameters in the global space then 
> while submitting the 
> workflow, these parameters should be auto populated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20662) Need to auto populate the workflow parameters if its already defined in the global space

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20662:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1351 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1351/])
AMBARI-20662.Need to auto populate the workflow parameters if its 
(padmapriyanitt: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=109ed393fcb52d0887213a054bc18dbae3a70d4e])
* (edit) 
contrib/views/wfmanager/src/main/resources/ui/app/components/job-config.js


> Need to auto populate the workflow parameters if its already defined in the 
> global space
> 
>
> Key: AMBARI-20662
> URL: https://issues.apache.org/jira/browse/AMBARI-20662
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: 2.5.1
>
> Attachments: AMBARI-20662_trunk.patch
>
>
> Need to auto populate the workflow parameters if its already defined in the 
> global space.
> ie If user has already specified workflow parameters in the global space then 
> while submitting the 
> workflow, these parameters should be auto populated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (AMBARI-20668) Component identities is not updated in Add Service Wizard

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-20668:


 Summary: Component identities is not updated in Add Service Wizard
 Key: AMBARI-20668
 URL: https://issues.apache.org/jira/browse/AMBARI-20668
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 3.0.0


After enabling Kerberos go to Add Service Wizard and try to update some 
component identity config, it will be ignored.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20413) The Zoom feature in WFM, hides the WF completely either with Maximum and Min

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-20413:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12861873/AMBARI-20413_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:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 core tests{color}.  The test build failed in 
contrib/views/wfmanager/src/main/resources/ui 

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

This message is automatically generated.

> The Zoom feature in WFM, hides the WF completely either with Maximum and Min
> 
>
> Key: AMBARI-20413
> URL: https://issues.apache.org/jira/browse/AMBARI-20413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: 2.5.1
>
> Attachments: AMBARI-20413_trunk.patch
>
>
> Steps to repro:
> Create a WF and add a action
> Now use the Zoom feature and Maximize it completely and return to normal. You 
> will not be able to see the WF information.
> The same is applied for complete Minimize as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20413) The Zoom feature in WFM, hides the WF completely either with Maximum and Min

[Padma Priya Nagaraj (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Padma Priya Nagaraj updated AMBARI-20413:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk, branch-2.5

> The Zoom feature in WFM, hides the WF completely either with Maximum and Min
> 
>
> Key: AMBARI-20413
> URL: https://issues.apache.org/jira/browse/AMBARI-20413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: 2.5.1
>
> Attachments: AMBARI-20413_trunk.patch
>
>
> Steps to repro:
> Create a WF and add a action
> Now use the Zoom feature and Maximize it completely and return to normal. You 
> will not be able to see the WF information.
> The same is applied for complete Minimize as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20662) Need to auto populate the workflow parameters if its already defined in the global space

[Padma Priya Nagaraj (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Padma Priya Nagaraj updated AMBARI-20662:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk, branch-2.5

> Need to auto populate the workflow parameters if its already defined in the 
> global space
> 
>
> Key: AMBARI-20662
> URL: https://issues.apache.org/jira/browse/AMBARI-20662
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: 2.5.1
>
> Attachments: AMBARI-20662_trunk.patch
>
>
> Need to auto populate the workflow parameters if its already defined in the 
> global space.
> ie If user has already specified workflow parameters in the global space then 
> while submitting the 
> workflow, these parameters should be auto populated.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20659) Notification widgets position have been fixed and size have been reduced

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20659:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1350 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1350/])
AMBARI-20659.Notification widgets position have been fixed and size have 
(padmapriyanitt: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8c9b33e08fe50c19f3b0f5c5805f0075400f572f])
* (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/components/alert-message.hbs


> Notification widgets position have been fixed and size have been reduced
> 
>
> Key: AMBARI-20659
> URL: https://issues.apache.org/jira/browse/AMBARI-20659
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.5.1
>
> Attachments: AMBARI-20659-trunk.patch
>
>
> Notification will not be visible when we are the bottom of page



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20659) Notification widgets position have been fixed and size have been reduced

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20659:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7228 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7228/])
AMBARI-20659.Notification widgets position have been fixed and size have 
(padmapriyanitt: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=92e5b590c99daf71996f95e2a8c45a76fd20df82])
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/components/alert-message.hbs
* (edit) contrib/views/hive20/src/main/resources/ui/app/styles/app.scss


> Notification widgets position have been fixed and size have been reduced
> 
>
> Key: AMBARI-20659
> URL: https://issues.apache.org/jira/browse/AMBARI-20659
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.5.1
>
> Attachments: AMBARI-20659-trunk.patch
>
>
> Notification will not be visible when we are the bottom of page



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20413) The Zoom feature in WFM, hides the WF completely either with Maximum and Min

[M Madhan Mohan Reddy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

M Madhan Mohan Reddy updated AMBARI-20413:
--
Attachment: AMBARI-20413_trunk.patch

> The Zoom feature in WFM, hides the WF completely either with Maximum and Min
> 
>
> Key: AMBARI-20413
> URL: https://issues.apache.org/jira/browse/AMBARI-20413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: 2.5.1
>
> Attachments: AMBARI-20413_trunk.patch
>
>
> Steps to repro:
> Create a WF and add a action
> Now use the Zoom feature and Maximize it completely and return to normal. You 
> will not be able to see the WF information.
> The same is applied for complete Minimize as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20413) The Zoom feature in WFM, hides the WF completely either with Maximum and Min

[M Madhan Mohan Reddy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

M Madhan Mohan Reddy updated AMBARI-20413:
--
Status: Patch Available  (was: In Progress)

> The Zoom feature in WFM, hides the WF completely either with Maximum and Min
> 
>
> Key: AMBARI-20413
> URL: https://issues.apache.org/jira/browse/AMBARI-20413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: 2.5.1
>
> Attachments: AMBARI-20413_trunk.patch
>
>
> Steps to repro:
> Create a WF and add a action
> Now use the Zoom feature and Maximize it completely and return to normal. You 
> will not be able to see the WF information.
> The same is applied for complete Minimize as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20413) The Zoom feature in WFM, hides the WF completely either with Maximum and Min

[M Madhan Mohan Reddy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

M Madhan Mohan Reddy updated AMBARI-20413:
--
Affects Version/s: (was: 2.5.0)
   2.5.1
Fix Version/s: (was: trunk)
   2.5.1

> The Zoom feature in WFM, hides the WF completely either with Maximum and Min
> 
>
> Key: AMBARI-20413
> URL: https://issues.apache.org/jira/browse/AMBARI-20413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: 2.5.1
>
>
> Steps to repro:
> Create a WF and add a action
> Now use the Zoom feature and Maximize it completely and return to normal. You 
> will not be able to see the WF information.
> The same is applied for complete Minimize as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20413) The Zoom feature in WFM, hides the WF completely either with Maximum and Min

[M Madhan Mohan Reddy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

M Madhan Mohan Reddy updated AMBARI-20413:
--
Attachment: (was: AMBARI-20413_trunk.patch)

> The Zoom feature in WFM, hides the WF completely either with Maximum and Min
> 
>
> Key: AMBARI-20413
> URL: https://issues.apache.org/jira/browse/AMBARI-20413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: M Madhan Mohan Reddy
>Assignee: M Madhan Mohan Reddy
>  Labels: WFD, WFM
> Fix For: trunk
>
>
> Steps to repro:
> Create a WF and add a action
> Now use the Zoom feature and Maximize it completely and return to normal. You 
> will not be able to see the WF information.
> The same is applied for complete Minimize as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20549) upgrade frontend-maven-plugin to latest >= 1.3 to make use of ignore proxy feature

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20549:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1349 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1349/])
AMBARI-20549. upgrade frontend-maven-plugin to latest >= 1.3 to make use 
(pallavkul: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dd74821c58fb8d92b74c7fcf59c002fcce9a4bcf])
* (edit) contrib/views/pig/pom.xml
* (edit) 
contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/package.json
* (edit) contrib/views/hawq/pom.xml
* (edit) contrib/views/jobs/pom.xml
* (edit) contrib/views/capacity-scheduler/pom.xml
* (edit) contrib/views/hive20/pom.xml
* (edit) contrib/views/hive20/src/main/resources/ui/package.json
* (edit) contrib/views/hueambarimigration/pom.xml
* (edit) contrib/views/wfmanager/pom.xml
* (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/package.json
* (edit) contrib/views/wfmanager/src/main/resources/ui/pom.xml
* (edit) contrib/views/hive-next/pom.xml
* (edit) contrib/views/files/src/main/resources/ui/package.json
* (edit) contrib/views/files/pom.xml


> upgrade frontend-maven-plugin to latest >= 1.3 to make use of ignore proxy 
> feature
> --
>
> Key: AMBARI-20549
> URL: https://issues.apache.org/jira/browse/AMBARI-20549
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-admin, ambari-views, ambari-web
>Affects Versions: 2.5.1
>Reporter: Jaimin Jetly
>Assignee: venkat
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20549.patch, AMBARI-20549-trunk.01.patch, 
> AMBARI-20549-trunk.patch
>
>
> frontend-maven-plugin inherits maven settings.xml proxy values, in latest 
> version >=1.3 proxy settings can be ignore by setting 
> 'npmInheritsProxyConfigFromMaven' to 'false'
> REF: https://github.com/eirslett/frontend-maven-plugin/pull/387
> The following files contain the plugin
> {noformat}
> ambari-admin/pom.xml
> ambari-web/pom.xml
> contrib/views/capacity-scheduler/pom.xml
> contrib/views/files/pom.xml
> contrib/views/hawq/pom.xml
> contrib/views/hive-next/pom.xml
> contrib/views/hive20/pom.xml
> contrib/views/hueambarimigration/pom.xml
> contrib/views/jobs/pom.xml
> contrib/views/pig/pom.xml
> contrib/views/wfmanager/pom.xml
> contrib/views/wfmanager/src/main/resources/ui/pom.xml
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (AMBARI-20659) Notification widgets position have been fixed and size have been reduced

[Padma Priya Nagaraj (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-20659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Padma Priya Nagaraj updated AMBARI-20659:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk, branch-2.5

> Notification widgets position have been fixed and size have been reduced
> 
>
> Key: AMBARI-20659
> URL: https://issues.apache.org/jira/browse/AMBARI-20659
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.1
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.5.1
>
> Attachments: AMBARI-20659-trunk.patch
>
>
> Notification will not be visible when we are the bottom of page



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20664) Remove hardcoding of /usr/hdp by AMBARI-20543 needed for IBM Power

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20664:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7227 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7227/])
AMBARI-20664. Remove hardcoding of /usr/hdp by AMBARI-20543 needed for 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=19848685efdac9731c820b0c7902725e5eafa829])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/configuration/tez-site.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-site.xml
* (edit) 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/params_linux.py


> Remove hardcoding of /usr/hdp by AMBARI-20543 needed for IBM Power
> --
>
> Key: AMBARI-20664
> URL: https://issues.apache.org/jira/browse/AMBARI-20664
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.1
>
> Attachments: AMBARI-20664.patch
>
>
>  hardcoded /usr/hdp inside
> common-services for several services. It should instead use `stack_root`,
> which was one of the comments during the code review.
> An Ambari Upgrade from 2.5.0 to 2.5.1 should fix those properties via the
> Upgrade Catalog.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20543) lzo.GPLNativeCodeLoader: Could not load native gpl library

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20543:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7227 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/7227/])
AMBARI-20664. Remove hardcoding of /usr/hdp by AMBARI-20543 needed for 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=19848685efdac9731c820b0c7902725e5eafa829])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/configuration/tez-site.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-site.xml
* (edit) 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/params_linux.py


> lzo.GPLNativeCodeLoader: Could not load native gpl library
> --
>
> Key: AMBARI-20543
> URL: https://issues.apache.org/jira/browse/AMBARI-20543
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.1
>
> Attachments: AMBARI-20543.patch, patchAMBARI-20543-II.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20664) Remove hardcoding of /usr/hdp by AMBARI-20543 needed for IBM Power

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20664:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1348 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1348/])
AMBARI-20664. Remove hardcoding of /usr/hdp by AMBARI-20543 needed for 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d7646eb2fc1948a7482aad656fc3176940b134f6])
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/configuration/tez-site.xml
* (edit) 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hadoop-env.xml


> Remove hardcoding of /usr/hdp by AMBARI-20543 needed for IBM Power
> --
>
> Key: AMBARI-20664
> URL: https://issues.apache.org/jira/browse/AMBARI-20664
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.1
>
> Attachments: AMBARI-20664.patch
>
>
>  hardcoded /usr/hdp inside
> common-services for several services. It should instead use `stack_root`,
> which was one of the comments during the code review.
> An Ambari Upgrade from 2.5.0 to 2.5.1 should fix those properties via the
> Upgrade Catalog.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20543) lzo.GPLNativeCodeLoader: Could not load native gpl library

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20543:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1348 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1348/])
AMBARI-20664. Remove hardcoding of /usr/hdp by AMBARI-20543 needed for 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d7646eb2fc1948a7482aad656fc3176940b134f6])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.6/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-site.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/configuration/tez-site.xml
* (edit) 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/services/HDFS/configuration/hadoop-env.xml
* (edit) 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hadoop-env.xml


> lzo.GPLNativeCodeLoader: Could not load native gpl library
> --
>
> Key: AMBARI-20543
> URL: https://issues.apache.org/jira/browse/AMBARI-20543
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.1
>
> Attachments: AMBARI-20543.patch, patchAMBARI-20543-II.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20584) Pig view doesn't load in older version of firefox

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20584:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1347 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1347/])
AMBARI-20584. Pig view doesn't load in older version of firefox (Venkata 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9dd5dcd7f03f29fbf83528a8dbabef1cebf8f811])
* (edit) contrib/views/pig/src/main/resources/ui/pig-web/app/routes/splash.js
* (edit) 
contrib/views/pig/src/main/resources/ui/pig-web/app/controllers/splash.js


> Pig view doesn't load in older version of firefox
> -
>
> Key: AMBARI-20584
> URL: https://issues.apache.org/jira/browse/AMBARI-20584
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: venkat
>Assignee: venkat
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-20584-trunk.patch
>
>
> Pig view doesn't load in older version of firefox as the code contains ES6 
> syntax specifications which are not supported in older versions of browsers.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20598) hive view 2.0 handling partition table statistics support added in hive server 2.1

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20598:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1347 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1347/])
AMBARI-20598 : added support for stats of partitioned table for hive 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4dbae3d55b8e1459c64eb700d2d6f2f016401e1e])
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/ConnectionDelegate.java
* (add) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/parsers/DatabaseMetadataExtractor.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/dto/TableStats.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/DDLProxy.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/StatementExecutor.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/JdbcConnector.java
* (add) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/client/DatabaseMetadataWrapper.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/message/ResultInformation.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/dto/ColumnStats.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/message/job/Result.java
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/services/stats-service.js
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/HiveJdbcConnectionDelegate.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/client/DDLDelegatorImpl.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/parsers/TableMetaParserImpl.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/client/DDLDelegator.java
* (add) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/message/GetDatabaseMetadataJob.java
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/components/table-statistics.js
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/components/table-statistics.hbs
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/internal/parsers/TableMetaParser.java


> hive view 2.0 handling partition table statistics support added in hive 
> server 2.1
> --
>
> Key: AMBARI-20598
> URL: https://issues.apache.org/jira/browse/AMBARI-20598
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Nitiraj Singh Rathore
>Assignee: Nitiraj Singh Rathore
> Fix For: 2.5.0
>
> Attachments: AMBARI-20598_branch-2.5_2.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20587) Hive2: Enable LDAP support for Hive2.0

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20587:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1347 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1347/])
AMBARI-20587. Hive2: Enable LDAP support for Hive2.0. (dipayanb) 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=934a5bcc7fd571c20493e4ba052ae571019b1305])
* (add) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/message/job/AuthenticationFailed.java
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/client/DDLDelegatorImpl.java
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/controllers/application.js
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/jobs/JobService.java
* (add) contrib/views/hive20/src/main/resources/ui/app/services/ldap-auth.js
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/application.hbs
* (edit) contrib/views/hive20/src/main/resources/ui/app/router.js
* (add) contrib/views/hive20/src/main/resources/ui/app/templates/password.hbs
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/resources/browser/ConnectionService.java
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/templates/components/top-application-bar.hbs
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/components/top-application-bar.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/routes/application.js
* (add) contrib/views/hive20/src/main/resources/ui/app/controllers/password.js
* (add) contrib/views/hive20/src/main/resources/ui/app/routes/password.js
* (edit) 
contrib/views/hive20/src/main/resources/ui/app/controllers/service-check.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/routes/service-check.js
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/JdbcConnector.java
* (add) contrib/views/hive20/src/main/resources/ui/app/adapters/auth.js
* (edit) contrib/views/hive20/src/main/resources/ui/app/adapters/application.js
* (edit) 
contrib/views/hive20/src/main/java/org/apache/ambari/view/hive20/actor/message/job/Failure.java


> Hive2: Enable LDAP support for Hive2.0
> --
>
> Key: AMBARI-20587
> URL: https://issues.apache.org/jira/browse/AMBARI-20587
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Critical
> Fix For: 2.5.1
>
> Attachments: AMBARI-20587.2.branch-2.5.patch, 
> AMBARI-20587.branch-2.5.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AMBARI-20585) Hive view(1.5) doesn't load in older version of firefox

[Hudson (JIRA)]

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

Hudson commented on AMBARI-20585:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1347 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1347/])
AMBARI-20585. Hive view(1.5) doesn't load in older version of firefox 
(nitiraj.rathore: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d2c5ab66343c6f38b1c86f4133c0c4688fd4d39b])
* (edit) 
contrib/views/hive-next/src/main/resources/ui/hive-web/app/routes/splash.js
* (edit) 
contrib/views/hive-next/src/main/resources/ui/hive-web/app/controllers/splash.js


> Hive view(1.5) doesn't load in older version of firefox
> ---
>
> Key: AMBARI-20585
> URL: https://issues.apache.org/jira/browse/AMBARI-20585
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.5.0
>
> Attachments: AMBARI-20585-trunk.patch
>
>
> hive view(1.5) view doesn't load in older version of firefox as the code 
> contains ES6 syntax specifications which are not supported in older versions 
> of browsers.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)