[jira] [Updated] (ATLAS-2608) UI - Cache is not cleared if user click on cancel button while editing propagation flow

[Tejas Rawool (JIRA)]

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

Tejas Rawool updated ATLAS-2608:

Summary: UI - Cache is not cleared if user click on cancel button while 
editing propagation flow  (was: UI - Cached is not cleared if user click on 
cancel button while editing propagation flow)

> UI - Cache is not cleared if user click on cancel button while editing 
> propagation flow
> ---
>
> Key: ATLAS-2608
> URL: https://issues.apache.org/jira/browse/ATLAS-2608
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Tejas Rawool
>Priority: Major
> Fix For: 1.0.0
>
>
> Steps to reproduce:-
>  
> 1.Do a Basic Search for Tables
> 2.Now go to Lineage Tab of  sales_fact
> 3.Click on arrow between sales_fact and loadSalesDaily
> 4.Now switch to Block Propagation
> 5.Checked any of the entity and click on cancel button
> 6.Now again click on that arrow and go to block propagation without 
> refreshing the page
> Error:-
> An Duplicate entity is created which is incorrect



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

[jira] [Updated] (ATLAS-2608) UI - Cached is not cleared if user click on cancel button while editing propagation flow

[Tejas Rawool (JIRA)]

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

Tejas Rawool updated ATLAS-2608:

Summary: UI - Cached is not cleared if user click on cancel button while 
editing propagation flow  (was: UI - Cashed is not cleared if user click on 
cancel button while editing propagation flow)

> UI - Cached is not cleared if user click on cancel button while editing 
> propagation flow
> 
>
> Key: ATLAS-2608
> URL: https://issues.apache.org/jira/browse/ATLAS-2608
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Tejas Rawool
>Priority: Major
> Fix For: 1.0.0
>
>
> Steps to reproduce:-
>  
> 1.Do a Basic Search for Tables
> 2.Now go to Lineage Tab of  sales_fact
> 3.Click on arrow between sales_fact and loadSalesDaily
> 4.Now switch to Block Propagation
> 5.Checked any of the entity and click on cancel button
> 6.Now again click on that arrow and go to block propagation without 
> refreshing the page
> Error:-
> An Duplicate entity is created which is incorrect



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

[jira] [Created] (ATLAS-2608) UI - Cashed is not cleared if user click on cancel button while editing propagation flow

[Tejas Rawool (JIRA)]

Tejas Rawool created ATLAS-2608:
---

 Summary: UI - Cashed is not cleared if user click on cancel button 
while editing propagation flow
 Key: ATLAS-2608
 URL: https://issues.apache.org/jira/browse/ATLAS-2608
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Tejas Rawool
 Fix For: 1.0.0


Steps to reproduce:-

 

1.Do a Basic Search for Tables

2.Now go to Lineage Tab of  sales_fact

3.Click on arrow between sales_fact and loadSalesDaily

4.Now switch to Block Propagation

5.Checked any of the entity and click on cancel button

6.Now again click on that arrow and go to block propagation without refreshing 
the page

Error:-

An Duplicate entity is created which is incorrect



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

[jira] [Assigned] (ATLAS-2607) Classification lifecycle through metadata properties and relationships

[Srikanth Venkat (JIRA)]

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

Srikanth Venkat reassigned ATLAS-2607:
--

Assignee: Madhan Neethiraj

> Classification lifecycle through metadata properties and relationships
> --
>
> Key: ATLAS-2607
> URL: https://issues.apache.org/jira/browse/ATLAS-2607
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Reporter: Srikanth Venkat
>Assignee: Madhan Neethiraj
>Priority: Critical
>
> Currently tags or classifications in Atlas are considered active once they 
> are defined. For governance and stewardship purposes, it would be important 
> to attach the notion of what state in its lifecycle a particular 
> classification is. This would help with workflows to manage the lifecycle 
> aspects and provide any filtering needed to take appropriate actions. For 
> example only active classifications should be considered for classification 
> based policy enforcement. Additionally lifecycle status would help with 
> filtering and search as well as reporting and compliance/audit scenarios.
> Implementation Proposal:
>  * All tags or classifications have a "Lifecycle Status" property
>  * They can go through the following list of states during their lifecycle: 
> DRAFT -> ACTIVE  -> RETIRED
>  * Lifecycle Status can be set as an enum property that is mandatory or 
> required for all classifications.
>  * All existing classifications already present in Atlas before this change 
> will default to an ACTIVE status so that all pre-existing classifications 
> will continue to work as before.
>  * All new classifications after this change will start out with DRAFT status 
> and a steward or an admin with appropriate permissions can move them into an 
> ACTIVE state (controlled via Metadata security policies)
>  * Policy enforcement for authorization on classifications can ignore any 
> that are not in ACTIVE state. 
>  * Asset can only be attached to classifications with the status of ACTIVE
>  * For a classification in RETIRED state, we might have an optional 
> relationship with another classification called "Replaced By" which is the 
> new classification that the current one was remapped or replaced with. The 
> inverse relationship could be labeled "Replaces" which is on the new 
> classification and points to the removed classification that it replaces. 
>  * The state RETIRED implies this classification is no longer used and policy 
> enforcement will ignore any classifications in such states. 
>  * Additionally UI can filter and show by default only classifications that 
> are not RETIRED and a checkbox to "Show Retired"
>  * Deletion of classifications should work as it currently does with no 
> behavioral changes.
>  



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

[jira] [Created] (ATLAS-2607) Classification lifecycle through metadata properties and relationships

[Srikanth Venkat (JIRA)]

Srikanth Venkat created ATLAS-2607:
--

 Summary: Classification lifecycle through metadata properties and 
relationships
 Key: ATLAS-2607
 URL: https://issues.apache.org/jira/browse/ATLAS-2607
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Reporter: Srikanth Venkat


