[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[ https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721287#comment-15721287 ] Hudson commented on AMBARI-19007: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #452 (See [https://builds.apache.org/job/Ambari-branch-2.5/452/]) AMBARI-19007 Atlas to support configuration of hooks from separate (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d2d7b07744855de692c231ca6b0b7f1fdd25d00c]) * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/configuration/sqoop-env.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java * (edit) ambari-common/src/main/python/resource_management/libraries/functions/setup_atlas_hook.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/hive-site.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/storm.py * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.10.0/configuration/storm-env.xml * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/sqoop.py * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hcat.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/STORM/configuration/storm-site.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat.py * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/configuration/falcon-env.xml * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/configuration/sqoop-site.xml > 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-rebase.02.patch, > AMBARI-19007-trunk.01.patch, AMBARI-19007-trunk.02.patch, > AMBARI-19007-trunk.patch, AMBARI-19007.01.patch, AMBARI-19007.02.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)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[ https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721284#comment-15721284 ] Hudson commented on AMBARI-19007: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6153 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6153/]) AMBARI-19007 Atlas to support configuration of hooks from separate (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8ad494e97302d5da69224c7ce9e493d5f20797c1]) * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/sqoop.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/STORM/configuration/storm-site.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/configuration/falcon-env.xml * (edit) ambari-common/src/main/python/resource_management/libraries/functions/setup_atlas_hook.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.10.0/configuration/storm-env.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/configuration/sqoop-env.xml * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hcat.py * (edit) ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/configuration/sqoop-site.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/webhcat.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/hive-site.xml * (edit) ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/params_linux.py * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/storm.py > 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-rebase.02.patch, > AMBARI-19007-trunk.01.patch, AMBARI-19007-trunk.02.patch, > AMBARI-19007-trunk.patch, AMBARI-19007.01.patch, AMBARI-19007.02.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)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[ https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721223#comment-15721223 ] Mugdha Varadkar commented on AMBARI-19007: -- committed to trunk: https://github.com/apache/ambari/commit/8ad494e97302d5da69224c7ce9e493d5f20797c1 branch-2.5: https://github.com/apache/ambari/commit/d2d7b07744855de692c231ca6b0b7f1fdd25d00c > 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-rebase.02.patch, > AMBARI-19007-trunk.01.patch, AMBARI-19007-trunk.02.patch, > AMBARI-19007-trunk.patch, AMBARI-19007.01.patch, AMBARI-19007.02.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)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715522#comment-15715522
]
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/12841476/AMBARI-19007-trunk.02.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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9505//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9505//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.02.patch, AMBARI-19007-trunk.patch, AMBARI-19007.01.patch,
> AMBARI-19007.02.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)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15709052#comment-15709052
]
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/12841037/AMBARI-19007-trunk.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 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.upgrade.UpgradeCatalog250Test
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9459//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9459//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.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)
[jira] [Commented] (AMBARI-19007) Atlas to support configuration of hooks from separate cluster
[
https://issues.apache.org/jira/browse/AMBARI-19007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706202#comment-15706202
]
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/12840898/AMBARI-19007.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/9443//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.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)
