Re: Review Request 62009: ATLAS-2101: Update Implementation to Eliminate Use of Stopwatch

2017-08-31 Thread Ashutosh Mestry 

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

(Updated Sept. 1, 2017, 1:47 a.m.)


Review request for atlas and Apoorv Naik.


Changes
---

Updates include:
- Added license header.


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


Repository: atlas


Description
---

**Details**
- Added _StandardIDPool_ to _Titan0_ Shaded JAR.
- Replace use of _Stopwatch_ with custom logic.


Diffs (updated)
-

  
graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
 PRE-CREATION 


Diff: https://reviews.apache.org/r/62009/diff/2/

Changes: https://reviews.apache.org/r/62009/diff/1-2/


Testing
---


Thanks,

Ashutosh Mestry

Re: Review Request 59821: ATLAS-1805:Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas

2017-08-31 Thread Ramesh Mani 

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

(Updated Aug. 31, 2017, 10:52 p.m.)


Review request for atlas and Madhan Neethiraj.


Changes
---

Patch after reviews


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


Repository: atlas


Description
---

ATLAS-1805: Provide an Atlas hook to send Hbase Namespace/Table/column family 
metadata to Atlas


Diffs (updated)
-

  addons/hbase-bridge-shim/pom.xml PRE-CREATION 
  
addons/hbase-bridge-shim/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
 PRE-CREATION 
  addons/hbase-bridge/pom.xml PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/event/HBaseEvent.java 
PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessorBase.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseContext.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseDataTypes.java
 PRE-CREATION 
  addons/hbase-bridge/src/main/resources/atlas-hbase-import-log4j.xml 
PRE-CREATION 
  
addons/hbase-bridge/src/test/java/org/apache/atlas/hbase/HBaseAtlasHookTest.java
 PRE-CREATION 
  addons/models/0060-hbase_model.json 3e46e06 
  distro/src/main/assemblies/standalone-package.xml 215cb23 
  pom.xml 8b9eee6 


Diff: https://reviews.apache.org/r/59821/diff/3/

Changes: https://reviews.apache.org/r/59821/diff/2-3/


Testing
---

* Review comments fixed with 2 exceptions whcih I have commented on 
* Added an IT test
* Testing done in LOCAL VM


Thanks,

Ramesh Mani

[jira] [Commented] (ATLAS-1690) Introduce top level relationships

2017-08-31 Thread Pierre Padovani (JIRA) 

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

Pierre Padovani commented on ATLAS-1690:


Two questions on this work:

1) Can a RelationshipType inherit from another RelationshipType?

2) If yes for #1, how does that affect tag propagation?

My use case: Given a set of metadata that belongs to a particular customer, 
where we use a classification with an attribute that contains the customer id, 
we would want that classification to propagate to all related entities. If we 
had a relationship type that was generic in nature and specified that the 
classification for the customer propagated, it would be nice to be able to 
specify sub-types that provide additional behaviors. 

> Introduce top level relationships
> -
>
> Key: ATLAS-1690
> URL: https://issues.apache.org/jira/browse/ATLAS-1690
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>  Labels: VirtualDataConnector
> Attachments: Atlas_RelationDef_Json_Structure_v1.pdf, Atlas 
> Relationships proposal v1.0.pdf, Atlas Relationships proposal v1.10.pdf, 
> Atlas Relationships proposal v1.1.pdf, Atlas Relationships proposal v1.2.pdf, 
> Atlas Relationships proposal v1.3.pdf, Atlas Relationships proposal v1.4.pdf, 
> Atlas Relationships proposal v1.5.pdf, Atlas Relationships proposal v1.6.pdf, 
> Atlas Relationships proposal v1.7.pdf, Atlas Relationships proposal v1.8.pdf, 
> Atlas Relationships proposal v1.9.pdf
>
>
> Introduce top level relationships including support for 
> -many to many relationships
> - relationship names including the name for both ends and the relationship.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Build failed in Jenkins: Atlas-0.8-IntegrationTests #38

2017-08-31 Thread Apache Jenkins Server 
See 


