[jira] [Created] (ATLAS-933) Test failure: HiveHookIT.testInsertIntoTable

2016-06-21 Thread Shwetha G S (JIRA)
Shwetha G S created ATLAS-933:
-

 Summary: Test failure: HiveHookIT.testInsertIntoTable
 Key: ATLAS-933
 URL: https://issues.apache.org/jira/browse/ATLAS-933
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S
 Fix For: 0.7-incubating
 Attachments: ATLAS-933.patch

{noformat}
Tests run: 45, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 93.454 sec <<< 
FAILURE! - in org.apache.atlas.hive.hook.HiveHookIT
testInsertIntoTable(org.apache.atlas.hive.hook.HiveHookIT)  Time elapsed: 2.097 
sec  <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API GET_ENTITY failed 
with status 500(Internal Server Error) Response Body ({"error":"Could not 
execute operation due to backend 
exception","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could not 
execute operation due to backend exception\n\tat 
com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:44)\n\tat
 
com.thinkaurelius.titan.diskstorage.BackendTransaction.executeRead(BackendTransaction.java:428)\n\tat
 
com.thinkaurelius.titan.diskstorage.BackendTransaction.edgeStoreQuery(BackendTransaction.java:253)\n\tat
 
com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.edgeQuery(StandardTitanGraph.java:365)\n\tat
 
com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor$2.get(SimpleVertexQueryProcessor.java:109)\n\tat
 
com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor$2.get(SimpleVertexQueryProcessor.java:106)\n\tat
 
com.thinkaurelius.titan.graphdb.vertices.CacheVertex.loadRelations(CacheVertex.java:47)\n\tat
 
com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor.getBasicIterator(SimpleVertexQueryProcessor.java:106)\n\tat
 
com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor.iterator(SimpleVertexQueryProcessor.java:63)\n\tat
 
com.thinkaurelius.titan.graphdb.transaction.RelationConstructor$1$1.(RelationConstructor.java:36)\n\tat
 
com.thinkaurelius.titan.graphdb.transaction.RelationConstructor$1.iterator(RelationConstructor.java:34)\n\tat
 
org.apache.atlas.repository.graph.GraphHelper.getTraitNames(GraphHelper.java:325)\n\tat
 
org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapGraphToTypedInstance(GraphToTypedInstanceMapper.java:70)\n\tat
 
org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToClassReference(GraphToTypedInstanceMapper.java:176)\n\tat
 
org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToAttribute(GraphToTypedInstanceMapper.java:146)\n\tat
 
org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToInstance(GraphToTypedInstanceMapper.java:101)\n\tat
 
org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapGraphToTypedInstance(GraphToTypedInstanceMapper.java:80)\n\tat
 
org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:167)\n\tat
 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)\n\tat
 
org.apache.atlas.services.DefaultMetadataService.getEntityDefinitionReference(DefaultMetadataService.java:398)\n\tat
 
org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:403)\n\tat
 
org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:515)\n\tat
 
org.apache.atlas.web.resources.EntityResource.getEntity(EntityResource.java:497)\n\tat
 sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)\n\tat 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
 java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
 

[jira] [Updated] (ATLAS-933) Test failure: HiveHookIT.testInsertIntoTable

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-933:
--
Attachment: ATLAS-933.patch

> Test failure: HiveHookIT.testInsertIntoTable
> 
>
> Key: ATLAS-933
> URL: https://issues.apache.org/jira/browse/ATLAS-933
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-933.patch
>
>
> {noformat}
> Tests run: 45, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 93.454 sec 
> <<< FAILURE! - in org.apache.atlas.hive.hook.HiveHookIT
> testInsertIntoTable(org.apache.atlas.hive.hook.HiveHookIT)  Time elapsed: 
> 2.097 sec  <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API GET_ENTITY 
> failed with status 500(Internal Server Error) Response Body ({"error":"Could 
> not execute operation due to backend 
> exception","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could 
> not execute operation due to backend exception\n\tat 
> com.thinkaurelius.titan.diskstorage.util.BackendOperation.execute(BackendOperation.java:44)\n\tat
>  
> com.thinkaurelius.titan.diskstorage.BackendTransaction.executeRead(BackendTransaction.java:428)\n\tat
>  
> com.thinkaurelius.titan.diskstorage.BackendTransaction.edgeStoreQuery(BackendTransaction.java:253)\n\tat
>  
> com.thinkaurelius.titan.graphdb.database.StandardTitanGraph.edgeQuery(StandardTitanGraph.java:365)\n\tat
>  
> com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor$2.get(SimpleVertexQueryProcessor.java:109)\n\tat
>  
> com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor$2.get(SimpleVertexQueryProcessor.java:106)\n\tat
>  
> com.thinkaurelius.titan.graphdb.vertices.CacheVertex.loadRelations(CacheVertex.java:47)\n\tat
>  
> com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor.getBasicIterator(SimpleVertexQueryProcessor.java:106)\n\tat
>  
> com.thinkaurelius.titan.graphdb.query.vertex.SimpleVertexQueryProcessor.iterator(SimpleVertexQueryProcessor.java:63)\n\tat
>  
> com.thinkaurelius.titan.graphdb.transaction.RelationConstructor$1$1.(RelationConstructor.java:36)\n\tat
>  
> com.thinkaurelius.titan.graphdb.transaction.RelationConstructor$1.iterator(RelationConstructor.java:34)\n\tat
>  
> org.apache.atlas.repository.graph.GraphHelper.getTraitNames(GraphHelper.java:325)\n\tat
>  
> org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapGraphToTypedInstance(GraphToTypedInstanceMapper.java:70)\n\tat
>  
> org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToClassReference(GraphToTypedInstanceMapper.java:176)\n\tat
>  
> org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToAttribute(GraphToTypedInstanceMapper.java:146)\n\tat
>  
> org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapVertexToInstance(GraphToTypedInstanceMapper.java:101)\n\tat
>  
> org.apache.atlas.repository.graph.GraphToTypedInstanceMapper.mapGraphToTypedInstance(GraphToTypedInstanceMapper.java:80)\n\tat
>  
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:167)\n\tat
>  
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinitionReference(DefaultMetadataService.java:398)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:403)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.getEntityDefinitionByAttribute(EntityResource.java:515)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.getEntity(EntityResource.java:497)\n\tat
>  sun.reflect.GeneratedMethodAccessor83.invoke(Unknown Source)\n\tat 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> 

[jira] [Updated] (ATLAS-856) Lazy-load type cache provider

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-856:
--
Fix Version/s: 0.7-incubating

> Lazy-load type cache provider
> -
>
> Key: ATLAS-856
> URL: https://issues.apache.org/jira/browse/ATLAS-856
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: David Kantor
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-856.patch, rb48565.patch
>
>
> A modified version of the default local cache provider which will run a 
> lookup on the backend storage if a requested type is not found in the cache, 
> and load it in the cache and return it if it's found. This lazy-loading cache 
> would cover the case where new types are registered, not the case where 
> existing types are modified, while avoiding the deployment/maintenance and 
> performance impact of a distributed cache in an HA environment.



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


[jira] [Updated] (ATLAS-584) Integrate CSRF prevention filter

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-584:
--
Fix Version/s: (was: 0.7-incubating)

> Integrate CSRF prevention filter
> 
>
> Key: ATLAS-584
> URL: https://issues.apache.org/jira/browse/ATLAS-584
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Kalyani Kashikar
>Priority: Blocker
>
> Atlas needs to provide protection for CSRF protection.



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


[jira] [Updated] (ATLAS-584) Integrate CSRF prevention filter

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-584:
--
Priority: Major  (was: Blocker)

> Integrate CSRF prevention filter
> 
>
> Key: ATLAS-584
> URL: https://issues.apache.org/jira/browse/ATLAS-584
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Kalyani Kashikar
>
> Atlas needs to provide protection for CSRF protection.



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


Re: Review Request 48565: ATLAS-856: lazy-load type cache

2016-06-21 Thread Shwetha GS

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


Ship it!




Ship It!

- Shwetha GS


