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

Hadoop QA commented on AMBARI-19007:
------------------------------------

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

This message is automatically generated.

> Atlas to support configuration of hooks from separate cluster
> -------------------------------------------------------------
>
>                 Key: AMBARI-19007
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19007
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-server
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>            Priority: Blocker
>             Fix For: 3.0.0, 2.5.0
>
>         Attachments: AMBARI-19007-trunk.01.patch, AMBARI-19007-trunk.patch, 
> AMBARI-19007.01.patch, AMBARI-19007.patch
>
>
> *Need support in ambari to allow atlas to communicate with hooks installed on 
> separate clusters*
> # Ambari Stack definition changes (for all four hooks being installed on 
> Separate Cluster) - this information will be stored in blueprints.
> # Need to be able to sync with Atlas to leverage tag based security via 
> tagsync service
> # Ambari driven configuration and addition of flags to support the feature.



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

Reply via email to