Currently tags or classifications in Atlas are considered active once they are 
defined. For governance and stewardship purposes, it would be important to 
attach the notion of what state in its lifecycle a particular classification 
is. This would help with workflows to manage the lifecycle aspects and provide 
any filtering needed to take appropriate actions. For example only active 
classifications should be considered for classification based policy 
enforcement. Additionally lifecycle status would help with filtering and search 
as well as reporting and compliance/audit scenarios.

Implementation Proposal:
 * All tags or classifications have a "Lifecycle Status" property
 * They can go through the following list of states during their lifecycle: 
DRAFT -> ACTIVE  -> RETIRED
 * Lifecycle Status can be set as an enum property that is mandatory or 
required for all classifications.
 * All existing classifications already present in Atlas before this change 
will default to an ACTIVE status so that all pre-existing classifications will 
continue to work as before.
 * All new classifications after this change will start out with DRAFT status 
and a steward or an admin with appropriate permissions can move them into an 
ACTIVE state (controlled via Metadata security policies)
 * Policy enforcement for authorization on classifications can ignore any that 
are not in ACTIVE state. 
 * Asset can only be attached to classifications with the status of ACTIVE
 * For a classification in RETIRED state, we might have an optional 
relationship with another classification called "Replaced By" which is the new 
classification that the current one was remapped or replaced with. The inverse 
relationship could be labeled "Replaces" which is on the new classification and 
points to the removed classification that it replaces. 
 * The state RETIRED implies this classification is no longer used and policy 
enforcement will ignore any classifications in such states. 
 * Additionally UI can filter and show by default only classifications that are 
not RETIRED and a checkbox to "Show Retired"
 * Deletion of classifications should work as it currently does with no 
behavioral changes.

 



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

Re: Review Request 66785: ATLAS-2603: [Docs] Add Atlas Kafka Bridge Documents

[Madhan Neethiraj]

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




docs/src/site/twiki/Bridge-Kafka.twiki
Lines 23 (patched)


import-Kafka.sh ==> import-kafka.sh (lower case 'k')



docs/src/site/twiki/Bridge-Kafka.twiki
Lines 34 (patched)


Since this is a bridge, notifications are not relevant. Please remove this 
line.



docs/src/site/twiki/Bridge-Kafka.twiki
Lines 37 (patched)


'NOTES' section doesn't seem to add much value. Please consider removing it.


- Madhan Neethiraj


On April 24, 2018, 10:46 p.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66785/
> ---
> 
> (Updated April 24, 2018, 10:46 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2603
> https://issues.apache.org/jira/browse/ATLAS-2603
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2603: [Docs] Add Atlas Kafka Bridge Documents
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/Bridge-Kafka.twiki PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/66785/diff/2/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ramesh Mani
> 
>

Re: Review Request 66791: Import: Fix for Glossary Terms

[Madhan Neethiraj]

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




repository/src/main/java/org/apache/atlas/repository/store/graph/v1/BulkImporterImpl.java
Line 76 (original)


if 'entity == null', line #79 will result in NPE. It will be safe to 
'continue' in this case.


- Madhan Neethiraj


On April 24, 2018, 11:15 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66791/
> ---
> 
> (Updated April 24, 2018, 11:15 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2602
> https://issues.apache.org/jira/browse/ATLAS-2602
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Background**
> During entity creation, has a pre-create phase that discovers entities that 
> need to be created within _AtlasEntity_. For import, this discovery was 
> ignoring the entities present within relationship attribute.
> 
> **Fix**
> The fix removes the condition.
> 
> 
> Diffs
> -
> 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityGraphDiscoveryV1.java
>  f092d1847 
>   
> repository/src/main/java/org/apache/atlas/repository/store/graph/v1/BulkImporterImpl.java
>  af310954f 
>   
> repository/src/test/java/org/apache/atlas/repository/impexp/ImportServiceTest.java
>  91d56ab80 
>   repository/src/test/resources/stocks-glossary.zip PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/66791/diff/1/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> - New unit tests cover this case.
> - Additional checks added using EntityDiscovery to query the Graph with known 
> guids after import succeeds.
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

[jira] [Commented] (ATLAS-2606) Graph shutdown called twice when Atlas is shutting down

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry commented on ATLAS-2606:


+1 for patch

> Graph shutdown called twice when Atlas is shutting down
> ---
>
> Key: ATLAS-2606
> URL: https://issues.apache.org/jira/browse/ATLAS-2606
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: 0001-ATLAS-2606-Graph-shutdown-fix.patch
>
>
> The Graph database registers a shutdown hook and spring infers the destroy 
> method bean, the shutdown hook registered with JVM kicks in after the spring 
> bean destruction which causes this error to be reported in the logs
>  
> {noformat}
> 2018-04-24 15:16:51,443 WARN  - [Thread-0:] ~ Failed to remove shutdown hook 
> (StandardJanusGraph:262)
> java.lang.IllegalStateException: Shutdown in progress
>     at 
> java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82)
>     at java.lang.Runtime.removeShutdownHook(Runtime.java:239)
>     at 
> org.janusgraph.graphdb.database.StandardJanusGraph.removeHook(StandardJanusGraph.java:259)
>     at 
> org.janusgraph.graphdb.database.StandardJanusGraph.close(StandardJanusGraph.java:193)
>     at 
> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.shutdown(AtlasJanusGraph.java:211)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
> {noformat}



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

[jira] [Updated] (ATLAS-2606) Graph shutdown called twice when Atlas is shutting down

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated ATLAS-2606:
---
Attachment: 0001-ATLAS-2606-Graph-shutdown-fix.patch

> Graph shutdown called twice when Atlas is shutting down
> ---
>
> Key: ATLAS-2606
> URL: https://issues.apache.org/jira/browse/ATLAS-2606
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: 0001-ATLAS-2606-Graph-shutdown-fix.patch
>
>
> The Graph database registers a shutdown hook and spring infers the destroy 
> method bean, the shutdown hook registered with JVM kicks in after the spring 
> bean destruction which causes this error to be reported in the logs
>  
> {noformat}
> 2018-04-24 15:16:51,443 WARN  - [Thread-0:] ~ Failed to remove shutdown hook 
> (StandardJanusGraph:262)
> java.lang.IllegalStateException: Shutdown in progress
>     at 
> java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82)
>     at java.lang.Runtime.removeShutdownHook(Runtime.java:239)
>     at 
> org.janusgraph.graphdb.database.StandardJanusGraph.removeHook(StandardJanusGraph.java:259)
>     at 
> org.janusgraph.graphdb.database.StandardJanusGraph.close(StandardJanusGraph.java:193)
>     at 
> org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.shutdown(AtlasJanusGraph.java:211)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke(Method.java:498)
> {noformat}



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

