Build failed in Jenkins: Atlas-master-IntegrationTests #797

[Apache Jenkins Server]

See 


--
[...truncated 653.13 KB...]
[INFO] Started ServerConnector@318ecbdc{HTTP/1.1,[http/1.1]}{0.0.0.0:31000}
[INFO] Started @1047660ms
[INFO] Started Jetty Server
[INFO] 
[INFO] --- maven-failsafe-plugin:2.18.1:integration-test (integration-test) @ 
falcon-bridge ---
[WARNING] useSystemClassloader setting has no effect when not forking
[INFO] Failsafe report directory: 

Running org.apache.atlas.falcon.hook.FalconHookIT
127.0.0.1 - - [18/Mar/2018:03:50:38 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clustervwLlsWioYo
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:39 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clustervwLlsWioYo
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:39 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clustervwLlsWioYo
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:40 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clustervwLlsWioYo
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:40 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clustervwLlsWioYo
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:40 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_cluster=qualifiedName=clustervwLlsWioYo
 HTTP/1.1" 404 106 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:41 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedMfXutrZW55@clusterr2VCL1sY3d
 HTTP/1.1" 404 118 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:41 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedMfXutrZW55@clusterr2VCL1sY3d
 HTTP/1.1" 404 118 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:41 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedMfXutrZW55@clusterr2VCL1sY3d
 HTTP/1.1" 404 118 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:42 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedMfXutrZW55@clusterr2VCL1sY3d
 HTTP/1.1" 200 924 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:42 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedMfXutrZW55@clusterr2VCL1sY3d
 HTTP/1.1" 200 924 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:42 +] "GET 
//localhost:31000/api/atlas/entities/b113e927-ff08-4f13-a6a4-66fedbdd0755 
HTTP/1.1" 200 924 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:42 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed_creation=qualifiedName=feedMfXutrZW55@clusterr2VCL1sY3d
 HTTP/1.1" 200 1267 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:42 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed_creation=qualifiedName=feedMfXutrZW55@clusterr2VCL1sY3d
 HTTP/1.1" 200 1267 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:42 +] "GET 
//localhost:31000/api/atlas/entities/3422af80-5bed-4fbc-af24-09d25482cc59 
HTTP/1.1" 200 1267 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:42 +] "GET 
//localhost:31000/api/atlas/entities/e26629f2-2150-4242-a1aa-413b7d264244 
HTTP/1.1" 200 1019 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:42 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedlhn0NoHnRL@clusterr2VCL1sY3d
 HTTP/1.1" 404 118 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:43 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedlhn0NoHnRL@clusterr2VCL1sY3d
 HTTP/1.1" 200 924 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:43 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed=qualifiedName=feedlhn0NoHnRL@clusterr2VCL1sY3d
 HTTP/1.1" 200 924 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:43 +] "GET 
//localhost:31000/api/atlas/entities/d22eace5-fae4-4e11-aebd-494691ca8012 
HTTP/1.1" 200 924 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:43 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed_creation=qualifiedName=feedlhn0NoHnRL@clusterr2VCL1sY3d
 HTTP/1.1" 200 1268 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:43 +] "GET 
//localhost:31000/api/atlas/entities?type=falcon_feed_creation=qualifiedName=feedlhn0NoHnRL@clusterr2VCL1sY3d
 HTTP/1.1" 200 1268 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:43 +] "GET 
//localhost:31000/api/atlas/entities/5d0c1e79-78a6-4156-930c-58eacd7ab60f 
HTTP/1.1" 200 1268 "-" "Java/1.8.0_152"
127.0.0.1 - - [18/Mar/2018:03:50:43 +] "GET 
//localhost:31000/api/atlas/entities/d5742e84-999b-4815-b056-226a896136d3 

[jira] [Comment Edited] (ATLAS-2498) Soft and hard deletes, deleting a "DELETED" entity and cleanup of unused types

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403696#comment-16403696
 ] 

Madhan Neethiraj edited comment on ATLAS-2498 at 3/17/18 7:21 PM:
--

bq. Is the atlas.DeleteHandler.impl configuration key supported in this version?
Starting with Apache Atlas 0.8 release, please set the following property to 
enable hard-delete:
{noformat}
  
atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.HardDeleteHandlerV1
{noformat}
 
bq. Is it possible to delete a "DELETED" entity?
Currently attempt to delete an entity which is in 'DELETED' state is ignored. 
However, when hard-delete is configured, it makes sense to delete such 
entities. It will enable the usecase you describe above.

