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

[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:
--
Attachment: ATLAS-925.patch

> 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.patch
>
>




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

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

[Shwetha G S (JIRA)]

Shwetha G S created ATLAS-925:
-

 Summary: 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






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

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

[Shwetha G S (JIRA)]

Shwetha G S created ATLAS-926:
-

 Summary: 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






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

[jira] [Created] (ATLAS-924) Release 0.7-incubating

[Shwetha G S (JIRA)]

Shwetha G S created ATLAS-924:
-

 Summary: Release 0.7-incubating
 Key: ATLAS-924
 URL: https://issues.apache.org/jira/browse/ATLAS-924
 Project: Atlas
  Issue Type: Task
Reporter: Shwetha G S
 Fix For: 0.7-incubating






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

Re: Review Request 48945: ATLAs-819 All user defined types should have a set of common attributes

[Shwetha GS]

> On June 20, 2016, 7:35 p.m., David Kantor wrote:
> > webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java, 
> > line 124
> > 
> >
> > Why has the log level has been changed to INFO in several places 
> > throught EntityResource?  I would think that in a production Atlas 
> > environment this would generate a lot of log noise.  Shouldn't these remain 
> > at DEBUG?

I also changed info logs in GraphBackedMetadataRepository to debug. At the 
least, we should have API inputs and outputs, else we can't figure out whats 
happening. If these logs are not relevant for you, you can change the log level 
to warn in atlas-log4j.xml, anyway its configurable

We also need a way of refreshing log levels at runtime so that we can enable 
debug logs whenever required


- Shwetha


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


On June 20, 2016, 12:01 p.m., Shwetha GS wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48945/
> ---
> 
> (Updated June 20, 2016, 12:01 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-819
> https://issues.apache.org/jira/browse/ATLAS-819
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Added  base type with the attributes name, owner and description that any 
> type can extend and the users can set these attributes.
> 
> 
> Diffs
> -
> 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/Util/EventUtil.java
>  c1ccd05 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/bridge/FalconBridge.java
>  1621d95 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/event/FalconEvent.java
>  37df6da 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java
>  95f255e 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
>  81cd5e0 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/service/AtlasService.java
>  c92bd43 
>   
> addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
>  8a5736a 
>   
> addons/hdfs-model/src/main/scala/org/apache/atlas/fs/model/FSDataModel.scala 
> cf81406 
>   
> 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/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
>  3686fa8 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> 5a175e7 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
> 9db8180 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/model/SqoopDataModelGenerator.java
>  c3bdbfa 
>   
> addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
>  b2171c2 
>   
> addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
>  bae4c1a 
>   client/src/main/java/org/apache/atlas/AtlasClient.java 4c88da9 
>   distro/src/conf/atlas-log4j.xml e14afa3 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
>  dd7dd74 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  c385df3 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  d9e6cb9 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/StructTypeDefinition.java
>  9dc93ae 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 0713d30 
>   webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java 
> 74d89ce 
> 
> Diff: https://reviews.apache.org/r/48945/diff/
> 
> 
> Testing
> ---
> 
> UTs
> 
> 
> Thanks,
> 
> Shwetha GS
> 
>

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

[Madhan Neethiraj]

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

(Updated June 21, 2016, 5:40 a.m.)


Review request for atlas.


Changes
---

Fix for IT failure in webapp - atlas.conf path was incorrect


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


Repository: atlas


Description
---

remove embedded atlas-application.properties


Diffs (updated)
-

  addons/hdfs-model/pom.xml f4033bc 
  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 bc62f87 

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] [Created] (ATLAS-923) Hive hook: hive_table.description should be set to table comments

[Shwetha G S (JIRA)]

Shwetha G S created ATLAS-923:
-

 Summary: Hive hook: hive_table.description should be set to table 
comments
 Key: ATLAS-923
 URL: https://issues.apache.org/jira/browse/ATLAS-923
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
Assignee: Shwetha G S


ATLAS-819 added description attribute to hive_table. But description is not 
set, it can be set to table comment



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

[jira] [Commented] (ATLAS-819) All user defined types should have a set of common attributes

[Shwetha G S (JIRA)]

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

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

Yes, the plan is to return system attributes as well. But since they can't be 
modified, they won't be part of type system. We will return createTime, 
lastModifiedTime, createdUser and modifiedUser in get entity definition along 
with id and state. It will be handled in ATLAS-916

> All user defined types should have a set of common attributes
> -
>
> Key: ATLAS-819
> URL: https://issues.apache.org/jira/browse/ATLAS-819
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-819-v2.patch, ATLAS-819.patch
>
>
> It would be very convenient if all user defined types have a conventional set 
> of common attributes including:
> * name
> * description
> * owner
> * created at
> * modified at



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

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

[Madhan Neethiraj (JIRA)]

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

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

Patch in review board at https://reviews.apache.org/r/49002/

> 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
> 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] [Resolved] (ATLAS-921) Processing encryption ... hangs

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-921.

Resolution: Invalid

This seems to be an issue in the cloudstack project and not the Apache Atlas 
project. I don't have permission to move the issue - please file a new one in 
the right project.

> 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] [Created] (ATLAS-922) remove test atlas-application.properties embedded in atlas-typesystem.jar

[Madhan Neethiraj (JIRA)]

Madhan Neethiraj created ATLAS-922:
--

 Summary: 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


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-921) Processing encryption ... hangs

[Oscar Segarra (JIRA)]

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

Oscar Segarra commented on ATLAS-921:
-

Hi, 

I can run 
[root@vdiccs01 ~]# cloudstack-setup-databases 
And system hangs when arrives to Processing encryption

I attach the output of the setup-encryption.

[root@vdiccs01 ~]# cloudstack-setup-encryption -v
Preparing /etc/cloudstack/management/db.properties  
[ OK ]
Processing encryption ...   
^CTraceback (most recent call last):
  File "/usr/bin/cloudstack-setup-encryption", line 274, in 
o.run()
  File "/usr/bin/cloudstack-setup-encryption", line 263, in run
self.processEncryptionStuff()
  File "/usr/bin/cloudstack-setup-encryption", line 219, in 
processEncryptionStuff
encryptKeyStorePassphrase()
  File "/usr/bin/cloudstack-setup-encryption", line 202, in 
encryptKeyStorePassphrase
self.putDbProperty('db.cloud.keyStorePassphrase', 
formatEncryptResult(encrypt(self.keyStorePassphrase)))
  File "/usr/bin/cloudstack-setup-encryption", line 189, in encrypt
return runCmd(cmd).strip('\n')
  File "/usr/bin/cloudstack-setup-encryption", line 49, in runCmd
stdout, stderr = process.communicate()
  File "/usr/lib64/python2.7/subprocess.py", line 800, in communicate
return self._communicate(input)
  File "/usr/lib64/python2.7/subprocess.py", line 1401, in _communicate
stdout, stderr = self._communicate_with_poll(input)
  File "/usr/lib64/python2.7/subprocess.py", line 1455, in 
_communicate_with_poll
ready = poller.poll()
KeyboardInterrupt
[root@vdiccs01 ~]#

It is blocking for me because i cannot continue with the installation.

Thanks a lot,

> 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] [Created] (ATLAS-921) Processing encryption ... hangs

[Oscar Segarra (JIRA)]

Oscar Segarra created ATLAS-921:
---

 Summary: 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] [Updated] (ATLAS-920) Lineage graph is broken when there are multiple paths from same source table

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-920:
---
Attachment: Screen Shot 2016-06-20 at 4.49.24 PM.png

> 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
> Fix For: 0.7-incubating
>
> 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-920) Lineage graph is broken when there are multiple paths from same source table

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-920:
---
Attachment: Screen Shot 2016-06-20 at 4.31.58 PM.png

Steps to reproduce:

0. 
hadoop dfs -mkdir  /hive_tables/test_path2
hadoop dfs -mkdir  /hive_tables/test_path1
1. CREATE TABLE test_export_table4 ( name string )
2.EXPORT TABLE test_export_table4 to 
'hdfs://localhost:9000/hive_tables/test_path2'
3. CREATE EXTERNAL TABLE test_import_table ( name string) location 
'hdfs://localhost:9000/test_import_path'
4. IMPORT TABLE test_import_table from 
'hdfs://localhost:9000/hive_tables/test_path1'
5. IMPORT TABLE test_import_table from 
'hdfs://localhost:9000/hive_tables/test_path2'

> 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
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-20 at 4.09.02 PM.png, Screen Shot 
> 2016-06-20 at 4.31.58 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] [Commented] (ATLAS-920) Lineage graph is broken when there are multiple paths from same source table

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-920:


Similiar issue with screenshot

> 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
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-20 at 4.09.02 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] [Comment Edited] (ATLAS-920) Lineage graph is broken when there are multiple paths from same source table

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad edited comment on ATLAS-920 at 6/20/16 11:23 PM:
--