Review Request 66791: Import: Fix for Glossary Terms

[Ashutosh Mestry]

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

Review request for atlas, Madhan Neethiraj and Sarath Subramanian.


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


Repository: atlas


Description
---

**Background**
During entity creation, has a pre-create phase that discovers entities that 
need to be created within _AtlasEntity_. For import, this discovery was 
ignoring the entities present within relationship attribute.

**Fix**
The fix removes the condition.


Diffs
-

  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityGraphDiscoveryV1.java
 f092d1847 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/BulkImporterImpl.java
 af310954f 
  
repository/src/test/java/org/apache/atlas/repository/impexp/ImportServiceTest.java
 91d56ab80 
  repository/src/test/resources/stocks-glossary.zip PRE-CREATION 


Diff: https://reviews.apache.org/r/66791/diff/1/


Testing
---

**Unit tests**
- New unit tests cover this case.
- Additional checks added using EntityDiscovery to query the Graph with known 
guids after import succeeds.


Thanks,

Ashutosh Mestry

[jira] [Updated] (ATLAS-2602) Import: Glossary Import Does not Display Imported Entities

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry updated ATLAS-2602:
---
Attachment: ATLAS-2602-Walkthrough-includes-relationship-attribu.patch

> Import: Glossary Import Does not Display Imported Entities
> --
>
> Key: ATLAS-2602
> URL: https://issues.apache.org/jira/browse/ATLAS-2602
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk, 1.0.0
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Major
> Fix For: trunk
>
> Attachments: 
> ATLAS-2602-Walkthrough-includes-relationship-attribu.patch
>
>
> *Pre-requisites*
>  * Create Glossary hierarchy with few terms.
>  * Export to ZIP using Atlas Export.
> *Steps to Duplicate*
>  * Import the file create in previous step.
>  * Open Atlas Web UI and navigate to Glossary tab. 
> _Expected:_ All terms created are visible.
> _Actual_: Few of the terms will be visible from in the tab.
> _Additional information:_  Using JanusGraph Gremlin shell, it appears that 
> the vertices are created but the edges (containing relationships) are missing.
>  
>  



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

Re: Review Request 66785: ATLAS-2603: [Docs] Add Atlas Kafka Bridge Documents

[Ramesh Mani]

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

(Updated April 24, 2018, 10:46 p.m.)


Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath Subramanian.


Changes
---

Change made to document


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


Repository: atlas


Description
---

ATLAS-2603: [Docs] Add Atlas Kafka Bridge Documents


Diffs (updated)
-

  docs/src/site/twiki/Bridge-Kafka.twiki PRE-CREATION 


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

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


Testing
---


Thanks,

Ramesh Mani

[jira] [Updated] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents

[Ramesh Mani (JIRA)]

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

Ramesh Mani updated ATLAS-2603:
---
Attachment: 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents_002.patch

> [Docs] Add Atlas Kafka Bridge Documents
> ---
>
> Key: ATLAS-2603
> URL: https://issues.apache.org/jira/browse/ATLAS-2603
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 
> 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents.patch, 
> 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents_002.patch
>
>
> [Docs] Add Atlas Kafka Bridge Documents



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

Re: Review Request 66783: ATLAS-2317:[Docs] Add HBase Bridge Documents

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On April 24, 2018, 9:04 p.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66783/
> ---
> 
> (Updated April 24, 2018, 9:04 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2317:[Docs] Add HBase Bridge Documents
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/Bridge-HBase.twiki PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/66783/diff/3/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ramesh Mani
> 
>

[jira] [Created] (ATLAS-2606) Graph shutdown called twice when Atlas is shutting down

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-2606:
--

 Summary: Graph shutdown called twice when Atlas is shutting down
 Key: ATLAS-2606
 URL: https://issues.apache.org/jira/browse/ATLAS-2606
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0-alpha
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: 1.0.0


The Graph database registers a shutdown hook and spring infers the destroy 
method bean, the shutdown hook registered with JVM kicks in after the spring 
bean destruction which causes this error to be reported in the logs

 
{noformat}
2018-04-24 15:16:51,443 WARN  - [Thread-0:] ~ Failed to remove shutdown hook 
(StandardJanusGraph:262)
java.lang.IllegalStateException: Shutdown in progress
    at 
java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82)
    at java.lang.Runtime.removeShutdownHook(Runtime.java:239)
    at 
org.janusgraph.graphdb.database.StandardJanusGraph.removeHook(StandardJanusGraph.java:259)
    at 
org.janusgraph.graphdb.database.StandardJanusGraph.close(StandardJanusGraph.java:193)
    at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusGraph.shutdown(AtlasJanusGraph.java:211)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
{noformat}



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

[jira] [Created] (ATLAS-2605) Drop Titan 0 support

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-2605:
--

 Summary: Drop Titan 0 support
 Key: ATLAS-2605
 URL: https://issues.apache.org/jira/browse/ATLAS-2605
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 1.0.0-alpha
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: 1.0.0


Since the titan 0 project is no longer maintained and Atlas 1.0 is moving 
towards JanusGraph which is much active and an improvement over Titan 1



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

Re: Review Request 66785: ATLAS-2603: [Docs] Add Atlas Kafka Bridge Documents

[Apoorv Naik]

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


Ship it!




Ship It!

- Apoorv Naik