bq. Does Atlas version 0.8.0 support hard deletes
Yes, it does. However, this is not a recommended configuration in production 
deployments - given role of Atlas in governance domain.


was (Author: madhan.neethiraj):
bq. Is the atlas.DeleteHandler.impl configuration key supported in this version?
Starting with Apache Atlas 0.8 release, please set the following property to 
enable hard-delete:
{noformat}
  
atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.HardDeleteHandlerV1
{noformat}
 
bq. Is it possible to delete a "DELETED" entity?
Currently attempt to delete an entity which is in 'DELETED' state is ignored. 
However, when hard-delete is configured, it makes sense to delete such 
entities. It will enable the usecase you describe above. Can you please file a 
JIRA for this update?

bq. Does Atlas version 0.8.0 support hard deletes
Yes, it does. However, this is not a recommended configuration in production 
deployments - given role of Atlas in governance domain.

> Soft and hard deletes, deleting a "DELETED" entity and cleanup of unused types
> --
>
> Key: ATLAS-2498
> URL: https://issues.apache.org/jira/browse/ATLAS-2498
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>Reporter: Mark Kiami
>Priority: Major
> Fix For: 1.0.0, 0.8.3
>
>
> Hello,
> Since the documentation on this feature not clear, could you please answer or 
> confirm the following:
>  # When an entity is deleted, its status goes to "DELETED", this is a soft 
> delete.
>  # Does Atlas version 0.8.0 support hard deletes (HDP 2.6.4 ships with 0.8.0)?
>  # Is the atlas.DeleteHandler.impl configuration key supported in this 
> version?
>  # Is it possible to delete a "DELETED" entity?
> I am asking this because I am stuck in the following scenario:
>  * Create a new ENTITY type named "custom_type"
>  * Create an entity of that type "entity_1_of_custom_type", its status is 
> "ACTIVE"
>  * Delete the entity "entity_1_of_custom_type", its status is "DELETED"
>  * Delete the ENTITY type named "custom_type"
>  * I get an error: \{"errorCode":"ATLAS-409-00-002","errorMessage":"Given 
> type custom_type has references"}
> How is it possible in this case to cleanup both the DELETED entity and the 
> unused type "custom_type"?
> Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2498) Soft and hard deletes, deleting a "DELETED" entity and cleanup of unused types

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj updated ATLAS-2498:

Fix Version/s: 0.8.3
   1.0.0

> Soft and hard deletes, deleting a "DELETED" entity and cleanup of unused types
> --
>
> Key: ATLAS-2498
> URL: https://issues.apache.org/jira/browse/ATLAS-2498
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>Reporter: Mark Kiami
>Priority: Major
> Fix For: 1.0.0, 0.8.3
>
>
> Hello,
> Since the documentation on this feature not clear, could you please answer or 
> confirm the following:
>  # When an entity is deleted, its status goes to "DELETED", this is a soft 
> delete.
>  # Does Atlas version 0.8.0 support hard deletes (HDP 2.6.4 ships with 0.8.0)?
>  # Is the atlas.DeleteHandler.impl configuration key supported in this 
> version?
>  # Is it possible to delete a "DELETED" entity?
> I am asking this because I am stuck in the following scenario:
>  * Create a new ENTITY type named "custom_type"
>  * Create an entity of that type "entity_1_of_custom_type", its status is 
> "ACTIVE"
>  * Delete the entity "entity_1_of_custom_type", its status is "DELETED"
>  * Delete the ENTITY type named "custom_type"
>  * I get an error: \{"errorCode":"ATLAS-409-00-002","errorMessage":"Given 
> type custom_type has references"}
> How is it possible in this case to cleanup both the DELETED entity and the 
> unused type "custom_type"?
> Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2498) Soft and hard deletes, deleting a "DELETED" entity and cleanup of unused types

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403696#comment-16403696
 ] 

Madhan Neethiraj commented on ATLAS-2498:
-

bq. Is the atlas.DeleteHandler.impl configuration key supported in this version?
Starting with Apache Atlas 0.8 release, please set the following property to 
enable hard-delete:
{noformat}
  
atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.HardDeleteHandlerV1
{noformat}
 
bq. Is it possible to delete a "DELETED" entity?
Currently attempt to delete an entity which is in 'DELETED' state is ignored. 
However, when hard-delete is configured, it makes sense to delete such 
entities. It will enable the usecase you describe above.

bq. Does Atlas version 0.8.0 support hard deletes
Yes, it does. However, this is not a recommended configuration in production 
deployments - given role of Atlas in governance domain.