It might be worth taking a look at ATLAS-405 which seems to address a similiar 
issue but with old UI


was (Author: suma.shivaprasad):
It might be worth taking a look at ATLAS-405 which seems to address a similiar 
issue

> 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
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-20 at 4.09.02 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] [Commented] (ATLAS-920) Lineage graph is broken when there are multiple paths from same source table

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-920:


It might be worth taking a look at ATLAS-405 which seems to address a similiar 
issue

> 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
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-20 at 4.09.02 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] [Commented] (ATLAS-920) Lineage graph is broken when there are multiple paths from same source table

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-920:


cc [~madhan.neethiraj]

> 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
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-20 at 4.09.02 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-920) Lineage graph is broken when there are multiple paths from same source table

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-920:
---
Summary: Lineage graph is broken when there are multiple paths from same 
source table  (was: Lineage graph is broken during alter view)

> 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
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-20 at 4.09.02 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] [Created] (ATLAS-920) Lineage graph is broken during alter view

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-920:
--

 Summary: Lineage graph is broken during alter view
 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
 Fix For: 0.7-incubating
 Attachments: Screen Shot 2016-06-20 at 4.09.02 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-920) Lineage graph is broken during alter view

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-920:
---
Attachment: Screen Shot 2016-06-20 at 4.09.02 PM.png

> Lineage graph is broken during alter view
> -
>
> 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
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-20 at 4.09.02 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-919) UI : Deleted references should be filtered out

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-919:
---
Attachment: Screen Shot 2016-06-20 at 3.56.33 PM.png

Refer screenshot which shows that the column is shown as a normal column 
instead of being filtered out

> UI : Deleted references should be filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json, Screen Shot 
> 2016-06-20 at 3.56.33 PM.png
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. The way to identify this is to check if the entity 
> state is DELETED when going through the references.



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

[jira] [Updated] (ATLAS-919) UI : Deleted references should be filtered out

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-919:
---
Description: Foe eg: In a hive_table one of the columns could be dropped in 
which case the columns array will have the deleted column as well. This could 
be completely filtered out in the UI. The way to identify this is to check if 
the entity state is DELETED when going through the references.  (was: Foe eg: 
In a hive_table one of the columns could be dropped in which case the columns 
array will have the deleted column as well. This could be completely filtered 
out in the UI. the way to identify this is to check if the entity status is 
DELETED when going through the references.)

> UI : Deleted references should be filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. The way to identify this is to check if the entity 
> state is DELETED when going through the references.



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

[jira] [Updated] (ATLAS-919) UI : Deleted references should be filtered out

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-919:
---
Description: Foe eg: In a hive_table one of the columns could be dropped in 
which case the columns array will have the deleted column as well. This could 
be completely filtered out in the UI. the way to identify this is to check if 
the entity status is DELETED when going through the references.  (was: Foe eg: 
In a hive_table one of the columns could be dropped in which case the columns 
array will have the deleted column as well. This could be shown in red color or 
completely filtered out in the UI. the way to identify this is to check if the 
entity status is DELETED when going through the references.)

> UI : Deleted references should be filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be completely 
> filtered out in the UI. the way to identify this is to check if the entity 
> status is DELETED when going through the references.



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

[jira] [Commented] (ATLAS-919) UI : Deleted references should be filtered out

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-919:


[~kevalbhatt18] In general, if the state=DELETED for any of the referenced 
entities , filter that out in UI as well. 

> UI : Deleted references should be filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be shown in 
> red color or completely filtered out in the UI. the way to identify this is 
> to check if the entity status is DELETED when going through the references.



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

[jira] [Updated] (ATLAS-919) UI : Deleted references should be filtered out

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-919:
---
Summary: UI : Deleted references should be filtered out  (was: UI : Deleted 
references should be shown in red color or filtered out)

> UI : Deleted references should be filtered out
> --
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be shown in 
> red color or completely filtered out in the UI. the way to identify this is 
> to check if the entity status is DELETED when going through the references.



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

[jira] [Comment Edited] (ATLAS-919) UI : Deleted references should be shown in red color or filtered out

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad edited comment on ATLAS-919 at 6/20/16 10:52 PM:
--

Attaching sample json . Refer column abc in json which has state =DELETED

{
jsonClass: "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
id: {
jsonClass: "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
id: "371b07b0-1a49-4491-9af6-953b376699e8",
version: 0,
typeName: "hive_column",
state: "DELETED"
},
typeName: "hive_column",
values: {
name: "abc",
qualifiedName: "testdb1.test_table.abc@primary",
comment: null,
type: "string",
table: {
jsonClass: "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
id: "91529261-d568-40ee-9b2e-b488cff61de1",
version: 0,
typeName: "hive_table",
state: "ACTIVE"
}
},
traitNames: [ ],
traits: { }
}
],


was (Author: suma.shivaprasad):
Attaching sample json 

> UI : Deleted references should be shown in red color or filtered out
> 
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.7-incubating
>
> Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be shown in 
> red color or completely filtered out in the UI. the way to identify this is 
> to check if the entity status is DELETED when going through the references.



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

[jira] [Commented] (ATLAS-919) UI : Deleted references should be shown in red color or filtered out

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-919:


Attaching sample json 

> UI : Deleted references should be shown in red color or filtered out
> 
>
> Key: ATLAS-919
> URL: https://issues.apache.org/jira/browse/ATLAS-919
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Fix For: 0.7-incubating
>
>
> Foe eg: In a hive_table one of the columns could be dropped in which case the 
> columns array will have the deleted column as well. This could be shown in 
> red color or completely filtered out in the UI. the way to identify this is 
> to check if the entity status is DELETED when going through the references.



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

[jira] [Created] (ATLAS-919) UI : Deleted references should be shown in red color or filtered out

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-919:
--

 Summary: UI : Deleted references should be shown in red color or 
filtered out
 Key: ATLAS-919
 URL: https://issues.apache.org/jira/browse/ATLAS-919
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Suma Shivaprasad
Assignee: Keval Bhatt
Priority: Critical
 Fix For: 0.7-incubating


Foe eg: In a hive_table one of the columns could be dropped in which case the 
columns array will have the deleted column as well. This could be shown in red 
color or completely filtered out in the UI. the way to identify this is to 
check if the entity status is DELETED when going through the references.



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

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

[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

Attached latest review board 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: 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

[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: 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)

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

[David Kantor]

---
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 (updated)
---

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

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

[David Kantor]

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

(Updated June 20, 2016, 9:55 p.m.)


Review request for atlas.


Changes
---

* Renamed ITypeCacheProvider to TypeCache, along with associated class and 
properties.  TypeCache is *not* a Guice provider so it was misleading/incorrect 
to name the class as a provider.
* Configure Guice to instantiate TypeCache implementation - removed TypeCache 
instantiation code from TypeSystem.
* Added test cases to verify StoreBackedTypeCache can be successfully 
instantiated and injected by Guice using Atlas properties file.
* Addressed Shwetha's review comments.


Summary (updated)
-

ATLAS-856: lazy-load type cache


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


Repository: atlas


Description
---

ATLAS-856: An extension of DefaultTypeCacheProvider 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)
-

  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] [Commented] (ATLAS-698) Remove Rexster Graph and Gremlin REST API

[ATLAS QA (JIRA)]

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

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/12811818/ATLAS-698.patch
  against master revision f4670dd.