On June 22, 2016, 2:28 a.m., David Kantor wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48565/
> ---
> 
> (Updated June 22, 2016, 2:28 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-856
> https://issues.apache.org/jira/browse/ATLAS-856
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-856: Implemented StoreBackedTypeCache, an extension of DefaultTypeCache 
> which loads the requested type from the type store if it is not found in the 
> cache, and adds it to the cache if it's found in the store.  Any attribute 
> and super types that are required by the requested type are also loaded from 
> the store if they are not already in the cache.
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/ApplicationProperties.java 
> 741e1a6ad5e10315a9a565d69f9838c438c2e18e 
>   repository/src/main/java/org/apache/atlas/RepositoryMetadataModule.java 
> c4c767827014a265471250306f35316a0b4ed67f 
>   
> repository/src/main/java/org/apache/atlas/repository/typestore/GraphBackedTypeStore.java
>  5ed9e02eb85ec25b63540cab40d148914d410786 
>   
> repository/src/main/java/org/apache/atlas/repository/typestore/ITypeStore.java
>  790c4b31c37e51289585f6f891366a8d8c86b168 
>   
> repository/src/main/java/org/apache/atlas/repository/typestore/StoreBackedTypeCache.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  37e7b66e073df294f5e38c79ba33c7ffcb394a8e 
>   
> repository/src/test/java/org/apache/atlas/repository/typestore/GraphBackedTypeStoreTest.java
>  dd530a755231c3d487d9f5104cb0aa7119863266 
>   
> repository/src/test/java/org/apache/atlas/repository/typestore/StoreBackedTypeCacheConfigurationTest.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/repository/typestore/StoreBackedTypeCacheTest.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/repository/typestore/StoreBackedTypeCacheTestModule.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/service/StoreBackedTypeCacheMetadataServiceTest.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/services/DefaultMetadataServiceMockTest.java
>  effee2a43d8c1e1369b52f1c3899cb882ea52aa1 
>   typesystem/src/main/java/org/apache/atlas/typesystem/types/TypeSystem.java 
> 14f1968c2dd6765793c1c43e3ea1ed5f3a9c8a42 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/cache/DefaultTypeCacheProvider.java
>  700bda6463e039b8f6ad2ac75840f9e637a883b0 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/cache/ITypeCacheProvider.java
>  55e9ddc463c748d3cd631d11860235dbe1a92714 
>   typesystem/src/test/java/org/apache/atlas/ApplicationPropertiesTest.java 
> 06796420361573d41ca084f4c45d7a5f17cf4ff0 
>   
> typesystem/src/test/java/org/apache/atlas/typesystem/types/cache/DefaultTypeCacheProviderTest.java
>  c426d50f52dfd99835d9fcf1c6f95841ba4b5494 
>   webapp/src/test/java/org/apache/atlas/web/listeners/TestModule.java 
> 9cb76d3d1660a0c806296c41d8108acc8925d3d0 
> 
> Diff: https://reviews.apache.org/r/48565/diff/
> 
> 
> Testing
> ---
> 
> Ran all unit and integration tests with no regressions.
> 
> 
> Thanks,
> 
> David Kantor
> 
>



[jira] [Updated] (ATLAS-856) Lazy-load type cache provider

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor updated ATLAS-856:
---
Attachment: rb48565.patch

Rebased with trunk and addressed Shwetha's comments.

> Lazy-load type cache provider
> -
>
> Key: ATLAS-856
> URL: https://issues.apache.org/jira/browse/ATLAS-856
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: David Kantor
> Attachments: ATLAS-856.patch, rb48565.patch
>
>
> A modified version of the default local cache provider which will run a 
> lookup on the backend storage if a requested type is not found in the cache, 
> and load it in the cache and return it if it's found. This lazy-loading cache 
> would cover the case where new types are registered, not the case where 
> existing types are modified, while avoiding the deployment/maintenance and 
> performance impact of a distributed cache in an HA environment.



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


[jira] [Updated] (ATLAS-856) Lazy-load type cache provider

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor updated ATLAS-856:
---
Attachment: (was: rb48565.patch)

> Lazy-load type cache provider
> -
>
> Key: ATLAS-856
> URL: https://issues.apache.org/jira/browse/ATLAS-856
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: David Kantor
> Attachments: ATLAS-856.patch
>
>
> A modified version of the default local cache provider which will run a 
> lookup on the backend storage if a requested type is not found in the cache, 
> and load it in the cache and return it if it's found. This lazy-loading cache 
> would cover the case where new types are registered, not the case where 
> existing types are modified, while avoiding the deployment/maintenance and 
> performance impact of a distributed cache in an HA environment.



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



Re: Review Request 48565: ATLAS-856: lazy-load type cache

2016-06-21 Thread David Kantor

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

(Updated June 22, 2016, 2:28 a.m.)


Review request for atlas.


Changes
---

Rebased with trunk, addressed Shwetha's comments.


Bugs: ATLAS-856
https://issues.apache.org/jira/browse/ATLAS-856


Repository: atlas


Description
---

ATLAS-856: Implemented StoreBackedTypeCache, an extension of DefaultTypeCache 
which loads the requested type from the type store if it is not found in the 
cache, and adds it to the cache if it's found in the store.  Any attribute and 
super types that are required by the requested type are also loaded from the 
store if they are not already in the cache.


Diffs (updated)
-

  common/src/main/java/org/apache/atlas/ApplicationProperties.java 
741e1a6ad5e10315a9a565d69f9838c438c2e18e 
  repository/src/main/java/org/apache/atlas/RepositoryMetadataModule.java 
c4c767827014a265471250306f35316a0b4ed67f 
  
repository/src/main/java/org/apache/atlas/repository/typestore/GraphBackedTypeStore.java
 5ed9e02eb85ec25b63540cab40d148914d410786 
  
repository/src/main/java/org/apache/atlas/repository/typestore/ITypeStore.java 
790c4b31c37e51289585f6f891366a8d8c86b168 
  
repository/src/main/java/org/apache/atlas/repository/typestore/StoreBackedTypeCache.java
 PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java 
37e7b66e073df294f5e38c79ba33c7ffcb394a8e 
  
repository/src/test/java/org/apache/atlas/repository/typestore/GraphBackedTypeStoreTest.java
 dd530a755231c3d487d9f5104cb0aa7119863266 
  
repository/src/test/java/org/apache/atlas/repository/typestore/StoreBackedTypeCacheConfigurationTest.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/repository/typestore/StoreBackedTypeCacheTest.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/repository/typestore/StoreBackedTypeCacheTestModule.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/service/StoreBackedTypeCacheMetadataServiceTest.java
 PRE-CREATION 
  
repository/src/test/java/org/apache/atlas/services/DefaultMetadataServiceMockTest.java
 effee2a43d8c1e1369b52f1c3899cb882ea52aa1 
  typesystem/src/main/java/org/apache/atlas/typesystem/types/TypeSystem.java 
14f1968c2dd6765793c1c43e3ea1ed5f3a9c8a42 
  
typesystem/src/main/java/org/apache/atlas/typesystem/types/cache/DefaultTypeCacheProvider.java
 700bda6463e039b8f6ad2ac75840f9e637a883b0 
  
typesystem/src/main/java/org/apache/atlas/typesystem/types/cache/ITypeCacheProvider.java
 55e9ddc463c748d3cd631d11860235dbe1a92714 
  typesystem/src/test/java/org/apache/atlas/ApplicationPropertiesTest.java 
06796420361573d41ca084f4c45d7a5f17cf4ff0 
  
typesystem/src/test/java/org/apache/atlas/typesystem/types/cache/DefaultTypeCacheProviderTest.java
 c426d50f52dfd99835d9fcf1c6f95841ba4b5494 
  webapp/src/test/java/org/apache/atlas/web/listeners/TestModule.java 
9cb76d3d1660a0c806296c41d8108acc8925d3d0 

Diff: https://reviews.apache.org/r/48565/diff/


Testing
---

Ran all unit and integration tests with no regressions.


Thanks,

David Kantor



Build failed in Jenkins: apache-atlas-nightly #337

2016-06-21 Thread Apache Jenkins Server
See 

Changes:

[sumasai.shivaprasad] ATLAS-931 Delete entities fails when hard delete is 
configured (dkantor

--
[...truncated 5990 lines...]
[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ atlas-webapp 
---
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:clean (clean) @ atlas-webapp ---
[WARNING] Keystore file 
'
 doesn't exist.
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 55 Java sources to 

[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 55 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 41 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

Build failed in Jenkins: apache-atlas-nightly #336

2016-06-21 Thread Apache Jenkins Server
See 

Changes:

[sumasai.shivaprasad] ATLAS-932: UI: 'create tag' button does not work - when 
there are no

[sumasai.shivaprasad] Updated release notes for ATLAS-932

--
[...truncated 5988 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ atlas-webapp 
---
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:clean (clean) @ atlas-webapp ---
[WARNING] Keystore file 
'
 doesn't exist.
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 55 Java sources to 

[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 55 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 40 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 40 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 

[jira] [Updated] (ATLAS-931) Delete entities fails when hard delete is configured

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor updated ATLAS-931:
---
Attachment: rb49047.patch

Rebased with trunk

> Delete entities fails when hard delete is configured
> 
>
> Key: ATLAS-931
> URL: https://issues.apache.org/jira/browse/ATLAS-931
> Project: Atlas
>  Issue Type: Bug
>Reporter: Prasad  S Madugundu
>Assignee: David Kantor
>Priority: Blocker
> Attachments: rb49047.patch
>
>
> When Atlas is configured for hard deletes, entity deletion fails with an 
> EntityNotFoundException when retrieving a deleted entity to include in the 
> response.  This occurs when the delete operation does not update any objects, 
> so that the list of updated guids returned by the service layer is empty and 
> EntityResource uses a deleted entity guid to retrieve the "sample" entity 
> definition to include the response.  If hard delete is enabled, the entity no 
> longer exists and the entity lookup fails.
> SEVERE: Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in 
> the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: 
> Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
>   at 
> org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
>   at 
> org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
>   at 
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
>   at 
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
>   at 
> org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
>   at 
> org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)



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


[jira] [Updated] (ATLAS-931) Delete entities fails when hard delete is configured

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor updated ATLAS-931:
---
Attachment: (was: rb49047.patch)

> Delete entities fails when hard delete is configured
> 
>
> Key: ATLAS-931
> URL: https://issues.apache.org/jira/browse/ATLAS-931
> Project: Atlas
>  Issue Type: Bug
>Reporter: Prasad  S Madugundu
>Assignee: David Kantor
>Priority: Blocker
>
> When Atlas is configured for hard deletes, entity deletion fails with an 
> EntityNotFoundException when retrieving a deleted entity to include in the 
> response.  This occurs when the delete operation does not update any objects, 
> so that the list of updated guids returned by the service layer is empty and 
> EntityResource uses a deleted entity guid to retrieve the "sample" entity 
> definition to include the response.  If hard delete is enabled, the entity no 
> longer exists and the entity lookup fails.
> SEVERE: Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in 
> the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: 
> Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
>   at 
> org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
>   at 
> org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
>   at 
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
>   at 
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
>   at 
> org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
>   at 
> org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)



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


[jira] [Commented] (ATLAS-931) Delete entities fails when hard delete is configured

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-931:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812333/rb49047.patch
  against master revision 7666ae9.

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

Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/350//console

This message is automatically generated.

> Delete entities fails when hard delete is configured
> 
>
> Key: ATLAS-931
> URL: https://issues.apache.org/jira/browse/ATLAS-931
> Project: Atlas
>  Issue Type: Bug
>Reporter: Prasad  S Madugundu
>Assignee: David Kantor
>Priority: Blocker
> Attachments: rb49047.patch
>
>
> When Atlas is configured for hard deletes, entity deletion fails with an 
> EntityNotFoundException when retrieving a deleted entity to include in the 
> response.  This occurs when the delete operation does not update any objects, 
> so that the list of updated guids returned by the service layer is empty and 
> EntityResource uses a deleted entity guid to retrieve the "sample" entity 
> definition to include the response.  If hard delete is enabled, the entity no 
> longer exists and the entity lookup fails.
> SEVERE: Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in 
> the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: 
> Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
>   at 
> org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
>   at 
> org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
>   at 
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
>   at 
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
>   at 
> org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
>   at 
> org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)



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


[jira] [Commented] (ATLAS-932) UI: 'create tag' button does not work

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-932:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812329/ATLAS-932.patch
  against master revision 7666ae9.

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

Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/349//console

This message is automatically generated.

> UI: 'create tag' button does not work
> -
>
> Key: ATLAS-932
> URL: https://issues.apache.org/jira/browse/ATLAS-932
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-932.patch
>
>
> With the latest Atlas from master, clicking on 'Create Tag' button does not 
> popup dialog to get details of new tag. Following error is seen in the Java 
> Console:
> Uncaught TypeError: Cannot read property 'get' of undefined
> CreateTagLayoutView.js:60



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


[jira] [Commented] (ATLAS-856) Lazy-load type cache provider

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-856:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812243/ATLAS-856.patch
  against master revision 7666ae9.

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

Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/348//console

This message is automatically generated.

> Lazy-load type cache provider
> -
>
> Key: ATLAS-856
> URL: https://issues.apache.org/jira/browse/ATLAS-856
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: David Kantor
> Attachments: ATLAS-856.patch, rb48565.patch
>
>
> A modified version of the default local cache provider which will run a 
> lookup on the backend storage if a requested type is not found in the cache, 
> and load it in the cache and return it if it's found. This lazy-loading cache 
> would cover the case where new types are registered, not the case where 
> existing types are modified, while avoiding the deployment/maintenance and 
> performance impact of a distributed cache in an HA environment.



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


[jira] [Updated] (ATLAS-931) Delete entities fails when hard delete is configured

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor updated ATLAS-931:
---
Attachment: (was: rb49047.patch)

> Delete entities fails when hard delete is configured
> 
>
> Key: ATLAS-931
> URL: https://issues.apache.org/jira/browse/ATLAS-931
> Project: Atlas
>  Issue Type: Bug
>Reporter: Prasad  S Madugundu
>Assignee: David Kantor
>Priority: Blocker
> Attachments: rb49047.patch
>
>
> When Atlas is configured for hard deletes, entity deletion fails with an 
> EntityNotFoundException when retrieving a deleted entity to include in the 
> response.  This occurs when the delete operation does not update any objects, 
> so that the list of updated guids returned by the service layer is empty and 
> EntityResource uses a deleted entity guid to retrieve the "sample" entity 
> definition to include the response.  If hard delete is enabled, the entity no 
> longer exists and the entity lookup fails.
> SEVERE: Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in 
> the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: 
> Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
>   at 
> org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
>   at 
> org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
>   at 
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
>   at 
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
>   at 
> org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
>   at 
> org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)



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


[jira] [Updated] (ATLAS-931) Delete entities fails when hard delete is configured

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor updated ATLAS-931:
---
Attachment: rb49047.patch

Attached latest review board patch after addressing review comment.

> Delete entities fails when hard delete is configured
> 
>
> Key: ATLAS-931
> URL: https://issues.apache.org/jira/browse/ATLAS-931
> Project: Atlas
>  Issue Type: Bug
>Reporter: Prasad  S Madugundu
>Assignee: David Kantor
>Priority: Blocker
> Attachments: rb49047.patch
>
>
> When Atlas is configured for hard deletes, entity deletion fails with an 
> EntityNotFoundException when retrieving a deleted entity to include in the 
> response.  This occurs when the delete operation does not update any objects, 
> so that the list of updated guids returned by the service layer is empty and 
> EntityResource uses a deleted entity guid to retrieve the "sample" entity 
> definition to include the response.  If hard delete is enabled, the entity no 
> longer exists and the entity lookup fails.
> SEVERE: Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in 
> the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: 
> Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
>   at 
> org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
>   at 
> org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
>   at 
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
>   at 
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
>   at 
> org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
>   at 
> org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)



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


[jira] [Commented] (ATLAS-932) UI: 'create tag' button does not work

2016-06-21 Thread Suma Shivaprasad (JIRA)

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

Suma Shivaprasad commented on ATLAS-932:


+1

> UI: 'create tag' button does not work
> -
>
> Key: ATLAS-932
> URL: https://issues.apache.org/jira/browse/ATLAS-932
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-932.patch
>
>
> With the latest Atlas from master, clicking on 'Create Tag' button does not 
> popup dialog to get details of new tag. Following error is seen in the Java 
> Console:
> Uncaught TypeError: Cannot read property 'get' of undefined
> CreateTagLayoutView.js:60



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


[jira] [Updated] (ATLAS-932) UI: 'create tag' button does not work

2016-06-21 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj updated ATLAS-932:
---
Attachment: ATLAS-932.patch

> UI: 'create tag' button does not work
> -
>
> Key: ATLAS-932
> URL: https://issues.apache.org/jira/browse/ATLAS-932
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-932.patch
>
>
> With the latest Atlas from master, clicking on 'Create Tag' button does not 
> popup dialog to get details of new tag. Following error is seen in the Java 
> Console:
> Uncaught TypeError: Cannot read property 'get' of undefined
> CreateTagLayoutView.js:60



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


[jira] [Created] (ATLAS-932) UI: 'create tag' button does not work

2016-06-21 Thread Madhan Neethiraj (JIRA)
Madhan Neethiraj created ATLAS-932:
--

 Summary: UI: 'create tag' button does not work
 Key: ATLAS-932
 URL: https://issues.apache.org/jira/browse/ATLAS-932
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
 Fix For: 0.7-incubating


With the latest Atlas from master, clicking on 'Create Tag' button does not 
popup dialog to get details of new tag. Following error is seen in the Java 
Console:
Uncaught TypeError: Cannot read property 'get' of undefined
CreateTagLayoutView.js:60



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


Build failed in Jenkins: apache-atlas-nightly #335

2016-06-21 Thread Apache Jenkins Server
See 

Changes:

[sumasai.shivaprasad] ATLAS-928 UI is not showing the name column for hive 
tables in the

--
[...truncated 5988 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ atlas-webapp 
---
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:clean (clean) @ atlas-webapp ---
[WARNING] Keystore file 
'
 doesn't exist.
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 55 Java sources to 

[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 55 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 40 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 40 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[jira] [Updated] (ATLAS-931) Delete entities fails when hard delete is configured

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor updated ATLAS-931:
---
Attachment: rb49047.patch

> Delete entities fails when hard delete is configured
> 
>
> Key: ATLAS-931
> URL: https://issues.apache.org/jira/browse/ATLAS-931
> Project: Atlas
>  Issue Type: Bug
>Reporter: Prasad  S Madugundu
>Assignee: David Kantor
>Priority: Blocker
> Attachments: rb49047.patch
>
>
> When Atlas is configured for hard deletes, entity deletion fails with an 
> EntityNotFoundException when retrieving a deleted entity to include in the 
> response.  This occurs when the delete operation does not update any objects, 
> so that the list of updated guids returned by the service layer is empty and 
> EntityResource uses a deleted entity guid to retrieve the "sample" entity 
> definition to include the response.  If hard delete is enabled, the entity no 
> longer exists and the entity lookup fails.
> SEVERE: Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in 
> the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: 
> Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
>   at 
> org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
>   at 
> org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
>   at 
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
>   at 
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
>   at 
> org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
>   at 
> org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)



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


[jira] [Commented] (ATLAS-928) UI is not showing the name column for hive tables in the schema tab

2016-06-21 Thread Suma Shivaprasad (JIRA)

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

Suma Shivaprasad commented on ATLAS-928:


+1. Tested with various hive_table entities

> UI is not showing the name column for hive tables in the schema tab
> ---
>
> Key: ATLAS-928
> URL: https://issues.apache.org/jira/browse/ATLAS-928
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-928.patch, hive_schema_response.json
>
>
> * Create a hive table from the hive hook.
> * Search for it in the UI, and select the schema tab
> * There is no name shown for the columns of the table (although all other 
> attributes like comment, data type are present).
> The same issue does not occur for quick_start Tables.
> The reason seems to be that the UI is using the attributeDefinitions element 
> in the return of the schema API to decide what columns to show. With 
> ATLAS-819, the name attribute was made a common attribute via a supertype for 
> assets like hive tables. The Schema API does not return the super type 
> attributes in the attributeDefinitions. Hence, even though the response of 
> the schema API contains the name attribute, because it is missing from the 
> attributeDefinitions, it is not picked up.



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


Build failed in Jenkins: apache-atlas-nightly #334

2016-06-21 Thread Apache Jenkins Server
See 

Changes:

[hyamijala] ATLAS-765 Need documentation for Authentication and Authorization

[sumasai.shivaprasad] ATLAS-822 Type updates - don't allow updating supertypes 
( shwethags via

[sumasai.shivaprasad] Updated release notes for ATLAS-922

--
[...truncated 5988 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ atlas-webapp 
---
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:clean (clean) @ atlas-webapp ---
[WARNING] Keystore file 
'
 doesn't exist.
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 55 Java sources to 

[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 55 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 40 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 40 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp 

[jira] [Updated] (ATLAS-931) Delete entities fails when hard delete is configured

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor updated ATLAS-931:
---
Description: 
When Atlas is configured for hard deletes, entity deletion fails with an 
EntityNotFoundException when retrieving a deleted entity to include in the 
response.  This occurs when the delete operation does not update any objects, 
so that the list of updated guids returned by the service layer is empty and 
EntityResource uses a deleted entity guid to retrieve the "sample" entity 
definition to include the response.  If hard delete is enabled, the entity no 
longer exists and the entity lookup fails.

SEVERE: Could not find an entity in the repository with __guid = 
d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in the 
repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 

Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: Could 
not find an entity in the repository with __guid = 
d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
at 
org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
at 
org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
at 
org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
at 
org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
at 
org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)

  was:
With the code that I pulled on 17 June 2016, DELETE method fails with the 
following stack trace:

SEVERE: Could not find an entity in the repository with __guid = 
d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in the 
repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 

Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: Could 
not find an entity in the repository with __guid = 
d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
at 
org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
at 
org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
at 
org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
at 
org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
at 
org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:507)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 

[jira] [Commented] (ATLAS-928) UI is not showing the name column for hive tables in the schema tab

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-928:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/1281/ATLAS-928.patch
  against master revision 3a68ea8.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 378 new 
Findbugs (version 2.0.3) 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 :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/346//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/346//console

This message is automatically generated.

> UI is not showing the name column for hive tables in the schema tab
> ---
>
> Key: ATLAS-928
> URL: https://issues.apache.org/jira/browse/ATLAS-928
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-928.patch, hive_schema_response.json
>
>
> * Create a hive table from the hive hook.
> * Search for it in the UI, and select the schema tab
> * There is no name shown for the columns of the table (although all other 
> attributes like comment, data type are present).
> The same issue does not occur for quick_start Tables.
> The reason seems to be that the UI is using the attributeDefinitions element 
> in the return of the schema API to decide what columns to show. With 
> ATLAS-819, the name attribute was made a common attribute via a supertype for 
> assets like hive tables. The Schema API does not return the super type 
> attributes in the attributeDefinitions. Hence, even though the response of 
> the schema API contains the name attribute, because it is missing from the 
> attributeDefinitions, it is not picked up.



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


[jira] [Updated] (ATLAS-931) Delete instances when hard delete is configured

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor updated ATLAS-931:
---
Summary: Delete instances when hard delete is configured  (was: Delete 
instances method fails in some scenarios)

> Delete instances when hard delete is configured
> ---
>
> Key: ATLAS-931
> URL: https://issues.apache.org/jira/browse/ATLAS-931
> Project: Atlas
>  Issue Type: Bug
>Reporter: Prasad  S Madugundu
>Assignee: David Kantor
>Priority: Blocker
>
> With the code that I pulled on 17 June 2016, DELETE method fails with the 
> following stack trace:
> SEVERE: Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in 
> the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: 
> Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
>   at 
> org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
>   at 
> org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
>   at 
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
>   at 
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
>   at 
> org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
>   at 
> org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
>   at java.lang.reflect.Method.invoke(Method.java:507)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
>   at 
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
>   at 
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
>   at 
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
>   at 
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
>   at 
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
>   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
>   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
>   at 
> 

[jira] [Resolved] (ATLAS-922) remove test atlas-application.properties embedded in atlas-typesystem.jar

2016-06-21 Thread Suma Shivaprasad (JIRA)

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

Suma Shivaprasad resolved ATLAS-922.

   Resolution: Fixed
Fix Version/s: 0.7-incubating

Committed as part of ATLAS-822. Thanks [~madhan.neethiraj] and [~yhemanth]

> remove test atlas-application.properties embedded in atlas-typesystem.jar
> -
>
> Key: ATLAS-922
> URL: https://issues.apache.org/jira/browse/ATLAS-922
> Project: Atlas
>  Issue Type: Bug
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-922.patch
>
>
> Currently atlas-typesystem.jar embeds atlas-application.properties containing 
> test properties as a resource. This embedded test properties file can be 
> loaded in the application/hook, instead of the expected configuration file, 
> if atlas-typesystem.jar appears earlier in the CLASSPATH. To prevent this, 
> atlas-application.properties containing test properties should be removed 
> from atlas-typesystem.jar.



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


[jira] [Commented] (ATLAS-856) Lazy-load type cache provider

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor commented on ATLAS-856:


[~shwethags] Yes your changes make sense, good idea to use Configuration and 
mutate the property setting needed for the tests.  I noticed your patch does a 
delete and add of classes that I renamed.  Rather than lose the history of 
those renamed modules, I will apply your changes in my source, and upload a new 
set of changes to review board and attach an updated.  That way the renames 
will be recorded in git correctly.  Thanks very much for your help on this.

> Lazy-load type cache provider
> -
>
> Key: ATLAS-856
> URL: https://issues.apache.org/jira/browse/ATLAS-856
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: David Kantor
> Attachments: ATLAS-856.patch, rb48565.patch
>
>
> A modified version of the default local cache provider which will run a 
> lookup on the backend storage if a requested type is not found in the cache, 
> and load it in the cache and return it if it's found. This lazy-loading cache 
> would cover the case where new types are registered, not the case where 
> existing types are modified, while avoiding the deployment/maintenance and 
> performance impact of a distributed cache in an HA environment.



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


Build failed in Jenkins: apache-atlas-nightly #333

2016-06-21 Thread Apache Jenkins Server
See 

Changes:

[hyamijala] ATLAS-904 Hive hook fails due to session state not being set 
(sumasai

[sshivalingamurthy] ATLAS-930 QuickStart is failing when run after a specific 
sequence of

--
[...truncated 6025 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ atlas-webapp 
---
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:clean (clean) @ atlas-webapp ---
[WARNING] Keystore file 
'
 doesn't exist.
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 55 Java sources to 

[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 55 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 40 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 40 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 

[jira] [Commented] (ATLAS-904) Hive hook fails due to session state not being set

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-904:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812227/ATLAS-904.4.patch
  against master revision 32a5b76.

{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 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 378 new 
Findbugs (version 2.0.3) 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 :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/345//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/345//console

This message is automatically generated.

> Hive hook fails due to session state not being set
> --
>
> Key: ATLAS-904
> URL: https://issues.apache.org/jira/browse/ATLAS-904
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-904.1.patch, ATLAS-904.2.patch, ATLAS-904.3.patch, 
> ATLAS-904.4.patch, ATLAS-904.patch
>
>
> {noformat}
> 2016-06-15 11:34:30,423 WARN  [Atlas Logger 0]: hook.HiveHook 
> (HiveHook.java:normalize(557)) - Could not rewrite query due to error. 
> Proceeding with original query EXPORT TABLE test_export_table to 
> 'hdfs://localhost:9000/hive_tables/test_path1'
> java.lang.NullPointerException: Conf non-local session path expected to be 
> non-null
>   at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:204)
>   at 
> org.apache.hadoop.hive.ql.session.SessionState.getHDFSSessionPath(SessionState.java:641)
>   at org.apache.hadoop.hive.ql.Context.(Context.java:133)
>   at org.apache.hadoop.hive.ql.Context.(Context.java:120)
>   at 
> org.apache.atlas.hive.rewrite.HiveASTRewriter.(HiveASTRewriter.java:44)
>   at org.apache.atlas.hive.hook.HiveHook.normalize(HiveHook.java:554)
>   at 
> org.apache.atlas.hive.hook.HiveHook.getProcessReferenceable(HiveHook.java:702)
>   at 
> 

[jira] [Commented] (ATLAS-856) Lazy-load type cache provider

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S commented on ATLAS-856:
---

[~dkantor], the attached patch has some changes to not create 
atlas-application.properties in respository/test. See if the changes make sense 
to you

> Lazy-load type cache provider
> -
>
> Key: ATLAS-856
> URL: https://issues.apache.org/jira/browse/ATLAS-856
> Project: Atlas
>  Issue Type: New Feature
>Reporter: David Kantor
>Assignee: David Kantor
> Attachments: ATLAS-856.patch, rb48565.patch
>
>
> A modified version of the default local cache provider which will run a 
> lookup on the backend storage if a requested type is not found in the cache, 
> and load it in the cache and return it if it's found. This lazy-loading cache 
> would cover the case where new types are registered, not the case where 
> existing types are modified, while avoiding the deployment/maintenance and 
> performance impact of a distributed cache in an HA environment.



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


[jira] [Updated] (ATLAS-765) Need documentation for Authentication and Authorization features of Atlas

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala updated ATLAS-765:
---
Attachment: ATLAS-765-1.patch

The attached file makes editorial changes to the text provided in the original 
patch. It also adds a link to the new wiki page in Index.twiki.

> Need documentation for Authentication and Authorization features of Atlas
> -
>
> Key: ATLAS-765
> URL: https://issues.apache.org/jira/browse/ATLAS-765
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-765-1.patch, ATLAS-765.patch
>
>
> Since authentication and authorization are incompatible changes to Atlas 
> source, it will be very helpful to have detailed user documentation on how to 
> set this up using various user / policy stores. The sooner we have this, the 
> better it will be for the community.



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


Re: Review Request 49016: ATLAS-765 - Documentation for Authentication and Authorization features of Atlas

2016-06-21 Thread Hemanth Yamijala

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


Ship it!




Looks ok to me. I have minor editorial comments (just in the language) and will 
make the changes before commit.

- Hemanth Yamijala


On June 21, 2016, 10:04 a.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/49016/
> ---
> 
> (Updated June 21, 2016, 10:04 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Mehul Parikh, Shwetha GS, Suma 
> Shivaprasad, and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-765
> https://issues.apache.org/jira/browse/ATLAS-765
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch provide documentation for Authentication and Authorization 
> features of Atlas in twiki format.
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/Authentication-Authorization.twiki PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/49016/diff/
> 
> 
> Testing
> ---
> 
> Verified the html file created in docs/target/site directory after running 
> mvn site.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>



[jira] [Commented] (ATLAS-822) Type updates - don't allow updating supertypes

2016-06-21 Thread Suma Shivaprasad (JIRA)

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

Suma Shivaprasad commented on ATLAS-822:


+1

> Type updates - don't allow updating supertypes
> --
>
> Key: ATLAS-822
> URL: https://issues.apache.org/jira/browse/ATLAS-822
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-822-v2.patch, ATLAS-822.patch
>
>
> In type updates, we allow adding super types. But set of super types is 
> maintained in every entity, and this type update will require updating all 
> the entities of that type which is not handled currently. We should either 
> update all entities or not allow updating super type information



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


[jira] [Updated] (ATLAS-904) Hive hook fails due to session state not being set

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala updated ATLAS-904:
---
Attachment: ATLAS-904.4.patch

There were minor import rebases in HiveHookIT

> Hive hook fails due to session state not being set
> --
>
> Key: ATLAS-904
> URL: https://issues.apache.org/jira/browse/ATLAS-904
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-904.1.patch, ATLAS-904.2.patch, ATLAS-904.3.patch, 
> ATLAS-904.4.patch, ATLAS-904.patch
>
>
> {noformat}
> 2016-06-15 11:34:30,423 WARN  [Atlas Logger 0]: hook.HiveHook 
> (HiveHook.java:normalize(557)) - Could not rewrite query due to error. 
> Proceeding with original query EXPORT TABLE test_export_table to 
> 'hdfs://localhost:9000/hive_tables/test_path1'
> java.lang.NullPointerException: Conf non-local session path expected to be 
> non-null
>   at 
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:204)
>   at 
> org.apache.hadoop.hive.ql.session.SessionState.getHDFSSessionPath(SessionState.java:641)
>   at org.apache.hadoop.hive.ql.Context.(Context.java:133)
>   at org.apache.hadoop.hive.ql.Context.(Context.java:120)
>   at 
> org.apache.atlas.hive.rewrite.HiveASTRewriter.(HiveASTRewriter.java:44)
>   at org.apache.atlas.hive.hook.HiveHook.normalize(HiveHook.java:554)
>   at 
> org.apache.atlas.hive.hook.HiveHook.getProcessReferenceable(HiveHook.java:702)
>   at 
> org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:596)
>   at org.apache.atlas.hive.hook.HiveHook.fireAndForget(HiveHook.java:222)
>   at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:77)
>   at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:182)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> 2016-06-15 11:34:30,423 ERROR [Atlas Logger 0]: hook.HiveHook 
> (HiveHook.java:run(184)) - Atlas hook failed due to error
> java.lang.NullPointerException
>   at java.lang.StringBuilder.(StringBuilder.java:109)
>   at 
> org.apache.atlas.hive.hook.HiveHook.getProcessQualifiedName(HiveHook.java:738)
>   at 
> org.apache.atlas.hive.hook.HiveHook.getProcessReferenceable(HiveHook.java:703)
>   at 
> org.apache.atlas.hive.hook.HiveHook.registerProcess(HiveHook.java:596)
>   at org.apache.atlas.hive.hook.HiveHook.fireAndForget(HiveHook.java:222)
>   at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:77)
>   at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:182)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



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


[jira] [Updated] (ATLAS-928) UI is not showing the name column for hive tables in the schema tab

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala updated ATLAS-928:
---
Attachment: ATLAS-928.patch

The right fix for this issue should probably come from the server side, but for 
now, I am attaching a temporary patch that fixes this on the UI side. 
Essentially, the attempt is for the UI to always include a name attribute if 
the returned superTypes contains 'Asset'. From my tests this is working for 
hive tables and quick start tables both. I will test more in detail, but 
putting this up in case someone can take a look.

> UI is not showing the name column for hive tables in the schema tab
> ---
>
> Key: ATLAS-928
> URL: https://issues.apache.org/jira/browse/ATLAS-928
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-928.patch, hive_schema_response.json
>
>
> * Create a hive table from the hive hook.
> * Search for it in the UI, and select the schema tab
> * There is no name shown for the columns of the table (although all other 
> attributes like comment, data type are present).
> The same issue does not occur for quick_start Tables.
> The reason seems to be that the UI is using the attributeDefinitions element 
> in the return of the schema API to decide what columns to show. With 
> ATLAS-819, the name attribute was made a common attribute via a supertype for 
> assets like hive tables. The Schema API does not return the super type 
> attributes in the attributeDefinitions. Hence, even though the response of 
> the schema API contains the name attribute, because it is missing from the 
> attributeDefinitions, it is not picked up.



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


[jira] [Assigned] (ATLAS-928) UI is not showing the name column for hive tables in the schema tab

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala reassigned ATLAS-928:
--

Assignee: Hemanth Yamijala  (was: Kalyani Kashikar)

> UI is not showing the name column for hive tables in the schema tab
> ---
>
> Key: ATLAS-928
> URL: https://issues.apache.org/jira/browse/ATLAS-928
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: hive_schema_response.json
>
>
> * Create a hive table from the hive hook.
> * Search for it in the UI, and select the schema tab
> * There is no name shown for the columns of the table (although all other 
> attributes like comment, data type are present).
> The same issue does not occur for quick_start Tables.
> The reason seems to be that the UI is using the attributeDefinitions element 
> in the return of the schema API to decide what columns to show. With 
> ATLAS-819, the name attribute was made a common attribute via a supertype for 
> assets like hive tables. The Schema API does not return the super type 
> attributes in the attributeDefinitions. Hence, even though the response of 
> the schema API contains the name attribute, because it is missing from the 
> attributeDefinitions, it is not picked up.



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


Re: Review Request 48939: ATLAS-904 Handle process qualified name per Hive Operation

2016-06-21 Thread Hemanth Yamijala

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


Ship it!




Ship It!

- Hemanth Yamijala


On June 20, 2016, 6:22 p.m., Suma Shivaprasad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48939/
> ---
> 
> (Updated June 20, 2016, 6:22 p.m.)
> 
> 
> Review request for atlas, Shwetha GS and Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-904
> https://issues.apache.org/jira/browse/ATLAS-904
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> 1. Process qualified name = HiveOperation.name + sorted inputs + sorted 
> outputs
> 2. HiveOperation.name doesnt provide identifiers for identiifying INSERT, 
> INSERT_OVERWRITE, UPDATE, DELETE etc separately . Hence adding 
> WriteEntity.WriteType as well which exhibits the following behaviour
> a. If there are multiple outputs, for each output, adds the query 
> type(WriteType)
> b. if query being run if is type INSERT [into/overwrite] TABLE [PARTITION], 
> WriteType is INSERT/INSERT_OVERWRITE
> b. If query is of type INSERT OVERWRITE hdfs_path, adds WriteType as 
> PATH_WRITE
> c. If query is of type UPDATE/DELETE, adds type as UPDATE/DELETE [ Note - 
> linage is not available for this since this is single table operation]
> 3.When input is of type local dir or hdfs path currently, it doesnt add it to 
> qualified name. The reason is that partition based paths cause a lot of 
> processes to be created in this case instead of updating the same process.
> Pending:
> Address Shwetha G S suggestion to add hdfs paths to process qualified name 
> only in case of non-partition based queries. This needs to be done per 
> HiveOperation type
> 1. if HiveOperation = LOAD, IMPORT, EXPORT - detect if the current query 
> context is dealing with partitions and do not add if it is partition based.
> 2. If HiveOperation = INSERT OVERWRITE DFS_PATH/LOCAL_PATH , then detect if 
> the query context is dealing with a partitioned table in inputs and decide if 
> we need to add or not.
> 
> 
> Diffs
> -
> 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/bridge/HiveMetaStoreBridge.java
>  c956a32 
>   addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java 
> 5d9950f 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> 5a175e7 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 0713d30 
> 
> Diff: https://reviews.apache.org/r/48939/diff/
> 
> 
> Testing
> ---
> 
> Existing tests modified to query with new qualified name. Need to add tests 
> for INSERT INTO TABLE
> 
> 
> Thanks,
> 
> Suma Shivaprasad
> 
>



[jira] [Commented] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S commented on ATLAS-930:
---

+1, committing

> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-930.patch, application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805. 
> However, I need a more complicated sequence of operations to reproduce the 
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata 
> service API CREATE_ENTITY failed with status 500(Internal Server Error) 
> Response Body ({"error":"Could not commit transaction due to exception during 
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could 
> not commit transaction due to exception during persistence\n\tat 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>  
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>  
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>  
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>  
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
>  org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>  
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
>  

[jira] [Updated] (ATLAS-920) Lineage graph is broken when there are multiple paths from same source table

2016-06-21 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj updated ATLAS-920:
---
Fix Version/s: (was: 0.7-incubating)

> Lineage graph is broken when there are multiple paths from same source table
> 
>
> Key: ATLAS-920
> URL: https://issues.apache.org/jira/browse/ATLAS-920
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Blocker
> Attachments: Screen Shot 2016-06-20 at 4.09.02 PM.png, Screen Shot 
> 2016-06-20 at 4.31.58 PM.png, Screen Shot 2016-06-20 at 4.49.24 PM.png
>
>
> Steps to reproduce
> 1. CREATE TABLE test_table(abc string) partitioned by (dt date)
> 2.  CREATE TABLE test_lineage as SELECT * from test_table
> 3. CREATE VIEW test_view as SELECT * from test_table
> 4. ALTER VIEW test_view as SELECT * from test_lineage
> The lineage is broken as seen in screen shot



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


[jira] [Updated] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

2016-06-21 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj updated ATLAS-624:
---
Fix Version/s: (was: 0.7-incubating)

> UI: Clicking a tag hyperlink should always result in DSL search. In some 
> cases, results in full-text search.
> 
>
> Key: ATLAS-624
> URL: https://issues.apache.org/jira/browse/ATLAS-624
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-624.1.patch, ATLAS-624.patch
>
>
> UI: Clicking a tag hyperlink should always result in DSL search.
> 1. Create a hive table with a column, Attach a tag to the column.
> 2. Now navigate to the schema tab of hive_table search result.
> 3. Click on the attached tag - This will result in full-text query search of 
> that tag, which will always return empty response. This should be ideally a 
> DSL search query which will show all the entities associated with that tag.
> Ideally, this should be true in all cases. i.e; Whenever a tag hyperlink is 
> clicked on atlas UI, this should result in DSL search only.
> UI snapshot for reference: 
> https://monosnap.com/file/QKWcuSeG85UI3NDXakvR7iD9LJd1RC



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


[jira] [Updated] (ATLAS-847) UI: Audit versioning does not paginate details from Atlas server

2016-06-21 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj updated ATLAS-847:
---
Fix Version/s: (was: 0.7-incubating)

> UI: Audit versioning does not paginate details from Atlas server
> 
>
> Key: ATLAS-847
> URL: https://issues.apache.org/jira/browse/ATLAS-847
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Kalyani Kashikar
>
> In ATLAS-664, the capability to view Audit events was added to the Atlas 
> admin UI. However, currently, the API call made only fetches the first 100 
> events (which is the default if no count is sent). In order to fetch the next 
> set of events, further API calls need to be made to the Audit API, by 
> providing additional parameters in the API. This JIRA is to track the 
> required changes in UI.



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


[jira] [Commented] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-927:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812162/ATLAS-927.patch
  against master revision 32a5b76.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 382 new 
Findbugs (version 2.0.3) 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 :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/343//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/343//console

This message is automatically generated.

> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-927.patch
>
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded 
> version:
> {code}
> Version :  
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project 
> version



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


Re: Review Request 48565: ATLAS-856: lazy-load type cache

2016-06-21 Thread David Kantor


> On June 21, 2016, 8:49 a.m., Shwetha GS wrote:
> > repository/src/test/resources/org/apache/atlas/repository/typestore/atlas-application.properties,
> >  line 2
> > 
> >
> > is there any way we can avoid having a copy of 
> > atlas-application.properties here?

I'm not sure how to avoid this given the current Atlas configuration mechanism. 
 I have added tests that depend on StoreBackedTypeCache being configured as the 
TypeCache implementation class in atlas-application.properties.  Other than 
using the atlas.conf system property to point ApplicationProperties at a 
directory which contains a properties file that has the setting needed for the 
tests, I don't see another way of overriding the default value of the 
atlas.TypeCache.impl property.  I suppose we could enhance 
ApplicationProperties to support overriding the configured value with a system 
property of the same name.  Is your main concern to avoid the proliferation of 
test versions of atlas-application.properties?


- David


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


On June 20, 2016, 9:57 p.m., David Kantor wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48565/
> ---
> 
> (Updated June 20, 2016, 9:57 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-856
> https://issues.apache.org/jira/browse/ATLAS-856
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-856: Implemented StoreBackedTypeCache, an extension of DefaultTypeCache 
> which loads the requested type from the type store if it is not found in the 
> cache, and adds it to the cache if it's found in the store.  Any attribute 
> and super types that are required by the requested type are also loaded from 
> the store if they are not already in the cache.
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/RepositoryMetadataModule.java 
> c4c767827014a265471250306f35316a0b4ed67f 
>   
> repository/src/main/java/org/apache/atlas/repository/typestore/GraphBackedTypeStore.java
>  5ed9e02eb85ec25b63540cab40d148914d410786 
>   
> repository/src/main/java/org/apache/atlas/repository/typestore/ITypeStore.java
>  790c4b31c37e51289585f6f891366a8d8c86b168 
>   
> repository/src/main/java/org/apache/atlas/repository/typestore/StoreBackedTypeCache.java
>  PRE-CREATION 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  d9e6cb9e9243c4d53808089efeaaaf1329561df3 
>   
> repository/src/test/java/org/apache/atlas/repository/typestore/GraphBackedTypeStoreTest.java
>  961442bbcaff86b472a876e6c348aa9e65c1efca 
>   
> repository/src/test/java/org/apache/atlas/repository/typestore/StoreBackedTypeCacheConfigurationTest.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/repository/typestore/StoreBackedTypeCacheTest.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/repository/typestore/StoreBackedTypeCacheTestModule.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/service/StoreBackedTypeCacheMetadataServiceTest.java
>  PRE-CREATION 
>   
> repository/src/test/java/org/apache/atlas/services/DefaultMetadataServiceMockTest.java
>  effee2a43d8c1e1369b52f1c3899cb882ea52aa1 
>   
> repository/src/test/resources/org/apache/atlas/repository/typestore/atlas-application.properties
>  PRE-CREATION 
>   typesystem/src/main/java/org/apache/atlas/typesystem/types/TypeSystem.java 
> 14f1968c2dd6765793c1c43e3ea1ed5f3a9c8a42 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/cache/DefaultTypeCacheProvider.java
>  700bda6463e039b8f6ad2ac75840f9e637a883b0 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/cache/ITypeCacheProvider.java
>  55e9ddc463c748d3cd631d11860235dbe1a92714 
>   
> typesystem/src/test/java/org/apache/atlas/typesystem/types/cache/DefaultTypeCacheProviderTest.java
>  c426d50f52dfd99835d9fcf1c6f95841ba4b5494 
> 
> Diff: https://reviews.apache.org/r/48565/diff/
> 
> 
> Testing
> ---
> 
> Ran all unit and integration tests with no regressions.
> 
> 
> Thanks,
> 
> David Kantor
> 
>



[jira] [Updated] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala updated ATLAS-930:
---
Priority: Critical  (was: Major)

> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-930.patch, application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805. 
> However, I need a more complicated sequence of operations to reproduce the 
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata 
> service API CREATE_ENTITY failed with status 500(Internal Server Error) 
> Response Body ({"error":"Could not commit transaction due to exception during 
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could 
> not commit transaction due to exception during persistence\n\tat 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>  
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>  
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>  
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>  
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
>  org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>  
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
>  

[jira] [Updated] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala updated ATLAS-930:
---
Attachment: ATLAS-930.patch

Attaching a fairly simple patch. Verified the failing scenario works fine with 
this patch. All existing tests pass.

> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-930.patch, application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805. 
> However, I need a more complicated sequence of operations to reproduce the 
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata 
> service API CREATE_ENTITY failed with status 500(Internal Server Error) 
> Response Body ({"error":"Could not commit transaction due to exception during 
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could 
> not commit transaction due to exception during persistence\n\tat 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>  
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>  
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>  
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>  
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
>  org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>  
> 

[jira] [Assigned] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala reassigned ATLAS-930:
--

Assignee: Hemanth Yamijala

> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Fix For: 0.7-incubating
>
> Attachments: application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805. 
> However, I need a more complicated sequence of operations to reproduce the 
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata 
> service API CREATE_ENTITY failed with status 500(Internal Server Error) 
> Response Body ({"error":"Could not commit transaction due to exception during 
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could 
> not commit transaction due to exception during persistence\n\tat 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>  
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>  
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>  
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>  
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
>  org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>  
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
>  

[jira] [Updated] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala updated ATLAS-930:
---
Fix Version/s: 0.7-incubating

> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Fix For: 0.7-incubating
>
> Attachments: application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805. 
> However, I need a more complicated sequence of operations to reproduce the 
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata 
> service API CREATE_ENTITY failed with status 500(Internal Server Error) 
> Response Body ({"error":"Could not commit transaction due to exception during 
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could 
> not commit transaction due to exception during persistence\n\tat 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>  
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>  
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>  
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>  
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
>  org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>  
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
>  

[jira] [Commented] (ATLAS-822) Type updates - don't allow updating supertypes

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-822:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812160/ATLAS-822-v2.patch
  against master revision 32a5b76.

{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 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 382 new 
Findbugs (version 2.0.3) 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 :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/342//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/342//console

This message is automatically generated.

> Type updates - don't allow updating supertypes
> --
>
> Key: ATLAS-822
> URL: https://issues.apache.org/jira/browse/ATLAS-822
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-822-v2.patch, ATLAS-822.patch
>
>
> In type updates, we allow adding super types. But set of super types is 
> maintained in every entity, and this type update will require updating all 
> the entities of that type which is not handled currently. We should either 
> update all entities or not allow updating super type information



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


[jira] [Assigned] (ATLAS-931) Delete instances method fails in some scenarios

2016-06-21 Thread David Kantor (JIRA)

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

David Kantor reassigned ATLAS-931:
--

Assignee: David Kantor

> Delete instances method fails in some scenarios
> ---
>
> Key: ATLAS-931
> URL: https://issues.apache.org/jira/browse/ATLAS-931
> Project: Atlas
>  Issue Type: Bug
>Reporter: Prasad  S Madugundu
>Assignee: David Kantor
>Priority: Blocker
>
> With the code that I pulled on 17 June 2016, DELETE method fails with the 
> following stack trace:
> SEVERE: Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in 
> the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: 
> Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
>   at 
> org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
>   at 
> org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
>   at 
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
>   at 
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
>   at 
> org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
>   at 
> org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
>   at java.lang.reflect.Method.invoke(Method.java:507)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
>   at 
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
>   at 
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
>   at 
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
>   at 
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
>   at 
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
>   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
>   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
>   at 
> com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
>   at 

[jira] [Created] (ATLAS-931) Delete instances method fails in some scenarios

2016-06-21 Thread Prasad S Madugundu (JIRA)
Prasad  S Madugundu created ATLAS-931:
-

 Summary: Delete instances method fails in some scenarios
 Key: ATLAS-931
 URL: https://issues.apache.org/jira/browse/ATLAS-931
 Project: Atlas
  Issue Type: Improvement
Reporter: Prasad  S Madugundu
Priority: Blocker


With the code that I pulled on 17 June 2016, DELETE method fails with the 
following stack trace:

SEVERE: Could not find an entity in the repository with __guid = 
d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in the 
repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 

Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: Could 
not find an entity in the repository with __guid = 
d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
at 
org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
at 
org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
at 
org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
at 
org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
at 
org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
at 
org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:507)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
at 
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
at 
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
at 
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
at 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
at 
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)
at 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
at 
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
at 
com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
   

[jira] [Updated] (ATLAS-931) Delete instances method fails in some scenarios

2016-06-21 Thread Prasad S Madugundu (JIRA)

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

Prasad  S Madugundu updated ATLAS-931:
--
Issue Type: Bug  (was: Improvement)

> Delete instances method fails in some scenarios
> ---
>
> Key: ATLAS-931
> URL: https://issues.apache.org/jira/browse/ATLAS-931
> Project: Atlas
>  Issue Type: Bug
>Reporter: Prasad  S Madugundu
>Priority: Blocker
>
> With the code that I pulled on 17 June 2016, DELETE method fails with the 
> following stack trace:
> SEVERE: Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> com.ibm.analytics.oms.exception.AtlasException: Could not find an entity in 
> the repository with __guid = d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
> Caused by: org.apache.atlas.typesystem.exception.EntityNotFoundException: 
> Could not find an entity in the repository with __guid = 
> d7b21c03-e518-44ed-83d3-2593e9c50dd1, 
>   at 
> org.apache.atlas.repository.graph.GraphHelper.findVertex(GraphHelper.java:183)
>   at 
> org.apache.atlas.repository.graph.GraphHelper.getVertexForGUID(GraphHelper.java:301)
>   at 
> org.apache.atlas.repository.graph.GraphBackedMetadataRepository.getEntityDefinition(GraphBackedMetadataRepository.java:146)
>   at 
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:42)
>   at 
> org.apache.atlas.services.DefaultMetadataService.getEntityDefinition(DefaultMetadataService.java:371)
>   at 
> org.apache.atlas.web.resources.EntityResource.getResponse(EntityResource.java:171)
>   at 
> org.apache.atlas.web.resources.EntityResource.deleteEntities(EntityResource.java:388)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
>   at java.lang.reflect.Method.invoke(Method.java:507)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
>   at 
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
>   at 
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
>   at 
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)
>   at 
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)
>   at 
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)
>   at 
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
>   at 
> org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)
>   at 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
>   at 
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)
>   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)
>   at com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)
>   at 
> com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)
>   at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)
>   

[jira] [Updated] (ATLAS-584) Integrate CSRF prevention filter

2016-06-21 Thread Kalyani Kashikar (JIRA)

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

Kalyani Kashikar updated ATLAS-584:
---
Due Date: 22/Jun/16

> Integrate CSRF prevention filter
> 
>
> Key: ATLAS-584
> URL: https://issues.apache.org/jira/browse/ATLAS-584
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Kalyani Kashikar
>Priority: Blocker
> Fix For: 0.7-incubating
>
>
> Atlas needs to provide protection for CSRF protection.



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


[jira] [Commented] (ATLAS-822) Type updates - don't allow updating supertypes

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-822:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812160/ATLAS-822-v2.patch
  against master revision 32a5b76.

{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 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 382 new 
Findbugs (version 2.0.3) 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 :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/341//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/341//console

This message is automatically generated.

> Type updates - don't allow updating supertypes
> --
>
> Key: ATLAS-822
> URL: https://issues.apache.org/jira/browse/ATLAS-822
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-822-v2.patch, ATLAS-822.patch
>
>
> In type updates, we allow adding super types. But set of super types is 
> maintained in every entity, and this type update will require updating all 
> the entities of that type which is not handled currently. We should either 
> update all entities or not allow updating super type information



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


[jira] [Assigned] (ATLAS-928) UI is not showing the name column for hive tables in the schema tab

2016-06-21 Thread Kalyani Kashikar (JIRA)

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

Kalyani Kashikar reassigned ATLAS-928:
--

Assignee: Kalyani Kashikar

> UI is not showing the name column for hive tables in the schema tab
> ---
>
> Key: ATLAS-928
> URL: https://issues.apache.org/jira/browse/ATLAS-928
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Kalyani Kashikar
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: hive_schema_response.json
>
>
> * Create a hive table from the hive hook.
> * Search for it in the UI, and select the schema tab
> * There is no name shown for the columns of the table (although all other 
> attributes like comment, data type are present).
> The same issue does not occur for quick_start Tables.
> The reason seems to be that the UI is using the attributeDefinitions element 
> in the return of the schema API to decide what columns to show. With 
> ATLAS-819, the name attribute was made a common attribute via a supertype for 
> assets like hive tables. The Schema API does not return the super type 
> attributes in the attributeDefinitions. Hence, even though the response of 
> the schema API contains the name attribute, because it is missing from the 
> attributeDefinitions, it is not picked up.



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


[jira] [Commented] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala commented on ATLAS-930:


Right, so with more debugging, the case is narrowed to:

* Create a hive table
* Call the API api/atlas/lineage/{GUID}/inputs/graph
* Run quick start - the failure is seen

The reason for the failure seems to be that the new lineage APIs are missing 
the {{GraphTransaction}} annotation. Hence the cause is similar to what we saw 
in ATLAS-805, except it is happening at a different place.

I'll put up a patch that hopefully fixes this.

> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
> Attachments: application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805. 
> However, I need a more complicated sequence of operations to reproduce the 
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata 
> service API CREATE_ENTITY failed with status 500(Internal Server Error) 
> Response Body ({"error":"Could not commit transaction due to exception during 
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could 
> not commit transaction due to exception during persistence\n\tat 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>  
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>  
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>  
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>  
> 

[jira] [Commented] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

2016-06-21 Thread Kalyani Kashikar (JIRA)

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

Kalyani Kashikar commented on ATLAS-624:


[~yhemanth]  :: Unable to reproduce the issue that you have mentioned. 
List of Steps : 
1) We are on TAGS Tab 
2) Click on PII Tag 
3)  Click on ( . . . ) action item on left nav for PII tag
4)  Click on Search Tag   