> Soft and hard deletes, deleting a "DELETED" entity and cleanup of unused types
> --
>
> Key: ATLAS-2498
> URL: https://issues.apache.org/jira/browse/ATLAS-2498
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>Reporter: Mark Kiami
>Priority: Major
>
> Hello,
> Since the documentation on this feature not clear, could you please answer or 
> confirm the following:
>  # When an entity is deleted, its status goes to "DELETED", this is a soft 
> delete.
>  # Does Atlas version 0.8.0 support hard deletes (HDP 2.6.4 ships with 0.8.0)?
>  # Is the atlas.DeleteHandler.impl configuration key supported in this 
> version?
>  # Is it possible to delete a "DELETED" entity?
> I am asking this because I am stuck in the following scenario:
>  * Create a new ENTITY type named "custom_type"
>  * Create an entity of that type "entity_1_of_custom_type", its status is 
> "ACTIVE"
>  * Delete the entity "entity_1_of_custom_type", its status is "DELETED"
>  * Delete the ENTITY type named "custom_type"
>  * I get an error: \{"errorCode":"ATLAS-409-00-002","errorMessage":"Given 
> type custom_type has references"}
> How is it possible in this case to cleanup both the DELETED entity and the 
> unused type "custom_type"?
> Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (ATLAS-2498) Soft and hard deletes, deleting a "DELETED" entity and cleanup of unused types

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403696#comment-16403696
 ] 

Madhan Neethiraj edited comment on ATLAS-2498 at 3/17/18 7:20 PM:
--

bq. Is the atlas.DeleteHandler.impl configuration key supported in this version?
Starting with Apache Atlas 0.8 release, please set the following property to 
enable hard-delete:
{noformat}
  
atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.HardDeleteHandlerV1
{noformat}
 
bq. Is it possible to delete a "DELETED" entity?
Currently attempt to delete an entity which is in 'DELETED' state is ignored. 
However, when hard-delete is configured, it makes sense to delete such 
entities. It will enable the usecase you describe above. Can you please file a 
JIRA for this update?

bq. Does Atlas version 0.8.0 support hard deletes
Yes, it does. However, this is not a recommended configuration in production 
deployments - given role of Atlas in governance domain.


was (Author: madhan.neethiraj):
bq. Is the atlas.DeleteHandler.impl configuration key supported in this version?
Starting with Apache Atlas 0.8 release, please set the following property to 
enable hard-delete:
{noformat}
  
atlas.DeleteHandlerV1.impl=org.apache.atlas.repository.store.graph.v1.HardDeleteHandlerV1
{noformat}
 
bq. Is it possible to delete a "DELETED" entity?
Currently attempt to delete an entity which is in 'DELETED' state is ignored. 
However, when hard-delete is configured, it makes sense to delete such 
entities. It will enable the usecase you describe above.

bq. Does Atlas version 0.8.0 support hard deletes
Yes, it does. However, this is not a recommended configuration in production 
deployments - given role of Atlas in governance domain.

> Soft and hard deletes, deleting a "DELETED" entity and cleanup of unused types
> --
>
> Key: ATLAS-2498
> URL: https://issues.apache.org/jira/browse/ATLAS-2498
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.8-incubating
>Reporter: Mark Kiami
>Priority: Major
>
> Hello,
> Since the documentation on this feature not clear, could you please answer or 
> confirm the following:
>  # When an entity is deleted, its status goes to "DELETED", this is a soft 
> delete.
>  # Does Atlas version 0.8.0 support hard deletes (HDP 2.6.4 ships with 0.8.0)?
>  # Is the atlas.DeleteHandler.impl configuration key supported in this 
> version?
>  # Is it possible to delete a "DELETED" entity?
> I am asking this because I am stuck in the following scenario:
>  * Create a new ENTITY type named "custom_type"
>  * Create an entity of that type "entity_1_of_custom_type", its status is 
> "ACTIVE"
>  * Delete the entity "entity_1_of_custom_type", its status is "DELETED"
>  * Delete the ENTITY type named "custom_type"
>  * I get an error: \{"errorCode":"ATLAS-409-00-002","errorMessage":"Given 
> type custom_type has references"}
> How is it possible in this case to cleanup both the DELETED entity and the 
> unused type "custom_type"?
> Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Build failed in Jenkins: Atlas-0.8-UnitTests #187

[Apache Jenkins Server]

See 


Changes:

[madhan] ATLAS-2500: added additional headers in HTTP response

--
[...truncated 244.18 KB...]
at 
com.thinkaurelius.titan.graphdb.vertices.AbstractVertex.getProperties(AbstractVertex.java:167)
at 
org.apache.atlas.repository.graphdb.titan0.Titan0Vertex.getPropertyValues(Titan0Vertex.java:107)
at 
org.apache.atlas.repository.graph.GraphHelper.getTraitNames(GraphHelper.java:610)
at 
org.apache.atlas.repository.graph.DeleteHandler.deleteAllTraits(DeleteHandler.java:475)
at 
org.apache.atlas.repository.graph.DeleteHandler.deleteEntities(DeleteHandler.java:123)
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepository.deleteEntities(GraphBackedMetadataRepository.java:485)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.atlas.TestUtils$3.invoke(TestUtils.java:686)
at com.sun.proxy.$Proxy40.deleteEntities(Unknown Source)
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryDeleteTestBase.deleteEntities(GraphBackedMetadataRepositoryDeleteTestBase.java:236)
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepositoryDeleteTestBase.testLowerBoundsIgnoredOnCompositeDeletedEntities(GraphBackedMetadataRepositoryDeleteTestBase.java:932)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:85)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:659)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:845)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1153)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
at org.testng.TestRunner.privateRun(TestRunner.java:771)
at org.testng.TestRunner.run(TestRunner.java:621)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
at org.testng.SuiteRunner.run(SuiteRunner.java:259)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1199)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1124)
at org.testng.TestNG.run(TestNG.java:1032)
at 
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:129)
at 
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:113)
at 
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)