{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.audit.HBaseBasedAuditRepositoryTest
./repository/target/surefire-reports/junitreports/TEST-org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/331//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/331//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.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-918) UI : Deleted entities show status as DELETED and Datasets should be differentiable in lineage

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-918:
---
Attachment: Screen Shot 2016-06-20 at 2.20.32 PM.png

> UI : Deleted entities show status as DELETED and Datasets should be 
> differentiable in lineage
> -
>
> Key: ATLAS-918
> URL: https://issues.apache.org/jira/browse/ATLAS-918
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: Screen Shot 2016-06-20 at 2.20.32 PM.png
>
>
> Keval,
> This jira is to track showing deleted entities with a diff color in lineage. 
> Is there anything missing in the lineage API to implement this? We need to 
> take care of this since no one looks at lineage via a process and will be 
> mostly looking at lineage from a table or  a dataset. Also a table can be 
> dropped and recreated in hive, leading to linage showing as attached in 
> screen shot
> Also can we show the property (status)__status for deleted entities  as 
> "DELETED" . We could display that in "properties" section.



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

[jira] [Commented] (ATLAS-918) UI : Deleted entities show status as DELETED and Datasets should be differentiable in lineage

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-918:


cc [~madhan.neethiraj]

> UI : Deleted entities show status as DELETED and Datasets should be 
> differentiable in lineage
> -
>
> Key: ATLAS-918
> URL: https://issues.apache.org/jira/browse/ATLAS-918
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: Screen Shot 2016-06-20 at 2.20.32 PM.png
>
>
> Keval,
> This jira is to track showing deleted entities with a diff color in lineage. 
> Is there anything missing in the lineage API to implement this? We need to 
> take care of this since no one looks at lineage via a process and will be 
> mostly looking at lineage from a table or  a dataset. Also a table can be 
> dropped and recreated in hive, leading to linage showing as attached in 
> screen shot
> Also can we show the property (status)__status for deleted entities  as 
> "DELETED" . We could display that in "properties" section.



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

[jira] [Updated] (ATLAS-918) UI : Deleted entities show status as DELETED and Datasets should be differentiable in lineage

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-918:
---
Summary: UI : Deleted entities show status as DELETED and Datasets should 
be differentiable in lineage  (was: UI : Deleted entities show status as 
DELETED and should be differentiable in lineage)

> UI : Deleted entities show status as DELETED and Datasets should be 
> differentiable in lineage
> -
>
> Key: ATLAS-918
> URL: https://issues.apache.org/jira/browse/ATLAS-918
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
>
> Keval,
> This jira is to track showing deleted entities with a diff color in lineage. 
> Is there anything missing in the lineage API to implement this? We need to 
> take care of this since no none looks at lineage via a process and will be 
> mostly looking at lineage from a table
> Also can we show the property (status)__status for deleted entities  as 
> "DELETED" . We could display that in "properties" section.



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

[jira] [Updated] (ATLAS-918) UI : Deleted entities show status as DELETED and should be differentiable in lineage

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-918:
---
Priority: Critical  (was: Major)

> UI : Deleted entities show status as DELETED and should be differentiable in 
> lineage
> 
>
> Key: ATLAS-918
> URL: https://issues.apache.org/jira/browse/ATLAS-918
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Critical
>
> Keval,
> This jira is to track showing deleted entities with a diff color in lineage. 
> Is there anything missing in the lineage API to implement this? We need to 
> take care of this since no none looks at lineage via a process and will be 
> mostly looking at lineage from a table
> Also can we show the property (status)__status for deleted entities  as 
> "DELETED" . We could display that in "properties" section.



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

[jira] [Created] (ATLAS-918) UI : Deleted entities show status as DELETED and should be differentiable in lineage

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-918:
--

 Summary: UI : Deleted entities show status as DELETED and should 
be differentiable in lineage
 Key: ATLAS-918
 URL: https://issues.apache.org/jira/browse/ATLAS-918
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Suma Shivaprasad
Assignee: Keval Bhatt


Keval,

This jira is to track showing deleted entities with a diff color in lineage. Is 
there anything missing in the lineage API to implement this? We need to take 
care of this since no none looks at lineage via a process and will be mostly 
looking at lineage from a table

Also can we show the property (status)__status for deleted entities  as 
"DELETED" . We could display that in "properties" section.



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

[jira] [Comment Edited] (ATLAS-909) Lineage view is broken when there are lots of queries /processes between two datasets

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad edited comment on ATLAS-909 at 6/20/16 7:59 PM:
-

[~kevalbhatt18] I tested this again and I observed that I am able to move 
up/down in the window and resize if required to get to the required table(Was 
not aware of this earlier). Hence downgrading to Minor. Assigning to [~aahn] to 
decide on UX changes needed if any


was (Author: suma.shivaprasad):
[~kevalbhatt18] I tested this again and I observed that I am able to move 
up/down in the window and resize if required to get to the required table. 
Hence downgrading to Minor. Assigning to [~aahn] to decide on UX changes needed 
if any

> Lineage view is broken when there are lots of queries /processes between two 
> datasets
> -
>
> Key: ATLAS-909
> URL: https://issues.apache.org/jira/browse/ATLAS-909
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Andrew Ahn
>Priority: Minor
> Attachments: Screen Shot 2016-06-15 at 6.03.01 PM.png
>
>
> LIneage view does not have a scroll option and its height/width seem to be 
> limited which was not the case with the older dashboard. This is seen easily 
> when there are around more than 15-20 queries between two tables. Uploading 
> screen shot



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

[jira] [Updated] (ATLAS-909) Lineage view is broken when there are lots of queries /processes between two datasets

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-909:
---
Fix Version/s: (was: 0.7-incubating)

> Lineage view is broken when there are lots of queries /processes between two 
> datasets
> -
>
> Key: ATLAS-909
> URL: https://issues.apache.org/jira/browse/ATLAS-909
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Andrew Ahn
>Priority: Minor
> Attachments: Screen Shot 2016-06-15 at 6.03.01 PM.png
>
>
> LIneage view does not have a scroll option and its height/width seem to be 
> limited which was not the case with the older dashboard. This is seen easily 
> when there are around more than 15-20 queries between two tables. Uploading 
> screen shot



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

[jira] [Updated] (ATLAS-909) Lineage view is broken when there are lots of queries /processes between two datasets

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-909:
---
Priority: Minor  (was: Blocker)

> Lineage view is broken when there are lots of queries /processes between two 
> datasets
> -
>
> Key: ATLAS-909
> URL: https://issues.apache.org/jira/browse/ATLAS-909
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Minor
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-15 at 6.03.01 PM.png
>
>
> LIneage view does not have a scroll option and its height/width seem to be 
> limited which was not the case with the older dashboard. This is seen easily 
> when there are around more than 15-20 queries between two tables. Uploading 
> screen shot



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

[jira] [Updated] (ATLAS-909) Lineage view is broken when there are lots of queries /processes between two datasets

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-909:
---
Assignee: Andrew Ahn  (was: Keval Bhatt)

> Lineage view is broken when there are lots of queries /processes between two 
> datasets
> -
>
> Key: ATLAS-909
> URL: https://issues.apache.org/jira/browse/ATLAS-909
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Andrew Ahn
>Priority: Minor
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-15 at 6.03.01 PM.png
>
>
> LIneage view does not have a scroll option and its height/width seem to be 
> limited which was not the case with the older dashboard. This is seen easily 
> when there are around more than 15-20 queries between two tables. Uploading 
> screen shot



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

[jira] [Commented] (ATLAS-909) Lineage view is broken when there are lots of queries /processes between two datasets

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-909:


[~kevalbhatt18] I tested this again and I observed that I am able to move 
up/down in the window and resize if required to get to the required table. 
Hence downgrading to Minor. Assigning to [~aahn] to decide on UX changes needed 
if any

> Lineage view is broken when there are lots of queries /processes between two 
> datasets
> -
>
> Key: ATLAS-909
> URL: https://issues.apache.org/jira/browse/ATLAS-909
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Keval Bhatt
>Priority: Blocker
> Fix For: 0.7-incubating
>
> Attachments: Screen Shot 2016-06-15 at 6.03.01 PM.png
>
>
> LIneage view does not have a scroll option and its height/width seem to be 
> limited which was not the case with the older dashboard. This is seen easily 
> when there are around more than 15-20 queries between two tables. Uploading 
> screen shot



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

[jira] [Commented] (ATLAS-819) All user defined types should have a set of common attributes

[David Kantor (JIRA)]

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

David Kantor commented on ATLAS-819:


Now that Atlas has user authentication, and presumably all Atlas operations are 
done on behalf of some user, having createdByUser and modifiedByUser system 
attributes would *very* useful.   I had mentioned this in an earlier comment.  
Perhaps it is beyond the scope of this JIRA and should be tracked separately.

> All user defined types should have a set of common attributes
> -
>
> Key: ATLAS-819
> URL: https://issues.apache.org/jira/browse/ATLAS-819
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-819-v2.patch, ATLAS-819.patch
>
>
> It would be very convenient if all user defined types have a conventional set 
> of common attributes including:
> * name
> * description
> * owner
> * created at
> * modified at



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

[jira] [Commented] (ATLAS-844) Remove titan berkeley and elastic search jars if hbase/solr based profiles are chosen

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-844:


+1

> Remove titan berkeley and elastic search jars if hbase/solr based profiles 
> are chosen
> -
>
> Key: ATLAS-844
> URL: https://issues.apache.org/jira/browse/ATLAS-844
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-844.patch
>
>
> With ATLAS-833, users of Atlas now have the option of using an external 
> HBase/Solr installation, an self-contained HBase/Solr installation (embedded 
> mode) or BerkeleyDB/Elastic Search installation.
> When choosing either of the first two modes, we can potentially remove the 
> Titan berkeley DB or elastic search jars. This helps distributions which have 
> restrictions on using these jars from a contractual perspective.



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

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

[Apache Jenkins Server]

See 

Changes:

[sumasai.shivaprasad] ATLAS-915 Fix docs for import-hive changes (svimal2106 
via sumasai)

--
[...truncated 5980 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: 

Re: Review Request 48945: ATLAs-819 All user defined types should have a set of common attributes

[David Kantor]

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




webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java (line 
123)


Why has the log level has been changed to INFO in several places throught 
EntityResource?  I would think that in a production Atlas environment this 
would generate a lot of log noise.  Shouldn't these remain at DEBUG?



webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java (line 85)


See earlier comment about changing log level to INFO.


- David Kantor


On June 20, 2016, 12:01 p.m., Shwetha GS wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48945/
> ---
> 
> (Updated June 20, 2016, 12:01 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-819
> https://issues.apache.org/jira/browse/ATLAS-819
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Added  base type with the attributes name, owner and description that any 
> type can extend and the users can set these attributes.
> 
> 
> Diffs
> -
> 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/Util/EventUtil.java
>  c1ccd05 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/bridge/FalconBridge.java
>  1621d95 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/event/FalconEvent.java
>  37df6da 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java
>  95f255e 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
>  81cd5e0 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/service/AtlasService.java
>  c92bd43 
>   
> addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
>  8a5736a 
>   
> addons/hdfs-model/src/main/scala/org/apache/atlas/fs/model/FSDataModel.scala 
> cf81406 
>   
> 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/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
>  3686fa8 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> 5a175e7 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
> 9db8180 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/model/SqoopDataModelGenerator.java
>  c3bdbfa 
>   
> addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
>  b2171c2 
>   
> addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
>  bae4c1a 
>   client/src/main/java/org/apache/atlas/AtlasClient.java 4c88da9 
>   distro/src/conf/atlas-log4j.xml e14afa3 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
>  dd7dd74 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  c385df3 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  d9e6cb9 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/StructTypeDefinition.java
>  9dc93ae 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 0713d30 
>   webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java 
> 74d89ce 
> 
> Diff: https://reviews.apache.org/r/48945/diff/
> 
> 
> Testing
> ---
> 
> UTs
> 
> 
> Thanks,
> 
> Shwetha GS
> 
>

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

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad edited comment on ATLAS-698 at 6/20/16 7:22 PM:
-

[~shwethags]  For gremlin queries, was thinking it would be useful for querying 
/ debugging if there are issues/bugs with DSL queries . Could we mark it 
InterfaceAudience.Private instead of removing and just remove them from docs?

 +1 for Rexster API change


was (Author: suma.shivaprasad):
[~shwethags]  For gremlin queries, was thinking it would be useful for querying 
in debugging if there are issues/bugs with DSL queries . Could we mark it 
InterfaceAudience.Private instead of removing and just remove them from docs?

 +1 for Rexster API change

> 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.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] [Comment Edited] (ATLAS-698) Remove Rexster Graph and Gremlin REST API

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad edited comment on ATLAS-698 at 6/20/16 7:21 PM:
-

[~shwethags]  For gremlin queries, was thinking it would be useful for querying 
in debugging if there are issues/bugs with DSL queries . Could we mark it 
InterfaceAudience.Private instead of removing and just remove them from docs?

 +1 for Rexster API change


was (Author: suma.shivaprasad):
[~shwethags]  For gremlin queries, was thinking it would be useful for querying 
in debugging if there are issues/bugs with DSL queries . Could we mark it 
InterfaceAudience.Private instead of removing?

 

> 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.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

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad commented on ATLAS-698:


[~shwethags]  For gremlin queries, was thinking it would be useful for querying 
in debugging if there are issues/bugs with DSL queries . Could we mark it 
InterfaceAudience.Private instead of removing?

 

> 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.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)

Re: Review Request 48945: ATLAs-819 All user defined types should have a set of common attributes

[Suma Shivaprasad]

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


Ship it!




Ship It!

- Suma Shivaprasad


On June 20, 2016, 12:01 p.m., Shwetha GS wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48945/
> ---
> 
> (Updated June 20, 2016, 12:01 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-819
> https://issues.apache.org/jira/browse/ATLAS-819
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Added  base type with the attributes name, owner and description that any 
> type can extend and the users can set these attributes.
> 
> 
> Diffs
> -
> 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/Util/EventUtil.java
>  c1ccd05 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/bridge/FalconBridge.java
>  1621d95 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/event/FalconEvent.java
>  37df6da 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java
>  95f255e 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
>  81cd5e0 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/service/AtlasService.java
>  c92bd43 
>   
> addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
>  8a5736a 
>   
> addons/hdfs-model/src/main/scala/org/apache/atlas/fs/model/FSDataModel.scala 
> cf81406 
>   
> 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/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
>  3686fa8 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> 5a175e7 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
> 9db8180 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/model/SqoopDataModelGenerator.java
>  c3bdbfa 
>   
> addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
>  b2171c2 
>   
> addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
>  bae4c1a 
>   client/src/main/java/org/apache/atlas/AtlasClient.java 4c88da9 
>   distro/src/conf/atlas-log4j.xml e14afa3 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
>  dd7dd74 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  c385df3 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  d9e6cb9 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/StructTypeDefinition.java
>  9dc93ae 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 0713d30 
>   webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java 
> 74d89ce 
> 
> Diff: https://reviews.apache.org/r/48945/diff/
> 
> 
> Testing
> ---
> 
> UTs
> 
> 
> Thanks,
> 
> Shwetha GS
> 
>

Re: Review Request 48945: ATLAs-819 All user defined types should have a set of common attributes

[Suma Shivaprasad]

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


Ship it!




Ship It!

- Suma Shivaprasad


On June 20, 2016, 12:01 p.m., Shwetha GS wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48945/
> ---
> 
> (Updated June 20, 2016, 12:01 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-819
> https://issues.apache.org/jira/browse/ATLAS-819
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Added  base type with the attributes name, owner and description that any 
> type can extend and the users can set these attributes.
> 
> 
> Diffs
> -
> 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/Util/EventUtil.java
>  c1ccd05 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/bridge/FalconBridge.java
>  1621d95 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/event/FalconEvent.java
>  37df6da 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java
>  95f255e 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
>  81cd5e0 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/service/AtlasService.java
>  c92bd43 
>   
> addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
>  8a5736a 
>   
> addons/hdfs-model/src/main/scala/org/apache/atlas/fs/model/FSDataModel.scala 
> cf81406 
>   
> 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/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
>  3686fa8 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> 5a175e7 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
> 9db8180 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/model/SqoopDataModelGenerator.java
>  c3bdbfa 
>   
> addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
>  b2171c2 
>   
> addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
>  bae4c1a 
>   client/src/main/java/org/apache/atlas/AtlasClient.java 4c88da9 
>   distro/src/conf/atlas-log4j.xml e14afa3 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
>  dd7dd74 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  c385df3 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  d9e6cb9 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/StructTypeDefinition.java
>  9dc93ae 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 0713d30 
>   webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java 
> 74d89ce 
> 
> Diff: https://reviews.apache.org/r/48945/diff/
> 
> 
> Testing
> ---
> 
> UTs
> 
> 
> Thanks,
> 
> Shwetha GS
> 
>

Atlas and sqoop hook

[Margus Roo]

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-atlas/
There I can see that extra config parameters are loaded (in picture 
https://raw.githubusercontent.com/hortonworks/tutorials/atlas-ranger-tp/assets/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/slf4j/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 mapreduce.Job: Counters: 30
File System Counters
FILE: Number of bytes read=0
FILE: Number of bytes written=310818
FILE: Number of read operations=0
FILE: Number of large read operations=0
FILE: Number of write operations=0
HDFS: Number of bytes read=197

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

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad edited comment on ATLAS-904 at 6/20/16 6:25 PM:
-

Addressed review comments and rebased. Will address the partition based checks 
and handling in a separate jira - ATLAS-917


was (Author: suma.shivaprasad):
Addressed review comments and rebased. Will address the partition based checks 
and handling in a separate jira

> 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.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] [Created] (ATLAS-917) Add hdfs paths to process qualified name for non-partition based queries

[Suma Shivaprasad (JIRA)]

Suma Shivaprasad created ATLAS-917:
--

 Summary: Add hdfs paths to process qualified name for 
non-partition based queries
 Key: ATLAS-917
 URL: https://issues.apache.org/jira/browse/ATLAS-917
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.7-incubating
Reporter: Suma Shivaprasad
Assignee: Suma Shivaprasad


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.



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

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

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad edited comment on ATLAS-904 at 6/20/16 6:23 PM:
-

Addressed review comments and rebased. Will address the partition based checks 
and handling in a separate jira


was (Author: suma.shivaprasad):
Addressed review comments and rebased

> 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.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-904) Hive hook fails due to session state not being set

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-904:
---
Attachment: ATLAS-904.3.patch

Addressed review comments and rebased

> 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.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)

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

[Suma Shivaprasad]

---
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.


Changes
---

Fixed test failures due to lower case change


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 (updated)
-

  
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] [Updated] (ATLAS-647) entityText property should be prefixed with __

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-647:
---
Fix Version/s: (was: 0.7-incubating)