*Actual Result:*
This does trigger a dsl query on search results page. 

Let me know if you want to discuss this. 

> UI: Clicking a tag hyperlink should always result in DSL search. In some 
> cases, results in full-text search.
> 
>
> Key: ATLAS-624
> URL: https://issues.apache.org/jira/browse/ATLAS-624
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Kalyani Kashikar
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-624.1.patch, ATLAS-624.patch
>
>
> UI: Clicking a tag hyperlink should always result in DSL search.
> 1. Create a hive table with a column, Attach a tag to the column.
> 2. Now navigate to the schema tab of hive_table search result.
> 3. Click on the attached tag - This will result in full-text query search of 
> that tag, which will always return empty response. This should be ideally a 
> DSL search query which will show all the entities associated with that tag.
> Ideally, this should be true in all cases. i.e; Whenever a tag hyperlink is 
> clicked on atlas UI, this should result in DSL search only.
> UI snapshot for reference: 
> https://monosnap.com/file/QKWcuSeG85UI3NDXakvR7iD9LJd1RC



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


[jira] [Assigned] (ATLAS-584) Integrate CSRF prevention filter

2016-06-21 Thread Kalyani Kashikar (JIRA)

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

Kalyani Kashikar reassigned ATLAS-584:
--

Assignee: Kalyani Kashikar  (was: Saqeeb Shaikh)