--
[...truncated 32.97 MB...]
2017-08-31 18:32:07,439 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[d99caa2d-bbc9-43db-b67e-ccdc42cb0f79] 
(GraphBackedMetadataRepository:179)
2017-08-31 18:32:07,439 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[b64ed909-827d-4c75-887b-15cc3b8c7064] 
(GraphBackedMetadataRepository:179)
2017-08-31 18:32:07,439 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[c18efcb2-1473-43e0-915c-bf8faa000582] 
(GraphBackedMetadataRepository:179)
2017-08-31 18:32:07,439 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[ae62af07-0968-448e-bd5a-78b2533da774] 
(GraphBackedMetadataRepository:179)
2017-08-31 18:32:07,509 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 
{"version":{"version":"1.0.0"},"message":{"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c465d3a8-b86c-4356-8458-1a4d258a7247","version":0,"typeName":"hive_db","state":"ACTIVE"},"typeName":"hive_db","values":{"name":"default","location":":"Default
 Hive 
database","ownerType":{"value":"ROLE","ordinal":2},"qualifiedName":"default@primary","owner":"public","clusterName":"primary"},"traitNames":[],"traits":{},"systemAttributes":{}},"operationType":"ENTITY_UPDATE","traits":[]}}
 (KafkaNotification:218)
2017-08-31 18:32:07,509 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 
{"version":{"version":"1.0.0"},"message":{"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c20ff0f3-a2de-46ca-acd5-a293269ade6a","version":0,"typeName":"hive_table","state":"ACTIVE"},"typeName":"hive_table","values":{"tableType":"EXTERNAL_TABLE","name":"tablegrrjapqmwu","createTime":"2017-08-31T18:30:26.000Z","temporary":false,"db":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c465d3a8-b86c-4356-8458-1a4d258a7247","version":0,"typeName":"hive_db","state":"ACTIVE"},"retention":0,"qualifiedName":"default.tablegrrjapqmwu@primary","columns":[{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"d99caa2d-bbc9-43db-b67e-ccdc42cb0f79","version":0,"typeName":"hive_column","state":"ACTIVE"},"typeName":"hive_column","values":{"name":"id","qualifiedName":"default.tablegrrjapqmwu.id@primary","position":0,"owner":"jenkins","type":"int","table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c20ff0f3-a2de-46ca-acd5-a293269ade6a","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-08-31T18:32:01.998Z","modifiedTime":"2017-08-31T18:32:06.518Z"}},{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"b64ed909-827d-4c75-887b-15cc3b8c7064","version":0,"typeName":"hive_column","state":"ACTIVE"},"typeName":"hive_column","values":{"name":"name","qualifiedName":"default.tablegrrjapqmwu.name@primary","position":1,"owner":"jenkins","type":"string","table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c20ff0f3-a2de-46ca-acd5-a293269ade6a","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-08-31T18:32:01.998Z","modifiedTime":"2017-08-31T18:32:06.518Z"}}],"comment":"table

Re: Review Request 62009: ATLAS-2101: Update Implementation to Eliminate Use of Stopwatch

2017-08-31 Thread Sarath Subramanian 

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


Ship it!




Ship It!

- Sarath Subramanian


On Aug. 30, 2017, 10:02 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62009/
> ---
> 
> (Updated Aug. 30, 2017, 10:02 p.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2101
> https://issues.apache.org/jira/browse/ATLAS-2101
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Details**
> - Added _StandardIDPool_ to _Titan0_ Shaded JAR.
> - Replace use of _Stopwatch_ with custom logic.
> 
> 
> Diffs
> -
> 
>   
> graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62009/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 62009: ATLAS-2101: Update Implementation to Eliminate Use of Stopwatch

2017-08-31 Thread Sarath Subramanian 

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




graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
Lines 1 (patched)


Need to add apache license header. getting rat failure.


- Sarath Subramanian


On Aug. 30, 2017, 10:02 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62009/
> ---
> 
> (Updated Aug. 30, 2017, 10:02 p.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2101
> https://issues.apache.org/jira/browse/ATLAS-2101
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Details**
> - Added _StandardIDPool_ to _Titan0_ Shaded JAR.
> - Replace use of _Stopwatch_ with custom logic.
> 
> 
> Diffs
> -
> 
>   
> graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62009/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 62009: ATLAS-2101: Update Implementation to Eliminate Use of Stopwatch

2017-08-31 Thread Apoorv Naik 


> On Aug. 31, 2017, 5:48 p.m., Apoorv Naik wrote:
> > Ship It!

I'll commit once I review/test some scenarios. Code wise the changes look good.


- Apoorv


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


On Aug. 31, 2017, 5:02 a.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62009/
> ---
> 
> (Updated Aug. 31, 2017, 5:02 a.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2101
> https://issues.apache.org/jira/browse/ATLAS-2101
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Details**
> - Added _StandardIDPool_ to _Titan0_ Shaded JAR.
> - Replace use of _Stopwatch_ with custom logic.
> 
> 
> Diffs
> -
> 
>   
> graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62009/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 62009: ATLAS-2101: Update Implementation to Eliminate Use of Stopwatch

2017-08-31 Thread Apoorv Naik 

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


Ship it!




Ship It!

- Apoorv Naik


On Aug. 31, 2017, 5:02 a.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62009/
> ---
> 
> (Updated Aug. 31, 2017, 5:02 a.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2101
> https://issues.apache.org/jira/browse/ATLAS-2101
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Details**
> - Added _StandardIDPool_ to _Titan0_ Shaded JAR.
> - Replace use of _Stopwatch_ with custom logic.
> 
> 
> Diffs
> -
> 
>   
> graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62009/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

[jira] [Updated] (ATLAS-2092) Failures following concurrent updates

2017-08-31 Thread Ashutosh Mestry (JIRA) 

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

Ashutosh Mestry updated ATLAS-2092:
---
Attachment: import-nested-txn.patch

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
> Attachments: import-nested-txn.patch, Investigations and findings 
> relating to concurrent updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (ATLAS-2092) Failures following concurrent updates

2017-08-31 Thread Ashutosh Mestry (JIRA) 

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

Ashutosh Mestry edited comment on ATLAS-2092 at 8/31/17 4:45 PM:
-

[~grahamwallis] I am reading the PDF now. Analysis is comprehensive and I find 
it interesting read. Thanks for putting this together!

One thing we have noticed is that version of _Berkeley DB_ we are using has a 
few problems.  Mostly around transactions commits. Only yesterday we were 
contemplating on effort required to move our tests to use embedded HBASE and 
embedded Solr. We have not reached any conclusion yet. Doing this would help us 
get around some of the intermittent failures we see in test environments. It 
will also make our unit & IT tests run in an environment that is close to 
production.

How easy is it for you to duplicate this problem on HBASE/Solr setup? It would 
be interesting to see the results.

About 'double wrapping of transactions' (Appendix, Observation 2). I had worked 
on trying to resolve it. Please find patch attached.


was (Author: ashutoshm):
[~grahamwallis] I am reading the PDF now. Analysis is comprehensive and I find 
it interesting read. Thanks for putting this together!

One thing we have noticed is that version of _Berkeley DB_ we are using has a 
few problems.  Mostly around transactions commits. Only yesterday we were 
contemplating on effort required to move our tests to use embedded HBASE and 
embedded Solr. We have not reached any conclusion yet. Doing this would help us 
get around some of the intermittent failures we see in test environments. It 
will also make our unit & IT tests run in an environment that is close to 
production.

How easy is it for you to duplicate this problem on HBASE/Solr setup? It would 
be interesting to see the results.

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
> Attachments: Investigations and findings relating to concurrent 
> updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2092) Failures following concurrent updates

2017-08-31 Thread Nigel Jones (JIRA) 

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

Nigel Jones commented on ATLAS-2092:


thanks for the very thorough write-up and walk through.

In terms of resolution a little thinking 'out-loud'

* At the point we switch to janus and drop titan 0.54 we ideally don't want any 
workarounds in that version of the code, but we may need to make sure we 
address any odd things in the graph during a migration step?
* You mention that fixing titan 0.54 is unrealistic. I understand there is no 
longer any support/activity, it's a dead end. However if it is a small, precise 
change that is required, I still wonder if could build a patch that can be 
applied to 0.54, and ship it with atlas. We could also ensure the libraries we 
supply have it included (needs a build), and perhaps detect on startup, and log 
an error if patch isn't in place. Though this is a bit tedious, I still wonder 
if it's safer or more controlled than adding a fair bit of workaround code. may 
be worth thinking about?
* However in the case of any fix (as in previous point) am I right in thinking 
once this has occurred it may continue to cause functional issues since the key 
will always be out of the correct range? In which case we'd still either need 
to be able to detect, and/or self-heal/fix on demand, or have a fix-script 
available for old atlas users? this may make my previous point somewhat mute.

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
> Attachments: Investigations and findings relating to concurrent 
> updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2092) Failures following concurrent updates

2017-08-31 Thread Graham Wallis (JIRA) 

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

Graham Wallis commented on ATLAS-2092:
--

Hi Ashutosh,
That's weird - I am sure I attached the details to this issue immediately after 
the call on Tuesday - but I don't see it - let me try again :-)

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Build failed in Jenkins: Atlas-0.8-IntegrationTests #37

2017-08-31 Thread Apache Jenkins Server 
See 


Changes:

[amestry] ATLAS-2047: Exception Thrown by Kafka Consumer Ends up Filling Logs 
Due

--
[...truncated 30.90 MB...]
2017-08-31 06:02:11,350 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[374de30c-112f-4a37-91c8-61bcbcdda8fd] 
(GraphBackedMetadataRepository:179)
2017-08-31 06:02:11,385 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 
{"version":{"version":"1.0.0"},"message":{"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"e56962d9-5004-4c32-b7c0-3635a98bfb1a","version":0,"typeName":"hive_table","state":"ACTIVE"},"typeName":"hive_table","values":{"tableType":"EXTERNAL_TABLE","name":"tableie8myts9pe","createTime":"2017-08-31T06:00:20.000Z","temporary":false,"db":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"84ee00af-e5e5-4163-894e-4e68a3355c73","version":0,"typeName":"hive_db","state":"ACTIVE"},"retention":0,"qualifiedName":"default.tableie8myts9pe@primary","columns":[{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"a6849ee5-f1d5-4b05-bdd0-af9295d6a12f","version":0,"typeName":"hive_column","state":"ACTIVE"},"typeName":"hive_column","values":{"name":"id","qualifiedName":"default.tableie8myts9pe.id@primary","position":0,"owner":"jenkins","type":"int","table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"e56962d9-5004-4c32-b7c0-3635a98bfb1a","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-08-31T06:02:09.873Z","modifiedTime":"2017-08-31T06:02:09.873Z"}},{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"424d6e1d-5c3e-429b-a81d-1b313a79c861","version":0,"typeName":"hive_column","state":"ACTIVE"},"typeName":"hive_column","values":{"name":"name","qualifiedName":"default.tableie8myts9pe.name@primary","position":1,"owner":"jenkins","type":"string","table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"e56962d9-5004-4c32-b7c0-3635a98bfb1a","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-08-31T06:02:09.873Z","modifiedTime":"2017-08-31T06:02:09.873Z"}}],"comment":"table
 
comment","lastAccessTime":"2017-08-31T06:00:20.000Z","owner":"jenkins","sd":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"426aba0a-59c3-40f1-a018-2fe76e589db0","version":0,"typeName":"hive_storagedesc","state":"ACTIVE"},"typeName":"hive_storagedesc","values":{"location":"p:{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct","typeName":"hive_serde","values":{"serializationLib":"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe","parameters":{"serialization.format":"1"}}},"qualifiedName":"default.tableie8myts9pe@primary_storage","outputFormat":"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat","compressed":false,"numBuckets":-1,"inputFormat":"org.apache.hadoop.mapred.TextInputFormat","storedAsSubDirectories":false,"table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"e56962d9-5004-4c32-b7c0-3635a98bfb1a","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-08-31T06:02:09.873Z","modifiedTime":"2017-08-31T06:02:09.873Z"}},"parameters":{"comment":"table