> entityText property should be prefixed with __
> --
>
> Key: ATLAS-647
> URL: https://issues.apache.org/jira/browse/ATLAS-647
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>
> All internal properties for the vertex in the repository are prefixed with __ 
> to avoid conflicts with user defined attribute names. Looks like entityText 
> is missed out



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

[jira] [Updated] (ATLAS-625) GraphBackedDiscoveryServiceTest throws an exception in shutdown.

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-625:
---
Fix Version/s: (was: 0.7-incubating)

> GraphBackedDiscoveryServiceTest throws an exception in shutdown.
> 
>
> Key: ATLAS-625
> URL: https://issues.apache.org/jira/browse/ATLAS-625
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>
> The tests don't fail because this is guarded by a try-catch block, but 
> ideally we should check why we are getting this error and make sure the right 
> fix is done. This was pointed out by [~nixonrodrigues] initially.
> Filing this here just so we don't lose track.



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

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

[Shwetha G S (JIRA)]

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

Shwetha G S reassigned ATLAS-822:
-

Assignee: Shwetha G S

> 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
>
>
> 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)

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

[Suma Shivaprasad]

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

(Updated June 20, 2016, 5:27 p.m.)


Review request for atlas, Shwetha GS and Hemanth Yamijala.


Changes
---

Thanks for reviewing Hemanth. Fixed review comments. Please reopen any issue 
which I have dropped if you feel it should be addressed or if you have any more 
questions.


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 (updated)
-

  
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] [Updated] (ATLAS-493) Entity Versioning Support - Audit only