> Integrate CSRF prevention filter
> 
>
> Key: ATLAS-584
> URL: https://issues.apache.org/jira/browse/ATLAS-584
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Kalyani Kashikar
>Priority: Blocker
> Fix For: 0.7-incubating
>
>
> Atlas needs to provide protection for CSRF protection.



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


Review Request 49023: ATLAS-927 : aboutAtlas_tmpl.html has hard-coded project version

2016-06-21 Thread Kalyani Kashikar

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

Review request for atlas, Ayub Pathan, Madhan Neethiraj, Mehul Parikh, 
Selvamohan Neethiraj, and Hemanth Yamijala.


Bugs: ATLAS-927
https://issues.apache.org/jira/browse/ATLAS-927


Repository: atlas


Description
---

**Issue :**
dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded 
version. Instead, it should use mvn resource filtering to set the version to 
project version


Diffs
-

  
authorization/src/main/java/org/apache/atlas/authorize/simple/AtlasAuthorizationUtils.java
 291f11b 
  dashboardv2/public/js/models/VCommon.js 63015ec 
  dashboardv2/public/js/router/Router.js 3d2e785 
  dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html 08089b1 

Diff: https://reviews.apache.org/r/49023/diff/


Testing
---

**Verified :**
1) Ran mvn clean install
2) Verified accurate version displayed from API (in About page) : 
http://localhost:21000/api/atlas/admin/version
3) Verified version info using users from different groups.