testLowerBoundsIgnoredWhenDeletingCompositeEntitesOwnedByMap(org.apache.atlas.repository.graph.GraphBackedRepositoryHardDeleteTest)
  Time elapsed: 1.585 sec  <<< FAILURE!
org.apache.atlas.repository.RepositoryException: 
org.apache.atlas.typesystem.exception.NullRequiredAttributeException: Cannot 
unset required attribute MapValueReferencer.refToMapValue on vertex[id=26112 
type=MapValueReferencer guid=4d537092-6d70-41f8-a000-294acb79e583] edge = 
__MapValueReferencer.refToMapValue
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepository.deleteEntities(GraphBackedMetadataRepository.java:488)
at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.atlas.TestUtils$3.invoke(TestUtils.java:686)
at com.sun.proxy.$Proxy40.deleteEntities(Unknown Source)
at 

Re: Review Request 66113: ATLAS-2503 :- Fix authorization while creating/updating EnumDef

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/66113/#review199373
---


Ship it!




Ship It!

- Madhan Neethiraj


On March 16, 2018, 11:05 a.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66113/
> ---
> 
> (Updated March 16, 2018, 11:05 a.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Ashutosh Mestry, deepak sharma, Madhan 
> Neethiraj, and Sharmadha Sainath.
> 
> 
> Bugs: ATLAS-2503
> https://issues.apache.org/jira/browse/ATLAS-2503
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch includes changes to add authz verify method call to verify authz 
> allowed for that action in AtlasEnumDef and AtlasRelationShipDef store.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEnumDefStoreV1.java
>  5bd9c12e 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java
>  7163e427 
> 
> 
> Diff: https://reviews.apache.org/r/66113/diff/1/
> 
> 
> Testing
> ---
> 
> Build and Existing UT's / IT's passing.
> Tested with DATA-SCIENTIST and DATA-STEWARD role users.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>

[jira] [Resolved] (ATLAS-2488) AtlasClientV2 should support create of relationship

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj resolved ATLAS-2488.
-
Resolution: Fixed

Thanks [~jonesn]. Committed to master: 
[http://git-wip-us.apache.org/repos/asf/atlas/commit/b161859e].

> AtlasClientV2 should support create of relationship
> ---
>
> Key: ATLAS-2488
> URL: https://issues.apache.org/jira/browse/ATLAS-2488
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2488-1.patch, ATLAS-2488-2.patch
>
>
> RelationshipREST allows one to create, delete & get relationships
> However the AtlasClientV2 API only has support for get & delete, not create
> This is an omission (bug arguably?) , since the client should reflect what is 
> available via the rest API in a more java-usable form
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2500) Add additional headers to Atlas response.

[Madhan Neethiraj (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403561#comment-16403561
 ] 

Madhan Neethiraj commented on ATLAS-2500:
-

+1 for the patch. Thanks [~nixonrodrigues].

> Add additional headers to Atlas response.
> -
>
> Key: ATLAS-2500
> URL: https://issues.apache.org/jira/browse/ATLAS-2500
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2500.patch
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Jenkins build is back to normal : Atlas-master-IntegrationTests #792

[Apache Jenkins Server]

See