[Shwetha G S (JIRA)]

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

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

> Entity Versioning Support - Audit only
> --
>
> Key: ATLAS-493
> URL: https://issues.apache.org/jira/browse/ATLAS-493
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Shwetha G S
>
> General Use Case
> Atlas must be able to track the evolution of assets as they change. Each 
> evolution (or version) of each asset must be recorded in order to track 
> lineage
> Delete Use Case
> If an asset is deleted, the asset should not show up searches unless 
> explicitly searched for.
> Requirements
> Be able to show changes over time to be implemented through Audit Log
> Requires API support to retrieve history



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

[jira] [Updated] (ATLAS-492) Hive Hook Improvements

[Suma Shivaprasad (JIRA)]

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

Suma Shivaprasad updated ATLAS-492:
---
Fix Version/s: (was: 0.7-incubating)

> Hive Hook Improvements
> --
>
> Key: ATLAS-492
> URL: https://issues.apache.org/jira/browse/ATLAS-492
> Project: Atlas
>  Issue Type: New Feature
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Suma Shivaprasad
>
> h2. Requirements:
> * Support ALTER statements (add/replace/rename cols)
> * Support DROP statements ( support drop database, table, view)
> * Support LOAD statements
> * Remodelling changes



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

[jira] [Updated] (ATLAS-589) Document entity audit

[Shwetha G S (JIRA)]

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

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

> Document entity audit
> -
>
> Key: ATLAS-589
> URL: https://issues.apache.org/jira/browse/ATLAS-589
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>




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

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

[Shwetha G S (JIRA)]

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

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

Yes, we shouldn't allow updating supertypes

> 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
> Fix For: 0.7-incubating
>
>
> 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-807) Search for entities in v1 API could be very costly.

[Shwetha G S (JIRA)]

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

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

> Search for entities in v1 API could be very costly.
> ---
>
> Key: ATLAS-807
> URL: https://issues.apache.org/jira/browse/ATLAS-807
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: John Speidel
>
> As part of ATLAS-491, there is a new entity search API that uses Lucene 
> syntax. This search could be very costly, because the starting pipeline 
> filters for those vertices which have an attribute {entityText}. This is 
> added for pretty much every entity added to Atlas. So the Gremlin pipeline 
> could result in a lot of results. I am not entirely sure what the impact of 
> this will be, but filing it to keep track of analysis.



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

[jira] [Updated] (ATLAS-828) Entity audit creates lot of records for unchanged entities or irrelevant updates

[Shwetha G S (JIRA)]

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

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

> Entity audit creates lot of records for unchanged entities or irrelevant 
> updates
> 
>
> Key: ATLAS-828
> URL: https://issues.apache.org/jira/browse/ATLAS-828
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>
> Run a script to create 100 hive_tables in the same database.
> There will be about 100 audit records for the database indicating there was 
> an entity update on it. The information in each update is the same (probably 
> there's some timestamp that's changing, haven't looked very carefully).
> This is not very useful information, and is likely to make users miss more 
> relevant updates to the DB entity.



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

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

[Suma Shivaprasad]

> On June 20, 2016, 9:26 a.m., Hemanth Yamijala wrote:
> > addons/hive-bridge/src/main/java/org/apache/atlas/hive/hook/HiveHook.java, 
> > line 763
> > 
> >
> > Do we need a separator between the input set and output set?

This is already being taken care of within the if checks and is added before 
and output dataset entry is added to the buffer.


- Suma


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


On June 20, 2016, 4 a.m., Suma Shivaprasad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48939/
> ---
> 
> (Updated June 20, 2016, 4 a.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 
> 23c82df 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> e7fbf71 
>   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-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-624:


[~Kalyanikashikar], The scenario I raised is working. However clicking on Left 
hand pane > a tag > Search Tag is now firing full text query. Can you please 
check?

> 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] [Updated] (ATLAS-624) UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

[Kalyani Kashikar (JIRA)]

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

Kalyani Kashikar updated ATLAS-624:
---
Attachment: ATLAS-624.1.patch

[~yhemanth] Taken care of all the scenario from feedback provided by you.

> 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)

Re: Review Request 48724: ATLAS-624 : UI: Clicking a tag hyperlink should always result in DSL search. In some cases, results in full-text search.

[Kalyani Kashikar]

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

(Updated June 20, 2016, 1:39 p.m.)


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


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


Repository: atlas


Description
---

Tag search back tick character (`) added and search type changed to 'dsl'


Diffs (updated)
-

  dashboardv2/public/css/scss/main.scss 85a68b1 
  dashboardv2/public/js/templates/business_catalog/TreeLayoutView_tmpl.html 
b915680 
  dashboardv2/public/js/utils/CommonViewFunction.js a1c 
  dashboardv2/public/js/views/business_catalog/TreeLayoutView.js 63eaa3e 
  dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js cb96c79 
  dashboardv2/public/js/views/schema/SchemaLayoutView.js 55e7093 
  dashboardv2/public/js/views/search/SearchResultLayoutView.js 75bf6ef 
  dashboardv2/public/js/views/tag/TagDetailLayoutView.js 7e0f7ed 
  dashboardv2/public/js/views/tag/TagDetailTableLayoutView.js e9d4b57 
  dashboardv2/public/js/views/tag/TagLayoutView.js 42b8078 

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


Testing
---

**Verified following scenarios:** 
1) DSL search gets invoked from Tags on action of "Search Tag".
2) Verified that is we perform "Search Tag" it doesn't invoke fulltext search 
call. 
3) After adding ` in search query - DSL search results are comming correctly.


Thanks,

Kalyani Kashikar

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

[Vimal Sharma (JIRA)]

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

Vimal Sharma reassigned ATLAS-698:
--

Assignee: Vimal Sharma

> 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.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)

Re: Review Request 48945: ATLAs-819 All user defined types should have a set of common attributes

[Hemanth Yamijala]

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


Ship it!




The changes look ok to me. Please review model changes with Suma once before 
shipping.

- Hemanth Yamijala