Thanks,

Kalyani Kashikar



Build failed in Jenkins: apache-atlas-nightly #332

2016-06-21 Thread Apache Jenkins Server
See 

Changes:

[sshivalingamurthy] ATLAS-698 Remove Rexster Graph API (svimal2106 via 
shwethags)

--
[...truncated 6025 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ atlas-webapp 
---
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:clean (clean) @ atlas-webapp ---
[WARNING] Keystore file 
'
 doesn't exist.
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 55 Java sources to 

[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 55 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 40 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 40 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[jira] [Updated] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version

2016-06-21 Thread Kalyani Kashikar (JIRA)

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

Kalyani Kashikar updated ATLAS-927:
---
Attachment: (was: ATLAS-927.1.patch)

> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-927.patch
>
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded 
> version:
> {code}
> Version :  
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project 
> version



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


Re: Review Request 49022: ATLAS-822 Type updates - don't allow updating supertypes

2016-06-21 Thread Shwetha GS

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

(Updated June 21, 2016, 12:04 p.m.)


Review request for atlas.


Changes
---

fixed webapp IT


Bugs: ATLAS-822
https://issues.apache.org/jira/browse/ATLAS-822


Repository: atlas


Description
---

Type update will not allow modifying super types


Diffs (updated)
-

  addons/falcon-bridge/pom.xml f945a6c 
  addons/hdfs-model/pom.xml 80e74a2 
  addons/hive-bridge/pom.xml 24ab22f 
  addons/sqoop-bridge/pom.xml 5418885 
  addons/storm-bridge/pom.xml b51ab01 
  catalog/pom.xml 3817012 
  client/pom.xml a6b5a2f 
  notification/pom.xml f4cfdd3 
  pom.xml ecf76d0 
  repository/pom.xml 096a4b5 
  
repository/src/test/java/org/apache/atlas/repository/typestore/GraphBackedTypeStoreTest.java
 961442b 
  typesystem/pom.xml 219075b 
  
typesystem/src/main/java/org/apache/atlas/typesystem/types/HierarchicalType.java
 859ec72 
  
typesystem/src/test/java/org/apache/atlas/typesystem/types/HierarchicalTypeTest.java
 81da0be 
  webapp/pom.xml ce812c6 
  
webapp/src/test/java/org/apache/atlas/web/resources/TypesJerseyResourceIT.java 
477e4bf 

Diff: https://reviews.apache.org/r/49022/diff/


Testing
---

UTs


Thanks,

Shwetha GS



[jira] [Updated] (ATLAS-822) Type updates - don't allow updating supertypes

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-822:
--
Attachment: ATLAS-822-v2.patch

Fixed webapp IT

> Type updates - don't allow updating supertypes
> --
>
> Key: ATLAS-822
> URL: https://issues.apache.org/jira/browse/ATLAS-822
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-822-v2.patch, ATLAS-822.patch
>
>
> In type updates, we allow adding super types. But set of super types is 
> maintained in every entity, and this type update will require updating all 
> the entities of that type which is not handled currently. We should either 
> update all entities or not allow updating super type information



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


[jira] [Closed] (ATLAS-921) Processing encryption ... hangs

2016-06-21 Thread Oscar Segarra (JIRA)

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

Oscar Segarra closed ATLAS-921.
---

> Processing encryption ... hangs
> ---
>
> Key: ATLAS-921
> URL: https://issues.apache.org/jira/browse/ATLAS-921
> Project: Atlas
>  Issue Type: Bug
>Reporter: Oscar Segarra
>




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


[jira] [Commented] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala commented on ATLAS-930:


I tried the following sequences, which all seemed fine:

* Just creating hive tables and running quick start.
* Creating business taxonomy and running quick start.
* Creating hive table, default business taxonomy, search for hive_table and 
running quick start.

I am not even sure if the sequence is relevant or its just a fluke. Would be 
good if someone can replicate and confirm.

> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
> Attachments: application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805. 
> However, I need a more complicated sequence of operations to reproduce the 
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata 
> service API CREATE_ENTITY failed with status 500(Internal Server Error) 
> Response Body ({"error":"Could not commit transaction due to exception during 
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could 
> not commit transaction due to exception during persistence\n\tat 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>  
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>  
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>  
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>  
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
>  

[jira] [Updated] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala updated ATLAS-930:
---
Attachment: application.log.qs-fail-after-hive

Application log file when I reproduced the problem for steps reported in 
Description.

> QuickStart is failing when run after a specific sequence of operations
> --
>
> Key: ATLAS-930
> URL: https://issues.apache.org/jira/browse/ATLAS-930
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
> Attachments: application.log.qs-fail-after-hive
>
>
> I am seeing quick start fail with the same exception as in ATLAS-805. 
> However, I need a more complicated sequence of operations to reproduce the 
> problem. After many, many attempts, I am boiling this down to:
> * Create a hive table via the hive hook
> * Launch Atlas Admin UI
> * Create the default business taxonomy
> * Run a DSL query querying for hive_table
> * Select the table ingested in step 1
> * Run quick start.
> It fails with this exception:
> {code}
> Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata 
> service API CREATE_ENTITY failed with status 500(Internal Server Error) 
> Response Body ({"error":"Could not commit transaction due to exception during 
> persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could 
> not commit transaction due to exception during persistence\n\tat 
> com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
>  
> com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
>  
> org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
>  
> org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
>  
> org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
>  sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
>  
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
>  java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
>  
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
>  
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
>  
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
>  
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
>  javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
> com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
>  
> com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
>  
> com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
>  
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
>  org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat 
> com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
>  
> com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
>  

[jira] [Created] (ATLAS-930) QuickStart is failing when run after a specific sequence of operations

2016-06-21 Thread Hemanth Yamijala (JIRA)
Hemanth Yamijala created ATLAS-930:
--

 Summary: QuickStart is failing when run after a specific sequence 
of operations
 Key: ATLAS-930
 URL: https://issues.apache.org/jira/browse/ATLAS-930
 Project: Atlas
  Issue Type: Bug
Reporter: Hemanth Yamijala


I am seeing quick start fail with the same exception as in ATLAS-805. However, 
I need a more complicated sequence of operations to reproduce the problem. 
After many, many attempts, I am boiling this down to:

* Create a hive table via the hive hook
* Launch Atlas Admin UI
* Create the default business taxonomy
* Run a DSL query querying for hive_table
* Select the table ingested in step 1
* Run quick start.

It fails with this exception:
{code}
Exception in thread "main" org.apache.atlas.AtlasServiceException: Metadata 
service API CREATE_ENTITY failed with status 500(Internal Server Error) 
Response Body ({"error":"Could not commit transaction due to exception during 
persistence","stackTrace":"com.thinkaurelius.titan.core.TitanException: Could 
not commit transaction due to exception during persistence\n\tat 
com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx.commit(StandardTitanTx.java:1348)\n\tat
 
com.thinkaurelius.titan.graphdb.blueprints.TitanBlueprintsGraph.commit(TitanBlueprintsGraph.java:60)\n\tat
 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:43)\n\tat
 
org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:323)\n\tat
 
org.apache.atlas.services.DefaultMetadataService.createEntities(DefaultMetadataService.java:319)\n\tat
 
org.apache.atlas.web.resources.EntityResource.submit(EntityResource.java:125)\n\tat
 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat
 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat
 java.lang.reflect.Method.invoke(Method.java:606)\n\tat 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)\n\tat
 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)\n\tat
 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)\n\tat
 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)\n\tat
 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)\n\tat
 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)\n\tat
 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)\n\tat
 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)\n\tat
 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)\n\tat
 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)\n\tat
 javax.servlet.http.HttpServlet.service(HttpServlet.java:790)\n\tat 