On April 24, 2018, 8:48 p.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66785/
> ---
> 
> (Updated April 24, 2018, 8:48 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2603
> https://issues.apache.org/jira/browse/ATLAS-2603
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2603: [Docs] Add Atlas Kafka Bridge Documents
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/Bridge-Kafka.twiki PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/66785/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ramesh Mani
> 
>

Re: Review Request 66784: ATLAS2604 Minor fixups to open metadata archive types

[Mandy Chessell]

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




omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java
Line 10962 (original), 10962 (patched)


attributesTypedBy is clearer



omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java
Line 10963 (original), 10963 (patched)


The description should be a sentence in English.  This means it starts with 
a captial letter and does not include camel-case words.  I would keep the 
description the same.


- Mandy Chessell


On April 24, 2018, 8:48 p.m., David Radley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66784/
> ---
> 
> (Updated April 24, 2018, 8:48 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Mandy Chessell.
> 
> 
> Bugs: ATLAS2604
> https://issues.apache.org/jira/browse/ATLAS2604
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS2604 Minor fixups to open metadata archive types to avoid duplicate 
> attributes due to relationship end names.
> 
> 
> Diffs
> -
> 
>   
> omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java
>  faab96cac 
>   
> omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/66784/diff/1/
> 
> 
> Testing
> ---
> 
> Ran junit that failed without the patch applied. I ran this in Intellij using 
> the  Maven view to run the test phase on the OMRS module. This successfully 
> ran the test.
> 
> 
> Thanks,
> 
> David Radley
> 
>

Re: Review Request 66783: ATLAS-2317:[Docs] Add HBase Bridge Documents

[Ramesh Mani]

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

(Updated April 24, 2018, 9:04 p.m.)


Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath Subramanian.


Changes
---

Fixed review comments


Repository: atlas


Description
---

ATLAS-2317:[Docs] Add HBase Bridge Documents


Diffs (updated)
-

  docs/src/site/twiki/Bridge-HBase.twiki PRE-CREATION 


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

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


Testing
---


Thanks,

Ramesh Mani

Re: Review Request 66783: ATLAS-2317:[Docs] Add HBase Bridge Documents

[Ramesh Mani]

> On April 24, 2018, 8:36 p.m., Madhan Neethiraj wrote:
> > docs/src/site/twiki/Bridge-HBase.twiki
> > Lines 7 (patched)
> > 
> >
> > Similar to hive_db, hbase_namespace should be an Asset not a DataSet. 
> > Please review and update (the code).

I shall take care of the code update in separate JIRA.


- Ramesh


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


On April 24, 2018, 9:04 p.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66783/
> ---
> 
> (Updated April 24, 2018, 9:04 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2317:[Docs] Add HBase Bridge Documents
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/Bridge-HBase.twiki PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/66783/diff/3/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ramesh Mani
> 
>

[jira] [Updated] (ATLAS-2604) Minor fixups for relationshipdefs in the open metadata archive

[David Radley (JIRA)]

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

David Radley updated ATLAS-2604:

Description: Some relationships were introducing the same attribute name 
into an entity type. This Jira is to change the relationshipdefs so all the 
entitydef attributes are unique.  (was: Some relationships were introducing the 
same attribute name into an entity type. This Jira is to change the 
relationships so all the entity attributes are unique.)

> Minor fixups for relationshipdefs in the open metadata archive 
> ---
>
> Key: ATLAS-2604
> URL: https://issues.apache.org/jira/browse/ATLAS-2604
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
> Attachments: ATLAS2604.patch
>
>
> Some relationships were introducing the same attribute name into an entity 
> type. This Jira is to change the relationshipdefs so all the entitydef 
> attributes are unique.



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

[jira] [Updated] (ATLAS-2604) Minor fixups for relationshipdefs in the open metadata archive

[David Radley (JIRA)]

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

David Radley updated ATLAS-2604:

Description: Some relationships were introducing the same attribute name 
into an entity type. This Jira is to change the relationships so all the entity 
attributes are unique.

> Minor fixups for relationshipdefs in the open metadata archive 
> ---
>
> Key: ATLAS-2604
> URL: https://issues.apache.org/jira/browse/ATLAS-2604
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
>
> Some relationships were introducing the same attribute name into an entity 
> type. This Jira is to change the relationships so all the entity attributes 
> are unique.



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

[jira] [Updated] (ATLAS-2317) [Docs] Add HBase Bridge Documents

[Ramesh Mani (JIRA)]

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

Ramesh Mani updated ATLAS-2317:
---
Fix Version/s: 1.0.0

> [Docs] Add HBase Bridge Documents
> -
>
> Key: ATLAS-2317
> URL: https://issues.apache.org/jira/browse/ATLAS-2317
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1
>Reporter: ShuMing Li
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch
>
>
> Since HBase Bridge has been already 
> supported(https://issues.apache.org/jira/browse/ATLAS-1805), We should update 
> index 
> docs(https://github.com/apache/atlas/blob/master/docs/src/site/twiki/index.twiki)
>  to add HBase Config knowledge.



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

[jira] [Updated] (ATLAS-2604) Minor fixups for relationshipdefs in the open metadata archive

[David Radley (JIRA)]

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

David Radley updated ATLAS-2604:

Attachment: ATLAS2604.patch

> Minor fixups for relationshipdefs in the open metadata archive 
> ---
>
> Key: ATLAS-2604
> URL: https://issues.apache.org/jira/browse/ATLAS-2604
> Project: Atlas
>  Issue Type: Bug
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
> Attachments: ATLAS2604.patch
>
>
> Some relationships were introducing the same attribute name into an entity 
> type. This Jira is to change the relationships so all the entity attributes 
> are unique.



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

[jira] [Updated] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents

[Ramesh Mani (JIRA)]

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

Ramesh Mani updated ATLAS-2603:
---
Fix Version/s: 1.0.0

> [Docs] Add Atlas Kafka Bridge Documents
> ---
>
> Key: ATLAS-2603
> URL: https://issues.apache.org/jira/browse/ATLAS-2603
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 
> 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents.patch
>
>
> [Docs] Add Atlas Kafka Bridge Documents



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

Review Request 66785: ATLAS-2603: [Docs] Add Atlas Kafka Bridge Documents

[Ramesh Mani]

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

Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath Subramanian.


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


Repository: atlas


Description
---

ATLAS-2603: [Docs] Add Atlas Kafka Bridge Documents


Diffs
-

  docs/src/site/twiki/Bridge-Kafka.twiki PRE-CREATION 


Diff: https://reviews.apache.org/r/66785/diff/1/


Testing
---


Thanks,

Ramesh Mani

Review Request 66784: ATLAS2604 Minor fixups to open metadata archive types

[David Radley]

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

Review request for atlas, Madhan Neethiraj and Mandy Chessell.


Bugs: ATLAS2604
https://issues.apache.org/jira/browse/ATLAS2604


Repository: atlas


Description
---

ATLAS2604 Minor fixups to open metadata archive types to avoid duplicate 
attributes due to relationship end names.


Diffs
-

  
omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java
 faab96cac 
  
omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java
 PRE-CREATION 


Diff: https://reviews.apache.org/r/66784/diff/1/


Testing
---

Ran junit that failed without the patch applied. I ran this in Intellij using 
the  Maven view to run the test phase on the OMRS module. This successfully ran 
the test.


Thanks,

David Radley

[jira] [Updated] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents

[Ramesh Mani (JIRA)]

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

Ramesh Mani updated ATLAS-2603:
---
Attachment: 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents.patch

> [Docs] Add Atlas Kafka Bridge Documents
> ---
>
> Key: ATLAS-2603
> URL: https://issues.apache.org/jira/browse/ATLAS-2603
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Attachments: 
> 0001-ATLAS-2603-Docs-Add-Atlas-Kafka-Bridge-Documents.patch
>
>
> [Docs] Add Atlas Kafka Bridge Documents



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

[jira] [Updated] (ATLAS-2317) [Docs] Add HBase Bridge Documents

[Ramesh Mani (JIRA)]

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

Ramesh Mani updated ATLAS-2317:
---
Attachment: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch

> [Docs] Add HBase Bridge Documents
> -
>
> Key: ATLAS-2317
> URL: https://issues.apache.org/jira/browse/ATLAS-2317
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1
>Reporter: ShuMing Li
>Assignee: Ramesh Mani
>Priority: Major
> Attachments: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch
>
>
> Since HBase Bridge has been already 
> supported(https://issues.apache.org/jira/browse/ATLAS-1805), We should update 
> index 
> docs(https://github.com/apache/atlas/blob/master/docs/src/site/twiki/index.twiki)
>  to add HBase Config knowledge.



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

[jira] [Updated] (ATLAS-2317) [Docs] Add HBase Bridge Documents

[Ramesh Mani (JIRA)]

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

Ramesh Mani updated ATLAS-2317:
---
Attachment: (was: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch)

> [Docs] Add HBase Bridge Documents
> -
>
> Key: ATLAS-2317
> URL: https://issues.apache.org/jira/browse/ATLAS-2317
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1
>Reporter: ShuMing Li
>Assignee: Ramesh Mani
>Priority: Major
> Attachments: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch
>
>
> Since HBase Bridge has been already 
> supported(https://issues.apache.org/jira/browse/ATLAS-1805), We should update 
> index 
> docs(https://github.com/apache/atlas/blob/master/docs/src/site/twiki/index.twiki)
>  to add HBase Config knowledge.



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

Re: Review Request 66783: ATLAS-2317:[Docs] Add HBase Bridge Documents

[Ramesh Mani]

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

(Updated April 24, 2018, 8:36 p.m.)


Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath Subramanian.


Changes
---

Made a minor modification.


Repository: atlas


Description
---

ATLAS-2317:[Docs] Add HBase Bridge Documents


Diffs (updated)
-

  docs/src/site/twiki/Bridge-HBase.twiki PRE-CREATION 


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

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


Testing
---


Thanks,

Ramesh Mani

Re: Review Request 66783: ATLAS-2317:[Docs] Add HBase Bridge Documents

[Madhan Neethiraj]

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




docs/src/site/twiki/Bridge-HBase.twiki
Lines 7 (patched)


Similar to hive_db, hbase_namespace should be an Asset not a DataSet. 
Please review and update (the code).



docs/src/site/twiki/Bridge-HBase.twiki
Lines 22 (patched)


. ==> :


- Madhan Neethiraj


On April 24, 2018, 8:23 p.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66783/
> ---
> 
> (Updated April 24, 2018, 8:23 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2317:[Docs] Add HBase Bridge Documents
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/Bridge-HBase.twiki PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/66783/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ramesh Mani
> 
>

[jira] [Created] (ATLAS-2604) Minor fixups for relationshipdefs in the open metadata archive

[David Radley (JIRA)]

David Radley created ATLAS-2604:
---

 Summary: Minor fixups for relationshipdefs in the open metadata 
archive 
 Key: ATLAS-2604
 URL: https://issues.apache.org/jira/browse/ATLAS-2604
 Project: Atlas
  Issue Type: Bug
Reporter: David Radley
Assignee: David Radley






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

[jira] [Created] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents

[Ramesh Mani (JIRA)]

Ramesh Mani created ATLAS-2603:
--

 Summary: [Docs] Add Atlas Kafka Bridge Documents
 Key: ATLAS-2603
 URL: https://issues.apache.org/jira/browse/ATLAS-2603
 Project: Atlas
  Issue Type: Bug
Reporter: Ramesh Mani
Assignee: Ramesh Mani






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

[jira] [Updated] (ATLAS-2603) [Docs] Add Atlas Kafka Bridge Documents

[Ramesh Mani (JIRA)]

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

Ramesh Mani updated ATLAS-2603:
---
Description: [Docs] Add Atlas Kafka Bridge Documents

> [Docs] Add Atlas Kafka Bridge Documents
> ---
>
> Key: ATLAS-2603
> URL: https://issues.apache.org/jira/browse/ATLAS-2603
> Project: Atlas
>  Issue Type: Bug
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
>
> [Docs] Add Atlas Kafka Bridge Documents



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

Review Request 66783: ATLAS-2317:[Docs] Add HBase Bridge Documents

[Ramesh Mani]

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

Review request for atlas, Apoorv Naik, Madhan Neethiraj, and Sarath Subramanian.


Repository: atlas


Description
---

ATLAS-2317:[Docs] Add HBase Bridge Documents


Diffs
-

  docs/src/site/twiki/Bridge-HBase.twiki PRE-CREATION 


Diff: https://reviews.apache.org/r/66783/diff/1/


Testing
---


Thanks,

Ramesh Mani

[jira] [Updated] (ATLAS-2317) [Docs] Add HBase Bridge Documents

[Ramesh Mani (JIRA)]

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

Ramesh Mani updated ATLAS-2317:
---
Attachment: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch

> [Docs] Add HBase Bridge Documents
> -
>
> Key: ATLAS-2317
> URL: https://issues.apache.org/jira/browse/ATLAS-2317
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.8.1
>Reporter: ShuMing Li
>Assignee: Ramesh Mani
>Priority: Major
> Attachments: 0001-ATLAS-2317-Docs-Add-HBase-Bridge-Documents.patch
>
>
> Since HBase Bridge has been already 
> supported(https://issues.apache.org/jira/browse/ATLAS-1805), We should update 
> index 
> docs(https://github.com/apache/atlas/blob/master/docs/src/site/twiki/index.twiki)
>  to add HBase Config knowledge.



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

[jira] [Created] (ATLAS-2602) Import: Glossary Import Does not Display Imported Entities

[Ashutosh Mestry (JIRA)]

Ashutosh Mestry created ATLAS-2602:
--

 Summary: Import: Glossary Import Does not Display Imported Entities
 Key: ATLAS-2602
 URL: https://issues.apache.org/jira/browse/ATLAS-2602
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: trunk, 1.0.0
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
 Fix For: trunk


*Pre-requisites*
 * Create Glossary hierarchy with few terms.
 * Export to ZIP using Atlas Export.

*Steps to Duplicate*
 * Import the file create in previous step.
 * Open Atlas Web UI and navigate to Glossary tab. 

_Expected:_ All terms created are visible.

_Actual_: Few of the terms will be visible from in the tab.

_Additional information:_  Using JanusGraph Gremlin shell, it appears that the 
vertices are created but the edges (containing relationships) are missing.

 

 



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

Consuming Data from Atlas via Kafka

[Vento, Michael]

Hi Team,

My name is Michael Vento and I work for Comcast Cable. We are currently looking 
into possibly consuming metadata from Atlas from the ATLAS_ENTITIES kafka topic 
described here:
https://atlas.apache.org/Notification-Entity.html

Would you happen to have any additional documentation on this? The code that is 
provided there doesn’t include any imports so I wasn’t able to resolve the 
compile errors.

Thanks,

Michael Vento

Re: Dependent component versions for 1.0 release

[Nigel Jones]

On 2018/04/24 13:04:59, Graham Wallis  wrote: 

> Do we need to include anything about development versions including Maven, 
> Java, etc?

I think it would be worth mentioning in readme/ wiki build, though now we have 
the maven-enforcer in place we know the min prereq java is java 8 update 151 & 
maven 3.5.0 which aren't far off (latest 172 - jdk 11/18.10  is next lts and 
could be 'interesting', and maven 3.5.3)

Post-release I think there's a few other questions about specific component 
versions (and pom standardization where it makes sense), but I wouldn't change 
anything close to release

[jira] [Commented] (ATLAS-2598) Add POST method to fetch bulk entities with AtlasEntitiesWithExtInfo

[Graham Wallis (JIRA)]

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

Graham Wallis commented on ATLAS-2598:
--

Perhaps the best implementation would be to POST the collection of guids 
(effectively creating a query) and return a URI where the result of the query 
can retrieved using a subsequent GET. This seems to be preferred. 

The query/result would need to be cleaned up sometime later if it has not been 
the subject of a GET request - that would require some more thought.

> Add POST method to fetch bulk entities with AtlasEntitiesWithExtInfo
> 
>
> Key: ATLAS-2598
> URL: https://issues.apache.org/jira/browse/ATLAS-2598
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0-alpha
>Reporter: Nixon Rodrigues
>Priority: Major
> Fix For: 1.0.0
>
>
> To fetch bulk entities,  guids need to be passed as query params, there can 
> be a limit to the length of URL in GET method. 
> {noformat}
> http://localhost:21000/api/atlas/v2/entity/bulk?guid=d08a64f7-a2d4-4c88-aa67-6a98b5a52793&guid=a0910f28-6d63-4729-bd44-04c7e34edba5&guid=1b7b9749-d3ff-487c-bfd1-4e1ad6c3be90
> {noformat}
> POST method would be much suited for this .



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

[jira] [Commented] (ATLAS-2598) Add POST method to fetch bulk entities with AtlasEntitiesWithExtInfo

[Graham Wallis (JIRA)]

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

Graham Wallis commented on ATLAS-2598:
--

Hi [~nixonrodrigues] - as far as I know the HTTP spec does not forbid the use 
of a body on a GET request - it is not recommended, but it is permitted 
(subject to proxy considerations etc). Whilst using a body might be a bit 
suspect, would that be preferable to using a POST (for retrieval)?

> Add POST method to fetch bulk entities with AtlasEntitiesWithExtInfo
> 
>
> Key: ATLAS-2598
> URL: https://issues.apache.org/jira/browse/ATLAS-2598
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0-alpha
>Reporter: Nixon Rodrigues
>Priority: Major
> Fix For: 1.0.0
>
>
> To fetch bulk entities,  guids need to be passed as query params, there can 
> be a limit to the length of URL in GET method. 
> {noformat}
> http://localhost:21000/api/atlas/v2/entity/bulk?guid=d08a64f7-a2d4-4c88-aa67-6a98b5a52793&guid=a0910f28-6d63-4729-bd44-04c7e34edba5&guid=1b7b9749-d3ff-487c-bfd1-4e1ad6c3be90
> {noformat}
> POST method would be much suited for this .



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

Re: Dependent component versions for 1.0 release

[Graham Wallis]

Hi Madhan

Do we need to include anything about development versions including Maven, 
Java, etc?


Best regards,
  Graham

Graham Wallis
IBM Analytics
Internet: graham_wal...@uk.ibm.com 
IBM Laboratories, Hursley Park, Hursley, Hampshire SO21 2JN
Tel: +44 7741 379735




From:   Madhan Neethiraj 
To: "dev@atlas.apache.org" 
Date:   24/04/2018 00:45
Subject:Dependent component versions for 1.0 release



Atlas dev,

 

Please review the following component versions used by upcoming Apache 
Atlas 1.0 release:

  - Hadoop: 2.7.1

  - JanusGraph: 0.2.0

  - TinkerPop:  3.2.6

  - HBase:  1.1.2

  - Solr:   5.5.1

  - Kafka:  1.0.0

  - Jackson:2.9.2

  - Spring: 4.3.8

  - Hive:   1.2.1

  - Sqoop:  1.4.6

  - Storm:  1.2.0

 

Based on earlier discussions, support for Hadoop 3 will be taken up in a 
subsequent release, perhaps 3.1.

 

Regards,

Madhan



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

[jira] [Commented] (ATLAS-2601) OMAG server Swagger

[David Radley (JIRA)]

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

David Radley commented on ATLAS-2601:
-

[~daniela.otelea] . Ideally we should minimize the dependancies and standardise 
on one library to implement a capability. I am wondering why we need a new 
swagger dependancy - when we already have a working one knitted in the Atlas 
buld. .

omag-api is in the atlas web server - so this is not completely independent of 
Atlas.   

> OMAG server Swagger 
> 
>
> Key: ATLAS-2601
> URL: https://issues.apache.org/jira/browse/ATLAS-2601
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Maryna Strelchuk
>Assignee: Maryna Strelchuk
>Priority: Major
> Attachments: 0001-Atlas-2601-OMAG-server-Swagger.patch
>
>
> This Jira addresses the addition of the Swagger for the OMAG server. 
> Currently Swagger was added as a dependency for
>  * omag-server
>  * omag-api
>  * omas-connectedasset



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

[jira] [Commented] (ATLAS-2601) OMAG server Swagger

[Daniela Otelea (JIRA)]

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

Daniela Otelea commented on ATLAS-2601:
---

This mechanism (swagger) will be available for OMAG server - other Spring 
context, not part of Atlas Spring app. 

> OMAG server Swagger 
> 
>
> Key: ATLAS-2601
> URL: https://issues.apache.org/jira/browse/ATLAS-2601
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Maryna Strelchuk
>Assignee: Maryna Strelchuk
>Priority: Major
> Attachments: 0001-Atlas-2601-OMAG-server-Swagger.patch
>
>
> This Jira addresses the addition of the Swagger for the OMAG server. 
> Currently Swagger was added as a dependency for
>  * omag-server
>  * omag-api
>  * omas-connectedasset



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

[jira] [Commented] (ATLAS-2601) OMAG server Swagger

[Daniela Otelea (JIRA)]

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

Daniela Otelea commented on ATLAS-2601:
---

Added for review:

https://reviews.apache.org/r/66775/

> OMAG server Swagger 
> 
>
> Key: ATLAS-2601
> URL: https://issues.apache.org/jira/browse/ATLAS-2601
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Maryna Strelchuk
>Assignee: Maryna Strelchuk
>Priority: Major
> Attachments: 0001-Atlas-2601-OMAG-server-Swagger.patch
>
>
> This Jira addresses the addition of the Swagger for the OMAG server. 
> Currently Swagger was added as a dependency for
>  * omag-server
>  * omag-api
>  * omas-connectedasset



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

[jira] [Commented] (ATLAS-2601) OMAG server Swagger

[David Radley (JIRA)]

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

David Radley commented on ATLAS-2601:
-

The existing Atlas build uses enunciate to generate swagger. Is there a reason 
to add a second mechanism to generate Swagger? 

> OMAG server Swagger 
> 
>
> Key: ATLAS-2601
> URL: https://issues.apache.org/jira/browse/ATLAS-2601
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Maryna Strelchuk
>Assignee: Maryna Strelchuk
>Priority: Major
> Attachments: 0001-Atlas-2601-OMAG-server-Swagger.patch
>
>
> This Jira addresses the addition of the Swagger for the OMAG server. 
> Currently Swagger was added as a dependency for
>  * omag-server
>  * omag-api
>  * omas-connectedasset



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

[jira] [Updated] (ATLAS-2601) OMAG server Swagger

[Daniela Otelea (JIRA)]

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

Daniela Otelea updated ATLAS-2601:
--
Attachment: 0001-Atlas-2601-OMAG-server-Swagger.patch

> OMAG server Swagger 
> 
>
> Key: ATLAS-2601
> URL: https://issues.apache.org/jira/browse/ATLAS-2601
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Maryna Strelchuk
>Assignee: Maryna Strelchuk
>Priority: Major
> Attachments: 0001-Atlas-2601-OMAG-server-Swagger.patch
>
>
> This Jira addresses the addition of the Swagger for the OMAG server. 
> Currently Swagger was added as a dependency for
>  * omag-server
>  * omag-api
>  * omas-connectedasset



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

[jira] [Commented] (ATLAS-2598) Add POST method to fetch bulk entities with AtlasEntitiesWithExtInfo

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues commented on ATLAS-2598:


[~grahamwallis], your thoughts are welcomed. Please add your approach since the 
URL length can grow depending on the number of entities and there is a 
limitation in GET method.

> Add POST method to fetch bulk entities with AtlasEntitiesWithExtInfo
> 
>
> Key: ATLAS-2598
> URL: https://issues.apache.org/jira/browse/ATLAS-2598
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0-alpha
>Reporter: Nixon Rodrigues
>Priority: Major
> Fix For: 1.0.0
>
>
> To fetch bulk entities,  guids need to be passed as query params, there can 
> be a limit to the length of URL in GET method. 
> {noformat}
> http://localhost:21000/api/atlas/v2/entity/bulk?guid=d08a64f7-a2d4-4c88-aa67-6a98b5a52793&guid=a0910f28-6d63-4729-bd44-04c7e34edba5&guid=1b7b9749-d3ff-487c-bfd1-4e1ad6c3be90
> {noformat}
> POST method would be much suited for this .



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

[jira] [Assigned] (ATLAS-2601) OMAG server Swagger

[Maryna Strelchuk (JIRA)]

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

Maryna Strelchuk reassigned ATLAS-2601:
---

Assignee: Maryna Strelchuk

> OMAG server Swagger 
> 
>
> Key: ATLAS-2601
> URL: https://issues.apache.org/jira/browse/ATLAS-2601
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Maryna Strelchuk
>Assignee: Maryna Strelchuk
>Priority: Major
>
> This Jira addresses the addition of the Swagger for the OMAG server. 
> Currently Swagger was added as a dependency for
>  * omag-server
>  * omag-api
>  * omas-connectedasset



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

[jira] [Created] (ATLAS-2601) OMAG server Swagger

[Maryna Strelchuk (JIRA)]

Maryna Strelchuk created ATLAS-2601:
---

 Summary: OMAG server Swagger 
 Key: ATLAS-2601
 URL: https://issues.apache.org/jira/browse/ATLAS-2601
 Project: Atlas
  Issue Type: Improvement
Reporter: Maryna Strelchuk


This Jira addresses the addition of the Swagger for the OMAG server. 

Currently Swagger was added as a dependency for
 * omag-server
 * omag-api
 * omas-connectedasset



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

[jira] [Commented] (ATLAS-2598) Add POST method to fetch bulk entities with AtlasEntitiesWithExtInfo

[Graham Wallis (JIRA)]

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

Graham Wallis commented on ATLAS-2598:
--

I would not have thought that using POST to retrieve entities was an 
appropriate choice of HTTP method.

> Add POST method to fetch bulk entities with AtlasEntitiesWithExtInfo
> 
>
> Key: ATLAS-2598
> URL: https://issues.apache.org/jira/browse/ATLAS-2598
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0-alpha
>Reporter: Nixon Rodrigues
>Priority: Major
> Fix For: 1.0.0
>
>
> To fetch bulk entities,  guids need to be passed as query params, there can 
> be a limit to the length of URL in GET method. 
> {noformat}
> http://localhost:21000/api/atlas/v2/entity/bulk?guid=d08a64f7-a2d4-4c88-aa67-6a98b5a52793&guid=a0910f28-6d63-4729-bd44-04c7e34edba5&guid=1b7b9749-d3ff-487c-bfd1-4e1ad6c3be90
> {noformat}
> POST method would be much suited for this .



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

[jira] [Assigned] (ATLAS-2599) UI - Regression - Lineage is not displayed even it has DataSet as Supertype

[Keval Bhatt (JIRA)]

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

Keval Bhatt reassigned ATLAS-2599:
--

Assignee: Keval Bhatt

> UI - Regression - Lineage is not displayed even it has DataSet as Supertype
> ---
>
> Key: ATLAS-2599
> URL: https://issues.apache.org/jira/browse/ATLAS-2599
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Tejas Rawool
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.0.0
>
>
> Lineage should be displayed for the entity which has dataset as a supurtype 
> of its own or nested derivatives.
> Example:-
> ‘hdfs_path’ has supertype ‘fs_path’ which has supertype as ‘DataSet’.



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

[jira] [Created] (ATLAS-2599) UI - Regression - Lineage is not displayed even it has DataSet as Supertype

[Tejas Rawool (JIRA)]

Tejas Rawool created ATLAS-2599:
---

 Summary: UI - Regression - Lineage is not displayed even it has 
DataSet as Supertype
 Key: ATLAS-2599
 URL: https://issues.apache.org/jira/browse/ATLAS-2599
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0
Reporter: Tejas Rawool
 Fix For: 1.0.0


Lineage should be displayed for the entity which has dataset as a supurtype of 
its own or nested derivatives.

Example:-

‘hdfs_path’ has supertype ‘fs_path’ which has supertype as ‘DataSet’.



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

[jira] [Created] (ATLAS-2600) Glossary Term details page should allow add/update/remove of classifications

[Keval Bhatt (JIRA)]

Keval Bhatt created ATLAS-2600:
--

 Summary: Glossary Term details page should allow add/update/remove 
of classifications
 Key: ATLAS-2600
 URL: https://issues.apache.org/jira/browse/ATLAS-2600
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 1.0.0
Reporter: Keval Bhatt
Assignee: Keval Bhatt
 Fix For: 1.0.0






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

[jira] [Created] (ATLAS-2598) Add POST method to fetch bulk entities with AtlasEntitiesWithExtInfo

[Nixon Rodrigues (JIRA)]

Nixon Rodrigues created ATLAS-2598:
--

 Summary: Add POST method to fetch bulk entities with 
AtlasEntitiesWithExtInfo
 Key: ATLAS-2598
 URL: https://issues.apache.org/jira/browse/ATLAS-2598
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0-alpha
Reporter: Nixon Rodrigues
 Fix For: 1.0.0


To fetch bulk entities,  guids need to be passed as query params, there can be 
a limit to the length of URL in GET method. 

{noformat}
http://localhost:21000/api/atlas/v2/entity/bulk?guid=d08a64f7-a2d4-4c88-aa67-6a98b5a52793&guid=a0910f28-6d63-4729-bd44-04c7e34edba5&guid=1b7b9749-d3ff-487c-bfd1-4e1ad6c3be90
{noformat}

POST method would be much suited for this .





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