On June 20, 2016, 12:01 p.m., Shwetha GS wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48945/
> ---
> 
> (Updated June 20, 2016, 12:01 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-819
> https://issues.apache.org/jira/browse/ATLAS-819
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Added  base type with the attributes name, owner and description that any 
> type can extend and the users can set these attributes.
> 
> 
> Diffs
> -
> 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/Util/EventUtil.java
>  c1ccd05 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/bridge/FalconBridge.java
>  1621d95 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/event/FalconEvent.java
>  37df6da 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java
>  95f255e 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
>  81cd5e0 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/service/AtlasService.java
>  c92bd43 
>   
> addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
>  8a5736a 
>   
> addons/hdfs-model/src/main/scala/org/apache/atlas/fs/model/FSDataModel.scala 
> cf81406 
>   
> 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/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
>  3686fa8 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> 5a175e7 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
> 9db8180 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/model/SqoopDataModelGenerator.java
>  c3bdbfa 
>   
> addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
>  b2171c2 
>   
> addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
>  bae4c1a 
>   client/src/main/java/org/apache/atlas/AtlasClient.java 4c88da9 
>   distro/src/conf/atlas-log4j.xml e14afa3 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
>  dd7dd74 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  c385df3 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  d9e6cb9 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/StructTypeDefinition.java
>  9dc93ae 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 0713d30 
>   webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java 
> 74d89ce 
> 
> Diff: https://reviews.apache.org/r/48945/diff/
> 
> 
> Testing
> ---
> 
> UTs
> 
> 
> Thanks,
> 
> Shwetha GS
> 
>

[jira] [Commented] (ATLAS-915) Fix docs for import-hive changes

[ATLAS QA (JIRA)]

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

ATLAS QA commented on ATLAS-915:


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

{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/329//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/329//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/329//console

This message is automatically generated.

> Fix docs for import-hive changes
> 
>
> Key: ATLAS-915
> URL: https://issues.apache.org/jira/browse/ATLAS-915
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-915.patch, ATLAS-915.patch
>
>
> Pls fix According to changes in ATLAS-688



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

[jira] [Resolved] (ATLAS-739) UI: Search result for hive_process results in "query text of hive process shown as href link"

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala resolved ATLAS-739.

Resolution: Fixed

The new UI does not have these columns - they only show a name which 
corresponds to the query text (no hrefs etc). Hence, closing.

> UI: Search result for hive_process results in "query text of hive process 
> shown as href link"
> -
>
> Key: ATLAS-739
> URL: https://issues.apache.org/jira/browse/ATLAS-739
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Erik Bergenholtz
> Fix For: 0.7-incubating
>
>
> snapshot link for reference: 
> https://monosnap.com/file/k2JvD95oq63S6bHztj00fluCgJsTEW



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

[jira] [Updated] (ATLAS-819) All user defined types should have a set of common attributes

[Shwetha G S (JIRA)]

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

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

Addressed review comments

> All user defined types should have a set of common attributes
> -
>
> Key: ATLAS-819
> URL: https://issues.apache.org/jira/browse/ATLAS-819
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-819-v2.patch, ATLAS-819.patch
>
>
> It would be very convenient if all user defined types have a conventional set 
> of common attributes including:
> * name
> * description
> * owner
> * created at
> * modified at



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

Re: Review Request 48945: ATLAs-819 All user defined types should have a set of common attributes

[Shwetha GS]

> On June 20, 2016, 10:19 a.m., Hemanth Yamijala wrote:
> > addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java,
> >  line 107
> > 
> >
> > I didn't get why this was removed - possibly something specific to 
> > Falcon? Likewise, is the USER attribute going to be replaced by OWNER?

timestamp was set to current time and didn't have any other significance. 
Deleted it in favor of atlas system attributes created time and last modified 
time. user is deleted as owner is set now


> On June 20, 2016, 10:19 a.m., Hemanth Yamijala wrote:
> > addons/hdfs-model/src/main/scala/org/apache/atlas/fs/model/FSDataModel.scala,
> >  line 51
> > 
> >
> > This is removed, but should extend Asset?

Have made fs_path extend dataset and hdfs_path extend fs_path. Will check with 
Suma once


- Shwetha


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


On June 20, 2016, 9:01 a.m., Shwetha GS wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48945/
> ---
> 
> (Updated June 20, 2016, 9:01 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-819
> https://issues.apache.org/jira/browse/ATLAS-819
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Added  base type with the attributes name, owner and description that any 
> type can extend and the users can set these attributes.
> 
> 
> Diffs
> -
> 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/Util/EventUtil.java
>  c1ccd05 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/bridge/FalconBridge.java
>  1621d95 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/event/FalconEvent.java
>  37df6da 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java
>  95f255e 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
>  81cd5e0 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/service/AtlasService.java
>  c92bd43 
>   
> addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
>  8a5736a 
>   
> addons/hdfs-model/src/main/scala/org/apache/atlas/fs/model/FSDataModel.scala 
> cf81406 
>   
> 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/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
>  3686fa8 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> 5a175e7 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
> 9db8180 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/model/SqoopDataModelGenerator.java
>  c3bdbfa 
>   
> addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
>  b2171c2 
>   
> addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
>  bae4c1a 
>   client/src/main/java/org/apache/atlas/AtlasClient.java 4c88da9 
>   distro/src/conf/atlas-log4j.xml e14afa3 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
>  dd7dd74 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  c385df3 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  d9e6cb9 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/StructTypeDefinition.java
>  9dc93ae 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 0713d30 
>   webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java 
> 74d89ce 
> 
> Diff: https://reviews.apache.org/r/48945/diff/
> 
> 
> Testing
> ---
> 
> UTs
> 
> 
> Thanks,
> 
> Shwetha GS
> 
>

Re: Review Request 48945: ATLAs-819 All user defined types should have a set of common attributes

[Shwetha GS]

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

(Updated June 20, 2016, 12:01 p.m.)


Review request for atlas.


Changes
---

Addressed review comments


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


Repository: atlas


Description
---

Added  base type with the attributes name, owner and description that any type 
can extend and the users can set these attributes.


Diffs (updated)
-

  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/Util/EventUtil.java 
c1ccd05 
  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/bridge/FalconBridge.java
 1621d95 
  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/event/FalconEvent.java
 37df6da 
  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java 
95f255e 
  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
 81cd5e0 
  
addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/service/AtlasService.java
 c92bd43 
  
addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
 8a5736a 
  addons/hdfs-model/src/main/scala/org/apache/atlas/fs/model/FSDataModel.scala 
cf81406 
  
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/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
 3686fa8 
  addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
5a175e7 
  addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/hook/SqoopHook.java 
9db8180 
  
addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/model/SqoopDataModelGenerator.java
 c3bdbfa 
  
addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
 b2171c2 
  
addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
 bae4c1a 
  client/src/main/java/org/apache/atlas/AtlasClient.java 4c88da9 
  distro/src/conf/atlas-log4j.xml e14afa3 
  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
 dd7dd74 
  
repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
 c385df3 
  
repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java 
d9e6cb9 
  
typesystem/src/main/java/org/apache/atlas/typesystem/types/StructTypeDefinition.java
 9dc93ae 
  webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
0713d30 
  webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java 
74d89ce 

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


Testing
---

UTs


Thanks,

Shwetha GS

[jira] [Updated] (ATLAS-591) Atlas client ssl configuration failure

[Shwetha G S (JIRA)]

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

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

> Atlas client ssl configuration failure
> --
>
> Key: ATLAS-591
> URL: https://issues.apache.org/jira/browse/ATLAS-591
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>
> When server is not set-up with ssl, client shouldn't configure params for ssl
> {noformat}
> 2016-03-23 13:59:35,013 DEBUG [main]: atlas.ApplicationProperties 
> (ApplicationProperties.java:logConfiguration(86)) - atlas.enableTLS = false
> 2016-03-23 13:59:35,018 DEBUG [main]: atlas.ApplicationProperties 
> (ApplicationProperties.java:logConfiguration(86)) - atlas.rest.address = 
> http://localhost:21000
> 2016-03-23 13:59:35,420 DEBUG [Atlas Logger 0]: security.SecureClientUtils 
> (SecureClientUtils.java:newConnConfigurator(138)) - Cannot load customized 
> ssl related configuration. Fallback to system-generic settings.
> java.io.FileNotFoundException: /etc/security/clientKeys/all.jks (No such file 
> or directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.(FileInputStream.java:138)
> at 
> org.apache.hadoop.security.ssl.ReloadingX509TrustManager.loadTrustManager(ReloadingX509TrustManager.java:164)
> at 
> org.apache.hadoop.security.ssl.ReloadingX509TrustManager.(ReloadingX509TrustManager.java:81)
> at 
> org.apache.hadoop.security.ssl.FileBasedKeyStoresFactory.init(FileBasedKeyStoresFactory.java:209)
> at org.apache.hadoop.security.ssl.SSLFactory.init(SSLFactory.java:131)
> at 
> org.apache.atlas.security.SecureClientUtils.newSslConnConfigurator(SecureClientUtils.java:150)
> at 
> org.apache.atlas.security.SecureClientUtils.newConnConfigurator(SecureClientUtils.java:136)
> at 
> org.apache.atlas.security.SecureClientUtils.getClientConnectionHandler(SecureClientUtils.java:69)
> at org.apache.atlas.AtlasClient.(AtlasClient.java:126)
> at 
> org.apache.atlas.hive.bridge.HiveMetaStoreBridge.(HiveMetaStoreBridge.java:97)
> at 
> org.apache.atlas.hive.hook.HiveHook.fireAndForget(HiveHook.java:195)
> at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:62)
> at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:181)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Updated] (ATLAS-660) Validate that same entity is part of two composite references

[Shwetha G S (JIRA)]

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

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

> Validate that same entity is part of two composite references
> -
>
> Key: ATLAS-660
> URL: https://issues.apache.org/jira/browse/ATLAS-660
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>
> Currently, atlas allows an entity to be part of composite references of two 
> parent entities. For example, hive_column is a composite attribute of 
> hive_table. A hive_column entity can't be part of two different hive_table 
> entities (by the definition of composite which means child entity's lifecycle 
> depends on parent entity's lifecycle)



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

[jira] [Updated] (ATLAS-811) Entity delete should check for required reverse references - soft deletes

[Shwetha G S (JIRA)]

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

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

> Entity delete should check for required reverse references - soft deletes
> -
>
> Key: ATLAS-811
> URL: https://issues.apache.org/jira/browse/ATLAS-811
> Project: Atlas
>  Issue Type: Bug
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>
> DeleteHandler.deleteEdgeBetweenVertices() checks for elements.size(). With 
> soft deletes, even the deleted elements are part of the array. It should 
> instead check for active elements



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

[jira] [Commented] (ATLAS-819) All user defined types should have a set of common attributes

[Shwetha G S (JIRA)]

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

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

Yes, it makes sense to set column owner to table owner, will make the change

> All user defined types should have a set of common attributes
> -
>
> Key: ATLAS-819
> URL: https://issues.apache.org/jira/browse/ATLAS-819
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-819.patch
>
>
> It would be very convenient if all user defined types have a conventional set 
> of common attributes including:
> * name
> * description
> * owner
> * created at
> * modified at



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

[jira] [Commented] (ATLAS-915) Fix docs for import-hive changes

[Shwetha G S (JIRA)]

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

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

+1

> Fix docs for import-hive changes
> 
>
> Key: ATLAS-915
> URL: https://issues.apache.org/jira/browse/ATLAS-915
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-915.patch, ATLAS-915.patch
>
>
> Pls fix According to changes in ATLAS-688



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

[jira] [Commented] (ATLAS-915) Fix docs for import-hive changes

[ATLAS QA (JIRA)]

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

ATLAS QA commented on ATLAS-915:


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

{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/328//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/328//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/328//console

This message is automatically generated.

> Fix docs for import-hive changes
> 
>
> Key: ATLAS-915
> URL: https://issues.apache.org/jira/browse/ATLAS-915
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-915.patch, ATLAS-915.patch
>
>
> Pls fix According to changes in ATLAS-688



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

[jira] [Commented] (ATLAS-819) All user defined types should have a set of common attributes

[Hemanth Yamijala (JIRA)]

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

Hemanth Yamijala commented on ATLAS-819:


Added some review comments to the review board link.

In addition, compiled and tested this with Hive. One thing is that the columns 
now contain 'owner' which is coming as null. Should we default set owner to 
table owner?

> All user defined types should have a set of common attributes
> -
>
> Key: ATLAS-819
> URL: https://issues.apache.org/jira/browse/ATLAS-819
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-819.patch
>
>
> It would be very convenient if all user defined types have a conventional set 
> of common attributes including:
> * name
> * description
> * owner
> * created at
> * modified at



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

[jira] [Updated] (ATLAS-915) Fix docs for import-hive changes

[Vimal Sharma (JIRA)]

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

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

> Fix docs for import-hive changes
> 
>
> Key: ATLAS-915
> URL: https://issues.apache.org/jira/browse/ATLAS-915
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-915.patch, ATLAS-915.patch
>
>
> Pls fix According to changes in ATLAS-688



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

Re: Review Request 48945: ATLAs-819 All user defined types should have a set of common attributes

[Hemanth Yamijala]

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




addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
 


I didn't get why this was removed - possibly something specific to Falcon? 
Likewise, is the USER attribute going to be replaced by OWNER?



addons/hdfs-model/src/main/scala/org/apache/atlas/fs/model/FSDataModel.scala 


This is removed, but should extend Asset?



addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
 (line 48)


description is a part of Asset. So should go, just like owner?


- Hemanth Yamijala


On June 20, 2016, 9:01 a.m., Shwetha GS wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/48945/
> ---
> 
> (Updated June 20, 2016, 9:01 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-819
> https://issues.apache.org/jira/browse/ATLAS-819
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Added  base type with the attributes name, owner and description that any 
> type can extend and the users can set these attributes.
> 
> 
> Diffs
> -
> 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/Util/EventUtil.java
>  c1ccd05 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/bridge/FalconBridge.java
>  1621d95 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/event/FalconEvent.java
>  37df6da 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/hook/FalconHook.java
>  95f255e 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/model/FalconDataModelGenerator.java
>  81cd5e0 
>   
> addons/falcon-bridge/src/main/java/org/apache/atlas/falcon/service/AtlasService.java
>  c92bd43 
>   
> addons/falcon-bridge/src/test/java/org/apache/atlas/falcon/hook/FalconHookIT.java
>  8a5736a 
>   
> addons/hdfs-model/src/main/scala/org/apache/atlas/fs/model/FSDataModel.scala 
> cf81406 
>   
> addons/hive-bridge/src/main/java/org/apache/atlas/hive/model/HiveDataModelGenerator.java
>  3686fa8 
>   
> addons/sqoop-bridge/src/main/java/org/apache/atlas/sqoop/model/SqoopDataModelGenerator.java
>  c3bdbfa 
>   
> addons/storm-bridge/src/main/java/org/apache/atlas/storm/hook/StormAtlasHook.java
>  b2171c2 
>   
> addons/storm-bridge/src/main/scala/org/apache/atlas/storm/model/StormDataModel.scala
>  bae4c1a 
>   client/src/main/java/org/apache/atlas/AtlasClient.java 4c88da9 
>   distro/src/conf/atlas-log4j.xml e14afa3 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedMetadataRepository.java
>  dd7dd74 
>   
> repository/src/main/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexer.java
>  c385df3 
>   
> repository/src/main/java/org/apache/atlas/services/DefaultMetadataService.java
>  d9e6cb9 
>   
> typesystem/src/main/java/org/apache/atlas/typesystem/types/StructTypeDefinition.java
>  9dc93ae 
>   webapp/src/main/java/org/apache/atlas/web/resources/EntityResource.java 
> 0713d30 
>   webapp/src/main/java/org/apache/atlas/web/resources/TypesResource.java 
> 74d89ce 
> 
> Diff: https://reviews.apache.org/r/48945/diff/
> 
> 
> Testing
> ---
> 
> UTs
> 
> 
> Thanks,
> 
> Shwetha GS
> 
>

[jira] [Commented] (ATLAS-819) All user defined types should have a set of common attributes

[ATLAS QA (JIRA)]

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

ATLAS QA commented on ATLAS-819:


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

{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/327//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/327//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/327//console

This message is automatically generated.

> All user defined types should have a set of common attributes
> -
>
> Key: ATLAS-819
> URL: https://issues.apache.org/jira/browse/ATLAS-819
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-819.patch
>
>
> It would be very convenient if all user defined types have a conventional set 
> of common attributes including:
> * name
> * description
> * owner
> * created at
> * modified at



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

[jira] [Updated] (ATLAS-915) Fix docs for import-hive changes

[Vimal Sharma (JIRA)]

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

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

> Fix docs for import-hive changes
> 
>
> Key: ATLAS-915
> URL: https://issues.apache.org/jira/browse/ATLAS-915
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Vimal Sharma
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-915.patch
>
>
> Pls fix According to changes in ATLAS-688



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

[jira] [Updated] (ATLAS-653) insert into local dir, load from local dir does not show up in lineage

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-653:
--
Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-492

> insert into local dir, load from local dir does not show up in lineage
> --
>
> Key: ATLAS-653
> URL: https://issues.apache.org/jira/browse/ATLAS-653
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.7-incubating
>Reporter: Suma Shivaprasad
>Assignee: Suma Shivaprasad
>
> All the above commands do not show up in lineage since they dont have any 
> input entities registered.
> Local FS Paths can be modelled without any unique paths/attributes and can be 
> displayed in lineage



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

[jira] [Updated] (ATLAS-778) ALTER TABLE TOUCH is not modelled

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-778:
--
Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-492

> ALTER TABLE TOUCH is not modelled
> -
>
> Key: ATLAS-778
> URL: https://issues.apache.org/jira/browse/ATLAS-778
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>
> ALTER TABLE TOUCH is not modelled.
> ALTER TABLE TOUCH changes metadata of hive table(like create time, 
> transient_lastDdlTime). No entity update message is sent to atlas when table 
> touch command is fired.
> {noformat}
> 0: jdbc:hive2://localhost:1/default> describe formatted tg2;
> +---+-+---+--+
> |   col_name|data_type
> |comment|
> +---+-+---+--+
> | # col_name| data_type   
> | comment   |
> |   | NULL
> | NULL  |
> | abc   | string  
> |   |
> |   | NULL
> | NULL  |
> | # Detailed Table Information  | NULL
> | NULL  |
> | Database: | db2sdbxnpqone   
> | NULL  |
> | Owner:| apathan 
> | NULL  |
> | CreateTime:   | Wed May 11 23:19:55 IST 2016
> | NULL  |
> | LastAccessTime:   | UNKNOWN 
> | NULL  |
> | Protect Mode: | None
> | NULL  |
> | Retention:| 0   
> | NULL  |
> | Location: | 
> hdfs://localhost:9000/user/hive/warehouse/db2sdbxnpqone.db/tg2  | NULL
>   |
> | Table Type:   | MANAGED_TABLE   
> | NULL  |
> | Table Parameters: | NULL
> | NULL  |
> |   | transient_lastDdlTime   
> | 1462988995|
> |   | NULL
> | NULL  |
> | # Storage Information | NULL
> | NULL  |
> | SerDe Library:| 
> org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe  | NULL
>   |
> | InputFormat:  | org.apache.hadoop.mapred.TextInputFormat
> | NULL  |
> | OutputFormat: | 
> org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat  | NULL
>   |
> | Compressed:   | No  
> | NULL  |
> | Num Buckets:  | -1  
> | NULL  |
> | Bucket Columns:   | []  
> | NULL  |
> | Sort Columns: | []  
> | NULL  |
> | Storage Desc Params:  | NULL
> | NULL  |
> |   | serialization.format
> | 1 |
> +---+-+---+--+
> 26 rows selected (0.113 seconds)
> 0: jdbc:hive2://localhost:1/default> alter table tg2 touch;
> No rows affected (0.173 seconds)
> 0: jdbc:hive2://localhost:1/default> describe formatted tg2;
> 

[jira] [Updated] (ATLAS-702) "ALTER TABLE .. NOT STORED AS DIRECTORIES" metadata update is not sent to Atlas.

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-702:
--
Issue Type: Sub-task  (was: Bug)
Parent: ATLAS-492

> "ALTER TABLE .. NOT STORED AS DIRECTORIES" metadata update is not sent to 
> Atlas.
> 
>
> Key: ATLAS-702
> URL: https://issues.apache.org/jira/browse/ATLAS-702
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Assignee: Suma Shivaprasad
>
> 1. CREATE TABLE list_bucket_single (key STRING, value STRING) SKEWED BY (key) 
> ON (1,5,6) STORED AS DIRECTORIES;
> {noformat}
> 0: jdbc:hive2://localhost:1/default> describe formatted 
> list_bucket_single2;
> +---++---+--+
> |   col_name|   data_type 
>|comment|
> +---++---+--+
> | # col_name| data_type   
>| comment   |
> |   | NULL
>| NULL  |
> | key   | string  
>|   |
> | value | string  
>|   |
> |   | NULL
>| NULL  |
> | # Detailed Table Information  | NULL
>| NULL  |
> | Database: | default 
>| NULL  |
> | Owner:| apathan 
>| NULL  |
> | CreateTime:   | Mon Apr 25 16:27:21 IST 2016
>| NULL  |
> | LastAccessTime:   | UNKNOWN 
>| NULL  |
> | Protect Mode: | None
>| NULL  |
> | Retention:| 0   
>| NULL  |
> | Location: | 
> hdfs://localhost:9000/user/hive/warehouse/list_bucket_single2  | NULL 
>  |
> | Table Type:   | MANAGED_TABLE   
>| NULL  |
> | Table Parameters: | NULL
>| NULL  |
> |   | transient_lastDdlTime   
>| 1461581841|
> |   | NULL
>| NULL  |
> | # Storage Information | NULL
>| NULL  |
> | SerDe Library:| 
> org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe | NULL 
>  |
> | InputFormat:  | org.apache.hadoop.mapred.TextInputFormat
>| NULL  |
> | OutputFormat: | 
> org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat | NULL 
>  |
> | Compressed:   | No  
>| NULL  |
> | Num Buckets:  | -1  
>| NULL  |
> | Bucket Columns:   | []  
>| NULL  |
> | Sort Columns: | []  
>| NULL  |
> | Stored As SubDirectories: | Yes 
>| NULL  |
> | Skewed Columns:   | [key]   
>| NULL  |
> | Skewed Values:| [[1], [5], [6]] 
>| NULL  |
> | Storage Desc Params:  | NULL
>| 

[jira] [Updated] (ATLAS-538) Capture update delta details

[Shwetha G S (JIRA)]

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

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

> Capture update delta details
> 
>
> Key: ATLAS-538
> URL: https://issues.apache.org/jira/browse/ATLAS-538
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>
> Atlas supports partial/full update which can take the entire entity. We need 
> to figure out the exact attributes updated for entity history



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

[jira] [Resolved] (ATLAS-566) Remove BDB References

[Shwetha G S (JIRA)]

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

Shwetha G S resolved ATLAS-566.
---
Resolution: Duplicate

> Remove BDB References
> -
>
> Key: ATLAS-566
> URL: https://issues.apache.org/jira/browse/ATLAS-566
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Tom Beerbower
> Fix For: 0.7-incubating
>
>
> Berkley DB should be removed from Apache Atlas and should not be referenced 
> from any POMs or pulled in to any DOs of Atlas.



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

[jira] [Resolved] (ATLAS-581) Atlas UI should show state of Entity

[Shwetha G S (JIRA)]

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

Shwetha G S resolved ATLAS-581.
---
Resolution: Duplicate

> Atlas UI should show state of Entity
> 
>
> Key: ATLAS-581
> URL: https://issues.apache.org/jira/browse/ATLAS-581
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Erik Bergenholtz
>Assignee: Keval Bhatt
> Fix For: 0.7-incubating
>
>
> Atlas will be introducing an attribute indicating whether or not an entity is 
> deleted. In the search results page the UI should differentiate between a 
> deleted entity and a non-deleted entity. The best way to do this is up for 
> discussion, several options include:
> - Introduce a separate 'deleted' column with a check mark for deleted Entities
> - Show deleted Entities in muted gray text
> - Show deleted Entities in -strikethrough- text



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

[jira] [Updated] (ATLAS-630) Network partition of active instance before first time initialization completes could cause a split-brain scenario

[Shwetha G S (JIRA)]

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

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

> Network partition of active instance before first time initialization 
> completes could cause a split-brain scenario
> --
>
> Key: ATLAS-630
> URL: https://issues.apache.org/jira/browse/ATLAS-630
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Hemanth Yamijala
>Assignee: Hemanth Yamijala
>
> Start HA in active mode for the first time - when all dependent Graph stores 
> are being initialized the first time.
> Before the initialization completes, create a network partition such that the 
> active instance loses connection to Zookeeper. This could cause a split brain 
> scenario where the active instance does not stop the initialization and 
> another instance becomes active and starts initialization in parallel.
> This is only an issue for the very first initialization and the probability 
> of it happening is possibly very low.



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

[jira] [Updated] (ATLAS-590) HBaseBasedAuditRepository.start() fails

[Shwetha G S (JIRA)]

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

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

> HBaseBasedAuditRepository.start() fails
> ---
>
> Key: ATLAS-590
> URL: https://issues.apache.org/jira/browse/ATLAS-590
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
>
> The application doesn't fail, but prints this warning. Need to investigate
> {noformat}
> 2016-03-23 11:01:45,496 WARN  - [main:] ~ Failed to identify the fs of dir 
> hdfs://localhost.localdomain:8020/apps/hbase/data/lib, ignored 
> (DynamicClassLoader:106)
> java.io.IOException: No FileSystem for scheme: hdfs
> at 
> org.apache.hadoop.fs.FileSystem.getFileSystemClass(FileSystem.java:2644)
> at 
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2651)
> at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:92)
> at 
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2687)
> at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2669)
> at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:371)
> at org.apache.hadoop.fs.Path.getFileSystem(Path.java:295)
> at 
> org.apache.hadoop.hbase.util.DynamicClassLoader.(DynamicClassLoader.java:104)
> at 
> org.apache.hadoop.hbase.protobuf.ProtobufUtil.(ProtobufUtil.java:241)
> at org.apache.hadoop.hbase.ClusterId.parseFrom(ClusterId.java:64)
> at 
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:75)
> at 
> org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
> at 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:879)
> at 
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:635)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
> at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
> at 
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
> at 
> org.apache.atlas.repository.audit.HBaseBasedAuditRepository.start(HBaseBasedAuditRepository.java:257)
> at org.apache.atlas.service.Services.start(Services.java:45)
> at 
> org.apache.atlas.web.listeners.GuiceServletConfig.startServices(GuiceServletConfig.java:130)
> at 
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:124)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at 
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at 
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at 
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at 
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at 
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at 
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:93)
> at org.apache.atlas.Atlas.main(Atlas.java:107)
> 2016-03-23 11:01:45,555 INFO  - [main:] ~ Checking if table 
> ATLAS_ENTITY_AUDIT_EVENTS exists