com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:287)\n\tat
 
com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:277)\n\tat
 
com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:182)\n\tat
 
com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)\n\tat
 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)\n\tat
 org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:71)\n\tat 
com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)\n\tat
 
com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:119)\n\tat
 com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:133)\n\tat 
com.google.inject.servlet.GuiceFilter$1.call(GuiceFilter.java:130)\n\tat 
com.google.inject.servlet.GuiceFilter$Context.call(GuiceFilter.java:203)\n\tat 
com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:130)\n\tat 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)\n\tat
 

[jira] [Updated] (ATLAS-698) Remove Rexster Graph API

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-698:
--
Summary: Remove Rexster Graph API  (was: Remove Rexster Graph and Gremlin 
REST API)

> Remove Rexster Graph API
> 
>
> Key: ATLAS-698
> URL: https://issues.apache.org/jira/browse/ATLAS-698
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-698-v2.patch, ATLAS-698-v3.patch, ATLAS-698.patch
>
>
> Since these expose the internals of Atlas and are not intended for public 
> consumption, these should be removed:
> api/atlas/graph
> api/atlas/discovery/search/gremlin



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


[jira] [Updated] (ATLAS-822) Type updates - don't allow updating supertypes

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-822:
--
Summary: Type updates - don't allow updating supertypes  (was: Type updates 
- add supertypes)

> Type updates - don't allow updating supertypes
> --
>
> Key: ATLAS-822
> URL: https://issues.apache.org/jira/browse/ATLAS-822
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-822.patch
>
>
> In type updates, we allow adding super types. But set of super types is 
> maintained in every entity, and this type update will require updating all 
> the entities of that type which is not handled currently. We should either 
> update all entities or not allow updating super type information



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


Review Request 49022: ATLAS-822 Type updates - don't allow updating supertypes

2016-06-21 Thread Shwetha GS

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

Review request for atlas.


Bugs: ATLAS-822
https://issues.apache.org/jira/browse/ATLAS-822


Repository: atlas


Description
---

Type update will not allow modifying super types


Diffs
-

  addons/falcon-bridge/pom.xml f945a6c 
  addons/hdfs-model/pom.xml 80e74a2 
  addons/hive-bridge/pom.xml 24ab22f 
  addons/sqoop-bridge/pom.xml 5418885 
  addons/storm-bridge/pom.xml b51ab01 
  catalog/pom.xml 3817012 
  client/pom.xml a6b5a2f 
  notification/pom.xml f4cfdd3 
  pom.xml ecf76d0 
  repository/pom.xml 096a4b5 
  
repository/src/test/java/org/apache/atlas/repository/typestore/GraphBackedTypeStoreTest.java
 961442b 
  typesystem/pom.xml 219075b 
  
typesystem/src/main/java/org/apache/atlas/typesystem/types/HierarchicalType.java
 859ec72 
  
typesystem/src/test/java/org/apache/atlas/typesystem/types/HierarchicalTypeTest.java
 81da0be 
  webapp/pom.xml ce812c6 

Diff: https://reviews.apache.org/r/49022/diff/


Testing
---

UTs


Thanks,

Shwetha GS



[jira] [Updated] (ATLAS-822) Type updates - add supertypes

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-822:
--
Attachment: ATLAS-822.patch

Type update will not allow updating super types

> Type updates - add supertypes
> -
>
> Key: ATLAS-822
> URL: https://issues.apache.org/jira/browse/ATLAS-822
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-822.patch
>
>
> In type updates, we allow adding super types. But set of super types is 
> maintained in every entity, and this type update will require updating all 
> the entities of that type which is not handled currently. We should either 
> update all entities or not allow updating super type information



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


Build failed in Jenkins: apache-atlas-nightly #331

2016-06-21 Thread Apache Jenkins Server
See 

Changes:

[sshivalingamurthy] ATLAS-929 Add test for trait preservation on column rename 
for

--
[...truncated 6025 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ atlas-webapp 
---
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:clean (clean) @ atlas-webapp ---
[WARNING] Keystore file 
'
 doesn't exist.
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 56 Java sources to 

[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 56 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 41 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[jira] [Commented] (ATLAS-929) Add test for trait preservation on column rename for non-default database

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-929:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812139/ATLAS-929.patch
  against master revision 1c3b2be.

{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 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 382 new 
Findbugs (version 2.0.3) 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 :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/338//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/338//console

This message is automatically generated.

> Add test for trait preservation on column rename for non-default database
> -
>
> Key: ATLAS-929
> URL: https://issues.apache.org/jira/browse/ATLAS-929
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-929.patch
>
>
> The patch for ATLAS-752 had a bug where HiveHook assumes the table to reside 
> in the default database in Hive.
> Add a testcase to verify the fix for non-default database.



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


[jira] [Updated] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version

2016-06-21 Thread Kalyani Kashikar (JIRA)

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

Kalyani Kashikar updated ATLAS-927:
---
Attachment: ATLAS-927.1.patch

> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
> Attachments: ATLAS-927.1.patch
>
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded 
> version:
> {code}
> Version :  
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project 
> version



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


[jira] [Updated] (ATLAS-698) Remove Rexster Graph and Gremlin REST API

2016-06-21 Thread Vimal Sharma (JIRA)

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

Vimal Sharma updated ATLAS-698:
---
Attachment: ATLAS-698-v3.patch

> Remove Rexster Graph and Gremlin REST API
> -
>
> Key: ATLAS-698
> URL: https://issues.apache.org/jira/browse/ATLAS-698
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-698-v2.patch, ATLAS-698-v3.patch, ATLAS-698.patch
>
>
> Since these expose the internals of Atlas and are not intended for public 
> consumption, these should be removed:
> api/atlas/graph
> api/atlas/discovery/search/gremlin



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


[jira] [Commented] (ATLAS-698) Remove Rexster Graph and Gremlin REST API

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-698:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812133/ATLAS-698-v2.patch
  against master revision 1c3b2be.

{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 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 382 new 
Findbugs (version 2.0.3) 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 :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/337//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/337//console

This message is automatically generated.

> Remove Rexster Graph and Gremlin REST API
> -
>
> Key: ATLAS-698
> URL: https://issues.apache.org/jira/browse/ATLAS-698
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-698-v2.patch, ATLAS-698.patch
>
>
> Since these expose the internals of Atlas and are not intended for public 
> consumption, these should be removed:
> api/atlas/graph
> api/atlas/discovery/search/gremlin



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


Build failed in Jenkins: apache-atlas-nightly #330

2016-06-21 Thread Apache Jenkins Server
See 

Changes:

[sshivalingamurthy] ATLAS-925 Change master version to 0.8-incubating 
(shwethags)

--
[...truncated 6025 lines...]
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ atlas-webapp 
---
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:clean (clean) @ atlas-webapp ---
[WARNING] Keystore file 
'
 doesn't exist.
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 56 Java sources to 

[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 56 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 41 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[jira] [Resolved] (ATLAS-780) UI: Atlas UI shows an API response page after login sometimes

2016-06-21 Thread Nixon Rodrigues (JIRA)

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

Nixon Rodrigues resolved ATLAS-780.
---
Resolution: Fixed

This issue has been fixed in ATLAS-774.

> UI: Atlas UI shows an API response page after login sometimes
> -
>
> Key: ATLAS-780
> URL: https://issues.apache.org/jira/browse/ATLAS-780
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Priority: Minor
>
> I left the Atlas UI up for a while. After maybe an hour I came back and 
> performed some action on it. Possibly because of session expiry it took me 
> back to a login page and I logged in. Instead of taking me to the UI, this 
> showed the JSON response of an API. The URL displayed after login was 
> {{http://localhost:21000/api/atlas/types?type=TRAIT}}. This would probably be 
> a little confusing to the end user.



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


[jira] [Commented] (ATLAS-929) Add test for trait preservation on column rename for non-default database

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S commented on ATLAS-929:
---

+1. Thanks [~suma.shivaprasad] for finding the issue and giving the code fix

> Add test for trait preservation on column rename for non-default database
> -
>
> Key: ATLAS-929
> URL: https://issues.apache.org/jira/browse/ATLAS-929
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-929.patch
>
>
> The patch for ATLAS-752 had a bug where HiveHook assumes the table to reside 
> in the default database in Hive.
> Add a testcase to verify the fix for non-default database.



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


[jira] [Updated] (ATLAS-765) Need documentation for Authentication and Authorization features of Atlas

2016-06-21 Thread Nixon Rodrigues (JIRA)

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

Nixon Rodrigues updated ATLAS-765:
--
Attachment: ATLAS-765.patch

> Need documentation for Authentication and Authorization features of Atlas
> -
>
> Key: ATLAS-765
> URL: https://issues.apache.org/jira/browse/ATLAS-765
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Nixon Rodrigues
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-765.patch
>
>
> Since authentication and authorization are incompatible changes to Atlas 
> source, it will be very helpful to have detailed user documentation on how to 
> set this up using various user / policy stores. The sooner we have this, the 
> better it will be for the community.



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


Review Request 49016: ATLAS-765 - Documentation for Authentication and Authorization features of Atlas

2016-06-21 Thread Nixon Rodrigues

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

Review request for atlas, Madhan Neethiraj, Mehul Parikh, Shwetha GS, Suma 
Shivaprasad, and Hemanth Yamijala.


Bugs: ATLAS-765
https://issues.apache.org/jira/browse/ATLAS-765


Repository: atlas


Description
---

This patch provide documentation for Authentication and Authorization features 
of Atlas in twiki format.


Diffs
-

  docs/src/site/twiki/Authentication-Authorization.twiki PRE-CREATION 

Diff: https://reviews.apache.org/r/49016/diff/


Testing
---

Verified the html file created in docs/target/site directory after running mvn 
site.


Thanks,

Nixon Rodrigues



[jira] [Updated] (ATLAS-929) Add test for trait preservation on column rename for non-default database

2016-06-21 Thread Vimal Sharma (JIRA)

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

Vimal Sharma updated ATLAS-929:
---
Attachment: ATLAS-929.patch

> Add test for trait preservation on column rename for non-default database
> -
>
> Key: ATLAS-929
> URL: https://issues.apache.org/jira/browse/ATLAS-929
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Vimal Sharma
>Assignee: Vimal Sharma
> Attachments: ATLAS-929.patch
>
>
> The patch for ATLAS-752 had a bug where HiveHook assumes the table to reside 
> in the default database in Hive.
> Add a testcase to verify the fix for non-default database.



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


[jira] [Created] (ATLAS-929) Add test for trait preservation on column rename for non-default database

2016-06-21 Thread Vimal Sharma (JIRA)
Vimal Sharma created ATLAS-929:
--

 Summary: Add test for trait preservation on column rename for 
non-default database
 Key: ATLAS-929
 URL: https://issues.apache.org/jira/browse/ATLAS-929
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Vimal Sharma
Assignee: Vimal Sharma


The patch for ATLAS-752 had a bug where HiveHook assumes the table to reside in 
the default database in Hive.

Add a testcase to verify the fix for non-default database.



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


[jira] [Updated] (ATLAS-928) UI is not showing the name column for hive tables in the schema tab

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala updated ATLAS-928:
---
Fix Version/s: 0.7-incubating

> UI is not showing the name column for hive tables in the schema tab
> ---
>
> Key: ATLAS-928
> URL: https://issues.apache.org/jira/browse/ATLAS-928
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: hive_schema_response.json
>
>
> * Create a hive table from the hive hook.
> * Search for it in the UI, and select the schema tab
> * There is no name shown for the columns of the table (although all other 
> attributes like comment, data type are present).
> The same issue does not occur for quick_start Tables.
> The reason seems to be that the UI is using the attributeDefinitions element 
> in the return of the schema API to decide what columns to show. With 
> ATLAS-819, the name attribute was made a common attribute via a supertype for 
> assets like hive tables. The Schema API does not return the super type 
> attributes in the attributeDefinitions. Hence, even though the response of 
> the schema API contains the name attribute, because it is missing from the 
> attributeDefinitions, it is not picked up.



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


[jira] [Updated] (ATLAS-928) UI is not showing the name column for hive tables in the schema tab

2016-06-21 Thread Hemanth Yamijala (JIRA)

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

Hemanth Yamijala updated ATLAS-928:
---
Attachment: hive_schema_response.json

Attaching the hive_schema response that causes the issue.

> UI is not showing the name column for hive tables in the schema tab
> ---
>
> Key: ATLAS-928
> URL: https://issues.apache.org/jira/browse/ATLAS-928
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: hive_schema_response.json
>
>
> * Create a hive table from the hive hook.
> * Search for it in the UI, and select the schema tab
> * There is no name shown for the columns of the table (although all other 
> attributes like comment, data type are present).
> The same issue does not occur for quick_start Tables.
> The reason seems to be that the UI is using the attributeDefinitions element 
> in the return of the schema API to decide what columns to show. With 
> ATLAS-819, the name attribute was made a common attribute via a supertype for 
> assets like hive tables. The Schema API does not return the super type 
> attributes in the attributeDefinitions. Hence, even though the response of 
> the schema API contains the name attribute, because it is missing from the 
> attributeDefinitions, it is not picked up.



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


[jira] [Created] (ATLAS-928) UI is not showing the name column for hive tables in the schema tab

2016-06-21 Thread Hemanth Yamijala (JIRA)
Hemanth Yamijala created ATLAS-928:
--

 Summary: UI is not showing the name column for hive tables in the 
schema tab
 Key: ATLAS-928
 URL: https://issues.apache.org/jira/browse/ATLAS-928
 Project: Atlas
  Issue Type: Bug
Reporter: Hemanth Yamijala
Priority: Critical


* Create a hive table from the hive hook.
* Search for it in the UI, and select the schema tab
* There is no name shown for the columns of the table (although all other 
attributes like comment, data type are present).

The same issue does not occur for quick_start Tables.

The reason seems to be that the UI is using the attributeDefinitions element in 
the return of the schema API to decide what columns to show. With ATLAS-819, 
the name attribute was made a common attribute via a supertype for assets like 
hive tables. The Schema API does not return the super type attributes in the 
attributeDefinitions. Hence, even though the response of the schema API 
contains the name attribute, because it is missing from the 
attributeDefinitions, it is not picked up.



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


[jira] [Updated] (ATLAS-698) Remove Rexster Graph and Gremlin REST API

2016-06-21 Thread Vimal Sharma (JIRA)

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

Vimal Sharma updated ATLAS-698:
---
Attachment: ATLAS-698-v2.patch

> Remove Rexster Graph and Gremlin REST API
> -
>
> Key: ATLAS-698
> URL: https://issues.apache.org/jira/browse/ATLAS-698
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-698-v2.patch, ATLAS-698.patch
>
>
> Since these expose the internals of Atlas and are not intended for public 
> consumption, these should be removed:
> api/atlas/graph
> api/atlas/discovery/search/gremlin



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


[jira] [Updated] (ATLAS-925) Change master version to 0.8-incubating

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-925:
--
Fix Version/s: 0.8-incubating

> Change master version to 0.8-incubating
> ---
>
> Key: ATLAS-925
> URL: https://issues.apache.org/jira/browse/ATLAS-925
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-925-v2.patch, ATLAS-925.patch
>
>




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


[jira] [Commented] (ATLAS-925) Change master version to 0.8-incubating

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-925:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812097/ATLAS-925-v2.patch
  against master revision 7b3ace5.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 382 new 
Findbugs (version 2.0.3) 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 :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/336//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/336//console

This message is automatically generated.

> Change master version to 0.8-incubating
> ---
>
> Key: ATLAS-925
> URL: https://issues.apache.org/jira/browse/ATLAS-925
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Attachments: ATLAS-925-v2.patch, ATLAS-925.patch
>
>




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


[jira] [Commented] (ATLAS-925) Change master version to 0.8-incubating

2016-06-21 Thread Vimal Sharma (JIRA)

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

Vimal Sharma commented on ATLAS-925:


+1

> Change master version to 0.8-incubating
> ---
>
> Key: ATLAS-925
> URL: https://issues.apache.org/jira/browse/ATLAS-925
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-925-v2.patch, ATLAS-925.patch
>
>




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


Re: Atlas and sqoop hook

2016-06-21 Thread Shwetha Shivalingamurthy
Make sure you have latest sqoop, built from sqoop trunk.

Use ‹verbose in sqoop command to get debug logs. From the logs, you can
verify if sqoop atlas hook is invoked. Also make sure that the sqoop hook
picks the right atlas conf

Regards,
Shwetha






On 20/06/16, 11:58 PM, "Margus Roo"  wrote:

>Hi
>
>Downloaded and compiled atlas 0.7.
>Hive hook is working - create table [tablename] as select * from [src
>tablename] is working and data lineage is generated in atlas.
>Next I tried sqoop hook and followed
>http://atlas.incubator.apache.org/Bridge-Sqoop.html
>
>Command:
>sqoop-import --connect jdbc:mysql://mysqlhost/test --table sqoop_test
>--split-by id --hive-import -hive-table sqoop_test19 --username margusja
>--P
>creates a new table in Hive and new table is in atlas also but no data
>lineage
>
>I see from 
>http://hortonworks.com/hadoop-tutorial/cross-component-lineage-apache-atla
>s/
>There I can see that extra config parameters are loaded (in picture
>https://raw.githubusercontent.com/hortonworks/tutorials/atlas-ranger-tp/as
>sets/cross-component-lineage-with-atlas/8-sqoop-import-finish.png)
>and kafka producer creating ouutput but in my command:
>sqoop-import --connect jdbc:mysql://mysqlhost/test --table sqoop_test
>--split-by id --hive-import -hive-table sqoop_test19 --username margusja
>--P
>there is no extra output only:
>
>Warning: /usr/hdp/2.4.0.0-169/accumulo does not exist! Accumulo imports
>will fail.
>Please set $ACCUMULO_HOME to the root of your Accumulo installation.
>16/06/20 21:25:47 INFO sqoop.Sqoop: Running Sqoop version:
>1.4.6.2.4.0.0-169
>16/06/20 21:25:47 WARN tool.BaseSqoopTool: Setting your password on the
>command-line is insecure. Consider using -P instead.
>16/06/20 21:25:47 INFO tool.BaseSqoopTool: Using Hive-specific
>delimiters for output. You can override
>16/06/20 21:25:47 INFO tool.BaseSqoopTool: delimiters with
>--fields-terminated-by, etc.
>16/06/20 21:25:47 INFO manager.MySQLManager: Preparing to use a MySQL
>streaming resultset.
>16/06/20 21:25:47 INFO tool.CodeGenTool: Beginning code generation
>16/06/20 21:25:47 INFO manager.SqlManager: Executing SQL statement:
>SELECT t.* FROM `sqoop_test` AS t LIMIT 1
>16/06/20 21:25:47 INFO manager.SqlManager: Executing SQL statement:
>SELECT t.* FROM `sqoop_test` AS t LIMIT 1
>16/06/20 21:25:47 INFO orm.CompilationManager: HADOOP_MAPRED_HOME is
>/usr/hdp/2.4.0.0-169/hadoop-mapreduce
>Note: 
>/tmp/sqoop-root/compile/49b525e14ebd68542d86b68dc399bd84/sqoop_test.java
>uses or overrides a deprecated API.
>Note: Recompile with -Xlint:deprecation for details.
>16/06/20 21:25:48 INFO orm.CompilationManager: Writing jar file:
>/tmp/sqoop-root/compile/49b525e14ebd68542d86b68dc399bd84/sqoop_test.jar
>16/06/20 21:25:48 WARN manager.MySQLManager: It looks like you are
>importing from mysql.
>16/06/20 21:25:48 WARN manager.MySQLManager: This transfer can be
>faster! Use the --direct
>16/06/20 21:25:48 WARN manager.MySQLManager: option to exercise a
>MySQL-specific fast path.
>16/06/20 21:25:48 INFO manager.MySQLManager: Setting zero DATETIME
>behavior to convertToNull (mysql)
>16/06/20 21:25:48 INFO mapreduce.ImportJobBase: Beginning import of
>sqoop_test
>SLF4J: Class path contains multiple SLF4J bindings.
>SLF4J: Found binding in
>[jar:file:/usr/hdp/2.4.0.0-169/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/sl
>f4j/impl/StaticLoggerBinder.class]
>SLF4J: Found binding in
>[jar:file:/usr/hdp/2.4.0.0-169/zookeeper/lib/slf4j-log4j12-1.6.1.jar!/org/
>slf4j/impl/StaticLoggerBinder.class]
>SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
>explanation.
>SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
>16/06/20 21:25:50 INFO impl.TimelineClientImpl: Timeline service
>address: http://bigdata21.webmedia.int:8188/ws/v1/timeline/
>16/06/20 21:25:50 INFO client.RMProxy: Connecting to ResourceManager at
>bigdata21.webmedia.int/192.168.81.110:8050
>16/06/20 21:25:52 INFO db.DBInputFormat: Using read commited transaction
>isolation
>16/06/20 21:25:52 INFO db.DataDrivenDBInputFormat: BoundingValsQuery:
>SELECT MIN(`id`), MAX(`id`) FROM `sqoop_test`
>16/06/20 21:25:52 INFO mapreduce.JobSubmitter: number of splits:2
>16/06/20 21:25:52 INFO mapreduce.JobSubmitter: Submitting tokens for
>job: job_1460979043517_0118
>16/06/20 21:25:53 INFO impl.YarnClientImpl: Submitted application
>application_1460979043517_0118
>16/06/20 21:25:53 INFO mapreduce.Job: The url to track the job:
>http://bigdata21.webmedia.int:8088/proxy/application_1460979043517_0118/
>16/06/20 21:25:53 INFO mapreduce.Job: Running job: job_1460979043517_0118
>16/06/20 21:25:58 INFO mapreduce.Job: Job job_1460979043517_0118 running
>in uber mode : false
>16/06/20 21:25:58 INFO mapreduce.Job:  map 0% reduce 0%
>16/06/20 21:26:02 INFO mapreduce.Job:  map 50% reduce 0%
>16/06/20 21:26:03 INFO mapreduce.Job:  map 100% reduce 0%
>16/06/20 21:26:03 INFO mapreduce.Job: Job job_1460979043517_0118
>completed successfully
>16/06/20 21:26:03 INFO 

[jira] [Commented] (ATLAS-926) Change version in 0.7 branch to 0.7-incubating

2016-06-21 Thread ATLAS QA (JIRA)

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

ATLAS QA commented on ATLAS-926:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12812098/ATLAS-926.patch
  against master revision 7b3ace5.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

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

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 382 new 
Findbugs (version 2.0.3) 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 :
   
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/335//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/335//console

This message is automatically generated.

> Change version in 0.7 branch to 0.7-incubating
> --
>
> Key: ATLAS-926
> URL: https://issues.apache.org/jira/browse/ATLAS-926
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-926.patch
>
>




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


Build failed in Jenkins: apache-atlas-nightly #329

2016-06-21 Thread Apache Jenkins Server
See 

Changes:

[hyamijala] ATLAS-922 remove test atlas-application.properties embedded in

--
[...truncated 2466 lines...]
:243:
 Line matches the illegal pattern 'Trailing whitespace'.
:248:
 Line matches the illegal pattern 'Trailing whitespace'.
:28:
 Line matches the illegal pattern 'Trailing whitespace'.
:33:
 First sentence should end with a period.
:45:
 First sentence should end with a period.
:47:
 Line matches the illegal pattern 'Trailing whitespace'.
:52:
 Line matches the illegal pattern 'Trailing whitespace'.
:60:
 Line matches the illegal pattern 'Trailing whitespace'.
:64:
 Line matches the illegal pattern 'Trailing whitespace'.
:65:
 Line matches the illegal pattern 'Trailing whitespace'.
:66:
 Line matches the illegal pattern 'Trailing whitespace'.
:67:
 First sentence should end with a period.
:70:
 Line is longer than 120 characters.
:72:
 Line matches the illegal pattern 'Trailing whitespace'.
:73:
 Line matches the illegal pattern 'Trailing whitespace'.
:25:
 Line matches the illegal pattern 'Trailing whitespace'.
:29:36:
 ',' is not followed by whitespace.
:33:
 Line matches the illegal pattern 'Trailing whitespace'.
:36:23:
 ',' is not followed by whitespace.
:38:
 Line matches the illegal pattern 'Trailing whitespace'.
:40:
 Line matches the illegal pattern 'Trailing whitespace'.
:44:31:
 ',' is not followed by whitespace.
:45:
 Line matches the illegal pattern 'Trailing whitespace'.
:46:
 First sentence should end with a period.

[jira] [Updated] (ATLAS-584) Integrate CSRF prevention filter

2016-06-21 Thread Kalyani Kashikar (JIRA)

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

Kalyani Kashikar updated ATLAS-584:
---
Assignee: Saqeeb Shaikh

> Integrate CSRF prevention filter
> 
>
> Key: ATLAS-584
> URL: https://issues.apache.org/jira/browse/ATLAS-584
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Saqeeb Shaikh
>Priority: Blocker
> Fix For: 0.7-incubating
>
>
> Atlas needs to provide protection for CSRF protection.



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


Re: Review Request 49002: ATLAS-922: remove embedded atlas-application.properties

2016-06-21 Thread Hemanth Yamijala

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


Ship it!




Ship It!

- Hemanth Yamijala


On June 21, 2016, 6:20 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/49002/
> ---
> 
> (Updated June 21, 2016, 6:20 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-922
> https://issues.apache.org/jira/browse/ATLAS-922
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> remove embedded atlas-application.properties
> 
> 
> Diffs
> -
> 
>   addons/falcon-bridge/pom.xml 14c6090 
>   addons/hdfs-model/pom.xml f4033bc 
>   addons/hive-bridge/pom.xml dff93a9 
>   addons/sqoop-bridge/pom.xml 343bb4e 
>   addons/storm-bridge/pom.xml b1a7a9b 
>   catalog/pom.xml 8a49d3d 
>   client/pom.xml 69b8731 
>   common/src/main/java/org/apache/atlas/ApplicationProperties.java 48cb7a6 
>   notification/pom.xml fc08115 
>   pom.xml 1539922 
>   repository/pom.xml 533e48b 
>   typesystem/pom.xml c1f3fcd 
>   typesystem/src/main/resources/atlas-application.properties 2bbcdcd 
>   typesystem/src/test/resources/atlas-application.properties ba66ae5 
>   webapp/pom.xml e17f64d 
> 
> Diff: https://reviews.apache.org/r/49002/diff/
> 
> 
> Testing
> ---
> 
> Verified that atlas-application.properties is not embedded in 
> atlas-typesystem.jar and the application/hooks load 
> atlas-application.properties from application's conf directory (in the 
> CLASSPATH) - irrespective of where atlas jars appear in the CLASSPATH.
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>



[jira] [Updated] (ATLAS-499) Automatically update inverse references to prevent repository corruption

2016-06-21 Thread Shwetha G S (JIRA)

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

Shwetha G S updated ATLAS-499:
--
Fix Version/s: (was: 0.7-incubating)

> Automatically update inverse references to prevent repository corruption
> 
>
> Key: ATLAS-499
> URL: https://issues.apache.org/jira/browse/ATLAS-499
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: David Kantor
>
> For references that are defined in the type system as bi-directional, Atlas 
> does not enforce that clients update both sides of the reference, and relies 
> on well behaved client applications for repository consistency.   This allows 
> the repository to be easily corrupted with unbalanced references.  Atlas 
> should automatically update the inverse reference to avoid this corruption.



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


[jira] [Updated] (ATLAS-927) aboutAtlas_tmpl.html has hard-coded project version

2016-06-21 Thread Kalyani Kashikar (JIRA)

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

Kalyani Kashikar updated ATLAS-927:
---
Assignee: Kalyani Kashikar  (was: Keval Bhatt)

> aboutAtlas_tmpl.html has hard-coded project version
> ---
>
> Key: ATLAS-927
> URL: https://issues.apache.org/jira/browse/ATLAS-927
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Kalyani Kashikar
>
> dashboardv2/public/js/templates/common/aboutAtlas_tmpl.html has hard coded 
> version:
> {code}
> Version :  
> 0.7-incubating-SNAPSHOT-ra2cc01c4342ace7f7a3e3e254d7ede781f990318
> {code}
> Instead, it should use mvn resource filtering to set the version to project 
> version



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


Build failed in Jenkins: apache-atlas-nightly #328

2016-06-21 Thread Apache Jenkins Server
See 

Changes:

[sshivalingamurthy] ATLAS-819 All user defined types should have a set of 
common attributes

[sshivalingamurthy] ATLAS-844 Remove titan berkeley and elastic search jars if 
hbase/solr

--
[...truncated 5978 lines...]
[WARNING] Cannot get the branch information from the git repository: 
Detecting the current branch failed: fatal: ref HEAD is not a symbolic ref

[INFO] Executing: /bin/sh -c cd 
' && 'git' 
'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: UNKNOWN
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ atlas-webapp 
---
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:clean (clean) @ atlas-webapp ---
[WARNING] Keystore file 
'
 doesn't exist.
[INFO] 
[INFO] --- keytool-maven-plugin:1.5:generateKeyPair (generateKeyPair) @ 
atlas-webapp ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 56 Java sources to 

[WARNING] Note: Some input files use or override a deprecated API.
[WARNING] Note: Recompile with -Xlint:deprecation for details.
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ atlas-webapp 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 56 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-webapp ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-webapp ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 41 Java sources to 

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 41 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

  1   2   >