[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739608#comment-16739608 ] Graham Wallis commented on ATLAS-1773: -- The RBT review for the patch associated with this JIRA is at [https://reviews.apache.org/r/68412/] (The other patches have their own reviews pending where appropriate) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, > ATLAS-2810-2019-01-10.patch, ATLAS-2939-2018-12-21.patch, > ATLAS-2985-2019-01-10.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739499#comment-16739499 ] Graham Wallis commented on ATLAS-1773: -- Have updated two of the above patches. The ATLAS-2810 patch is the same as Nikhil's latest patch from the current review of ATLAS-2810; which will hopefully commit soon. The updated ATLAS-2985 patch contains further updates to cater for the fact that hard/soft delete does not work correctly. Suggest you continue to apply them in the order listed in the previous comment. > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, > ATLAS-2810-2019-01-10.patch, ATLAS-2939-2018-12-21.patch, > ATLAS-2985-2019-01-10.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-2985-2019-01-10.patch ATLAS-2810-2019-01-10.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, > ATLAS-2810-2019-01-10.patch, ATLAS-2939-2018-12-21.patch, > ATLAS-2985-2019-01-10.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-2810-2018-12-21.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, ATLAS-2939-2018-12-21.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-2985-2018-12-21.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, ATLAS-2939-2018-12-21.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2939) Enable EntityGraphMapper to unset optional attribute
[ https://issues.apache.org/jira/browse/ATLAS-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2939: - Attachment: ATLAS-2939-2018-12-21.patch > Enable EntityGraphMapper to unset optional attribute > > > Key: ATLAS-2939 > URL: https://issues.apache.org/jira/browse/ATLAS-2939 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Attachments: ATLAS-2939-2018-12-21.patch > > > Use Case: > Pre-condition: There exists an entity instance that has some combination of > mandatory attributes and non-mandatory attributes. All of the mandatory > attributes have values (otherwise the entity could not have been created) and > (for this example) at least some of the non-mandatory attributes have values. > A caller (an application for example) tries to update the entity's > attributes, providing a new set of attribute values. The revised set of > values contains values for all the mandatory attributes (otherwise the update > will be rejected) and contains values for a subset of the non-mandatory > attributes, such that a non-mandatory that was set (in the pre-condition > above) should be not set as a result of the update. In other words, at least > one of the non-mandatory attributes should be cleared. > Post-condition: I think the expected outcome is that the entity has attribute > values for all mandatory attributes and has attribute values for the > non-mandatory attributes that were were set by the update or that were > already set (in the pre-condition) and were not cleared by the update. It > should not have values for non-mandatory attributes that were either not > already set or that were set and were cleared by the update. > I think what currently happens is that attribute values are not actually > cleared as described above - i.e. they remain in the graph and will continue > to be seen on a subsequent retrieval of the entity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726798#comment-16726798 ] Graham Wallis commented on ATLAS-1773: -- To run the OMRS stack (connector and event mapper), apply the following patches from the set attached above (order is important): # ATLAS-2810-2018-12-21.patch - this is a delta on top of Nikhil's forthcoming changes - when his ATLAS-2810 patch commits to master this delta patch will no longer be needed # ATLAS-2939-2018-12-21.patch - this patch is currently under review # ATLAS-2985-2018-12-21.patch - provides support for hard and soft deletes but is not a complete solution (does not address duplication of delete notifications) so should only be used for development/demo purposes # ATLAS-1773-2018-12-21.patch - this is the connector and event mapper Then start Atlas and configure and activate the OMRS stack. > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, > ATLAS-2810-2018-12-21.patch, ATLAS-2939-2018-12-21.patch, > ATLAS-2985-2018-12-21.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-2985-2018-12-21.patch ATLAS-2939-2018-12-21.patch ATLAS-2810-2018-12-21.patch ATLAS-1773-2018-12-21.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-21.patch, > ATLAS-2810-2018-12-21.patch, ATLAS-2939-2018-12-21.patch, > ATLAS-2985-2018-12-21.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-2985-2018-12-05.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-12-05.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-2939-2018-11-14.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-3003) Hard Delete in Apache Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726758#comment-16726758 ] Graham Wallis commented on ATLAS-3003: -- ATLAS-2774 alone does not support soft delete followed by hard delete. If you combine with with ATLAS-2985 it will perform the hard delete. But even with the above combination there is a latent problem that duplicate notifications will be sent - a new notification event type is needed for the hard delete. > Hard Delete in Apache Atlas > --- > > Key: ATLAS-3003 > URL: https://issues.apache.org/jira/browse/ATLAS-3003 > Project: Atlas > Issue Type: Bug >Reporter: Abhishek Sharma >Priority: Blocker > > Hello, > I have tried to delete an entity in atlas but it turns out that Atlas only > soft deletes an entity and never hard deletes them. Is there a way in which I > can hard delete an entity so that it is entirely removed from Atlas. > Thanks in advance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2939) Enable EntityGraphMapper to unset optional attribute
[ https://issues.apache.org/jira/browse/ATLAS-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2939: - Description: Use Case: Pre-condition: There exists an entity instance that has some combination of mandatory attributes and non-mandatory attributes. All of the mandatory attributes have values (otherwise the entity could not have been created) and (for this example) at least some of the non-mandatory attributes have values. A caller (an application for example) tries to update the entity's attributes, providing a new set of attribute values. The revised set of values contains values for all the mandatory attributes (otherwise the update will be rejected) and contains values for a subset of the non-mandatory attributes, such that a non-mandatory that was set (in the pre-condition above) should be not set as a result of the update. In other words, at least one of the non-mandatory attributes should be cleared. Post-condition: I think the expected outcome is that the entity has attribute values for all mandatory attributes and has attribute values for the non-mandatory attributes that were were set by the update or that were already set (in the pre-condition) and were not cleared by the update. It should not have values for non-mandatory attributes that were either not already set or that were set and were cleared by the update. I think what currently happens is that attribute values are not actually cleared as described above - i.e. they remain in the graph and will continue to be seen on a subsequent retrieval of the entity. > Enable EntityGraphMapper to unset optional attribute > > > Key: ATLAS-2939 > URL: https://issues.apache.org/jira/browse/ATLAS-2939 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > > Use Case: > Pre-condition: There exists an entity instance that has some combination of > mandatory attributes and non-mandatory attributes. All of the mandatory > attributes have values (otherwise the entity could not have been created) and > (for this example) at least some of the non-mandatory attributes have values. > A caller (an application for example) tries to update the entity's > attributes, providing a new set of attribute values. The revised set of > values contains values for all the mandatory attributes (otherwise the update > will be rejected) and contains values for a subset of the non-mandatory > attributes, such that a non-mandatory that was set (in the pre-condition > above) should be not set as a result of the update. In other words, at least > one of the non-mandatory attributes should be cleared. > Post-condition: I think the expected outcome is that the entity has attribute > values for all mandatory attributes and has attribute values for the > non-mandatory attributes that were were set by the update or that were > already set (in the pre-condition) and were not cleared by the update. It > should not have values for non-mandatory attributes that were either not > already set or that were set and were cleared by the update. > I think what currently happens is that attribute values are not actually > cleared as described above - i.e. they remain in the graph and will continue > to be seen on a subsequent retrieval of the entity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2939) Enable EntityGraphMapper to unset optional attribute
[ https://issues.apache.org/jira/browse/ATLAS-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2939: - Attachment: (was: ATLAS-2939-2018-11-14.patch) > Enable EntityGraphMapper to unset optional attribute > > > Key: ATLAS-2939 > URL: https://issues.apache.org/jira/browse/ATLAS-2939 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > > Use Case: > Pre-condition: There exists an entity instance that has some combination of > mandatory attributes and non-mandatory attributes. All of the mandatory > attributes have values (otherwise the entity could not have been created) and > (for this example) at least some of the non-mandatory attributes have values. > A caller (an application for example) tries to update the entity's > attributes, providing a new set of attribute values. The revised set of > values contains values for all the mandatory attributes (otherwise the update > will be rejected) and contains values for a subset of the non-mandatory > attributes, such that a non-mandatory that was set (in the pre-condition > above) should be not set as a result of the update. In other words, at least > one of the non-mandatory attributes should be cleared. > Post-condition: I think the expected outcome is that the entity has attribute > values for all mandatory attributes and has attribute values for the > non-mandatory attributes that were were set by the update or that were > already set (in the pre-condition) and were not cleared by the update. It > should not have values for non-mandatory attributes that were either not > already set or that were set and were cleared by the update. > I think what currently happens is that attribute values are not actually > cleared as described above - i.e. they remain in the graph and will continue > to be seen on a subsequent retrieval of the entity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707044#comment-16707044 ] Graham Wallis edited comment on ATLAS-1773 at 12/5/18 3:46 PM: --- Latest ATLAS-1773 patch (5th Dec) relies on ATLAS-2939 for correct property handling and ATLAS-2985 for full delete function. was (Author: grahamwallis): Latest ATLAS-1773 patch (4th Dec) relies on ATLAS-2939 for correct property handling and ATLAS-2985 for full delete function. > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-05.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-12-05.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-12-05.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-05.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-12-05.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-12-04.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-05.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-12-05.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-2985-2018-12-05.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-04.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-12-05.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-2985-2018-11-30.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-04.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-12-05.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707044#comment-16707044 ] Graham Wallis edited comment on ATLAS-1773 at 12/4/18 1:34 PM: --- Latest ATLAS-1773 patch (4th Dec) relies on ATLAS-2939 for correct property handling and ATLAS-2985 for full delete function. was (Author: grahamwallis): Latest ATLAS-1773 patch (3rd Dec) relies on ATLAS-2939 for correct property handling and ATLAS-2985 for full delete function. > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-04.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-11-30.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-12-04.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-04.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-11-30.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-12-03.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-04.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-11-30.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-11-14.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-11-30.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707044#comment-16707044 ] Graham Wallis commented on ATLAS-1773: -- Latest ATLAS-1773 patch (3rd Dec) relies on ATLAS-2939 for correct property handling and ATLAS-2985 for full delete function. > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-03.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-11-30.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-12-03.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-12-03.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-11-30.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2985) Fix delete handlers and relationship store
[ https://issues.apache.org/jira/browse/ATLAS-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2985: - Description: The problems this fixes are as follows: * following a soft delete, a hard delete is not possible because the entity or relationship will have status DELETED, and prior to this Jira and patch the abstract delete handler skips the delete. * during a soft delete the modified-time, modified-by and version number attributes on the entity or relationship should be updated, but updateRelationship does not update system attributes - this Jira and patch updates the system attributes that will need to be updated during a delete or other update operations. * also fixes a minor copy-paste debug logging error. > Fix delete handlers and relationship store > -- > > Key: ATLAS-2985 > URL: https://issues.apache.org/jira/browse/ATLAS-2985 > Project: Atlas > Issue Type: Bug >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Critical > Attachments: ATLAS-2985-2018-11-30.patch > > > The problems this fixes are as follows: > * following a soft delete, a hard delete is not possible because the entity > or relationship will have status DELETED, and prior to this Jira and patch > the abstract delete handler skips the delete. > * during a soft delete the modified-time, modified-by and version number > attributes on the entity or relationship should be updated, but > updateRelationship does not update system attributes - this Jira and patch > updates the system attributes that will need to be updated during a delete or > other update operations. > * also fixes a minor copy-paste debug logging error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2985) Fix delete handlers and relationship store
Graham Wallis created ATLAS-2985: Summary: Fix delete handlers and relationship store Key: ATLAS-2985 URL: https://issues.apache.org/jira/browse/ATLAS-2985 Project: Atlas Issue Type: Bug Reporter: Graham Wallis Assignee: Graham Wallis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2985) Fix delete handlers and relationship store
[ https://issues.apache.org/jira/browse/ATLAS-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704999#comment-16704999 ] Graham Wallis commented on ATLAS-2985: -- Review is here: https://reviews.apache.org/r/69494/ > Fix delete handlers and relationship store > -- > > Key: ATLAS-2985 > URL: https://issues.apache.org/jira/browse/ATLAS-2985 > Project: Atlas > Issue Type: Bug >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Critical > Attachments: ATLAS-2985-2018-11-30.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-2985-2018-11-30.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-11-14.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2985-2018-11-30.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692943#comment-16692943 ] Graham Wallis commented on ATLAS-1773: -- Hi Bogdan - yes that was expected once the ATLAS-2774 changes went in to the relationship store. I rebased the patch for ATLAS-2967 yesterday and committed it to Atlas master. It should now be possible to build with just Atlas master and the ATLAS-2939 patch. The other Atlas dependencies (ATLAS-2936, ATLAS-2938 and ATLAS-2967) are now committed. > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-11-14.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2967-2018-11-14.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-2967-2018-11-14.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-11-14.patch, ATLAS-2939-2018-11-14.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2967) Save and restore homeId into AtlasRelationship instances
[ https://issues.apache.org/jira/browse/ATLAS-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis resolved ATLAS-2967. -- Resolution: Fixed Assignee: Graham Wallis > Save and restore homeId into AtlasRelationship instances > > > Key: ATLAS-2967 > URL: https://issues.apache.org/jira/browse/ATLAS-2967 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Major > Fix For: 2.0.0 > > Attachments: ATLAS-2967-2018-11-19.patch > > > In order to save homeId system attribute into a saved AtlasRelationship and > retrieve it when reading the relationship, need to update > EntityGraphRetriever and AtlasRelationshipStoreV2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2967) Save and restore homeId into AtlasRelationship instances
[ https://issues.apache.org/jira/browse/ATLAS-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2967: - Attachment: ATLAS-2967-2018-11-19.patch > Save and restore homeId into AtlasRelationship instances > > > Key: ATLAS-2967 > URL: https://issues.apache.org/jira/browse/ATLAS-2967 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Fix For: 2.0.0 > > Attachments: ATLAS-2967-2018-11-19.patch > > > In order to save homeId system attribute into a saved AtlasRelationship and > retrieve it when reading the relationship, need to update > EntityGraphRetriever and AtlasRelationshipStoreV2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2967) Save and restore homeId into AtlasRelationship instances
[ https://issues.apache.org/jira/browse/ATLAS-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2967: - Attachment: (was: ATLAS-2967-2018-11-14.patch) > Save and restore homeId into AtlasRelationship instances > > > Key: ATLAS-2967 > URL: https://issues.apache.org/jira/browse/ATLAS-2967 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Fix For: 2.0.0 > > > In order to save homeId system attribute into a saved AtlasRelationship and > retrieve it when reading the relationship, need to update > EntityGraphRetriever and AtlasRelationshipStoreV2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687745#comment-16687745 ] Graham Wallis commented on ATLAS-1773: -- Added 14th November patch - this level of connector code passes the mandatory level of the CTS (with mods to the CTS for authentication and a few other things). It pre-reqs the patches for ATLAS-2939 and ATLAS-2967 (which contain changes to base Atlas for clearing of properties and save and restore of relationship homeId). I have attached both those patches to this Jira for your convenience. You can apply the patches in any order to Atlas master. Good luck - let me know if you run into any problems. > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-11-14.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2967-2018-11-14.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-09-04.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-11-14.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2967-2018-11-14.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-10-01.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-11-14.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2967-2018-11-14.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-2967-2018-11-14.patch ATLAS-2939-2018-11-14.patch ATLAS-1773-2018-11-14.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-11-14.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2967-2018-11-14.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-08-31.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-11-14.patch, > ATLAS-2939-2018-11-14.patch, ATLAS-2967-2018-11-14.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2967) Save and restore homeId into AtlasRelationship instances
[ https://issues.apache.org/jira/browse/ATLAS-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686364#comment-16686364 ] Graham Wallis commented on ATLAS-2967: -- Review is here: [https://reviews.apache.org/r/69335/] > Save and restore homeId into AtlasRelationship instances > > > Key: ATLAS-2967 > URL: https://issues.apache.org/jira/browse/ATLAS-2967 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Fix For: 2.0.0 > > Attachments: ATLAS-2967-2018-11-14.patch > > > In order to save homeId system attribute into a saved AtlasRelationship and > retrieve it when reading the relationship, need to update > EntityGraphRetriever and AtlasRelationshipStoreV2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2939) Enable EntityGraphMapper to unset optional attribute
[ https://issues.apache.org/jira/browse/ATLAS-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16686362#comment-16686362 ] Graham Wallis commented on ATLAS-2939: -- Review is here: [https://reviews.apache.org/r/69336/] > Enable EntityGraphMapper to unset optional attribute > > > Key: ATLAS-2939 > URL: https://issues.apache.org/jira/browse/ATLAS-2939 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Attachments: ATLAS-2939-2018-11-14.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2939) Enable EntityGraphMapper to unset optional attribute
[ https://issues.apache.org/jira/browse/ATLAS-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2939: - Attachment: ATLAS-2939-2018-11-14.patch > Enable EntityGraphMapper to unset optional attribute > > > Key: ATLAS-2939 > URL: https://issues.apache.org/jira/browse/ATLAS-2939 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Attachments: ATLAS-2939-2018-11-14.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2967) Save and restore homeId into AtlasRelationship instances
[ https://issues.apache.org/jira/browse/ATLAS-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2967: - Fix Version/s: 2.0.0 > Save and restore homeId into AtlasRelationship instances > > > Key: ATLAS-2967 > URL: https://issues.apache.org/jira/browse/ATLAS-2967 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Fix For: 2.0.0 > > Attachments: ATLAS-2967-2018-11-14.patch > > > In order to save homeId system attribute into a saved AtlasRelationship and > retrieve it when reading the relationship, need to update > EntityGraphRetriever and AtlasRelationshipStoreV2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2967) Save and restore homeId into AtlasRelationship instances
[ https://issues.apache.org/jira/browse/ATLAS-2967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2967: - Attachment: ATLAS-2967-2018-11-14.patch > Save and restore homeId into AtlasRelationship instances > > > Key: ATLAS-2967 > URL: https://issues.apache.org/jira/browse/ATLAS-2967 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Attachments: ATLAS-2967-2018-11-14.patch > > > In order to save homeId system attribute into a saved AtlasRelationship and > retrieve it when reading the relationship, need to update > EntityGraphRetriever and AtlasRelationshipStoreV2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2967) Save and restore homeId into AtlasRelationship instances
Graham Wallis created ATLAS-2967: Summary: Save and restore homeId into AtlasRelationship instances Key: ATLAS-2967 URL: https://issues.apache.org/jira/browse/ATLAS-2967 Project: Atlas Issue Type: Improvement Reporter: Graham Wallis In order to save homeId system attribute into a saved AtlasRelationship and retrieve it when reading the relationship, need to update EntityGraphRetriever and AtlasRelationshipStoreV2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2938) Enable EntityGraphMapper to update entity version
[ https://issues.apache.org/jira/browse/ATLAS-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis resolved ATLAS-2938. -- Resolution: Fixed > Enable EntityGraphMapper to update entity version > -- > > Key: ATLAS-2938 > URL: https://issues.apache.org/jira/browse/ATLAS-2938 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2938) Enable EntityGraphMapper to update entity version
[ https://issues.apache.org/jira/browse/ATLAS-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis reassigned ATLAS-2938: Assignee: Graham Wallis Fix Version/s: 2.0.0 > Enable EntityGraphMapper to update entity version > -- > > Key: ATLAS-2938 > URL: https://issues.apache.org/jira/browse/ATLAS-2938 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2936) Enable Atlas to store provenance type information
[ https://issues.apache.org/jira/browse/ATLAS-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis reassigned ATLAS-2936: Assignee: Graham Wallis Fix Version/s: 2.0.0 > Enable Atlas to store provenance type information > - > > Key: ATLAS-2936 > URL: https://issues.apache.org/jira/browse/ATLAS-2936 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2936) Enable Atlas to store provenance type information
[ https://issues.apache.org/jira/browse/ATLAS-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis resolved ATLAS-2936. -- Resolution: Fixed > Enable Atlas to store provenance type information > - > > Key: ATLAS-2936 > URL: https://issues.apache.org/jira/browse/ATLAS-2936 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2939) Enable EntityGraphMapper to unset optional attribute
Graham Wallis created ATLAS-2939: Summary: Enable EntityGraphMapper to unset optional attribute Key: ATLAS-2939 URL: https://issues.apache.org/jira/browse/ATLAS-2939 Project: Atlas Issue Type: Improvement Reporter: Graham Wallis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2938) Enable EntityGraphMapper to update entity version
Graham Wallis created ATLAS-2938: Summary: Enable EntityGraphMapper to update entity version Key: ATLAS-2938 URL: https://issues.apache.org/jira/browse/ATLAS-2938 Project: Atlas Issue Type: Improvement Reporter: Graham Wallis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2936) Enable Atlas to store provenance type information
Graham Wallis created ATLAS-2936: Summary: Enable Atlas to store provenance type information Key: ATLAS-2936 URL: https://issues.apache.org/jira/browse/ATLAS-2936 Project: Atlas Issue Type: Improvement Reporter: Graham Wallis -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-10-01.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-31.patch, > ATLAS-1773-2018-09-04.patch, ATLAS-1773-2018-10-01.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-09-04.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-31.patch, ATLAS-1773-2018-09-04.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-08-31.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-31.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-08-31.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-04.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-08-04.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-04.patch, ATLAS-1773-2018-08-31.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-08-31.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-31.patch, > ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-08-17.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-08-23.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-08-22.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2853) Entity notifications to be sent after transaction commit
[ https://issues.apache.org/jira/browse/ATLAS-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598463#comment-16598463 ] Graham Wallis commented on ATLAS-2853: -- In addition to the problem of what happens on a rollback, the problem also affects commit - but I think your patch addresses it. The additional aspect to the problem is that if the notification is sent prior to commit then the subscribers can pick it up and query the graph before the graph has had a chance to commit - so the subscribers see the old (stale) state. The most obvious example of this was on an entity create - the subscriber then queried the graph and the graph denied any knowledge of the new entity. Doing the commit before send is better in both the commit and rollback cases. > Entity notifications to be sent after transaction commit > > > Key: ATLAS-2853 > URL: https://issues.apache.org/jira/browse/ATLAS-2853 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Critical > Fix For: 0.8.3, 1.1.0, 2.0.0 > > Attachments: ATLAS-2853.patch > > > Currently, notification on entity changes (create/update/delete entities, > add/update/remove classifications on entities) are sent before the changes > are committed in the database. If commit fails, the entity state seen by > notification receivers would be different from Atlas. To avoid this, Atlas > server should entity notifications only after the transaction is committed to > the database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2844) Add timestamp in EntityNotification
Graham Wallis created ATLAS-2844: Summary: Add timestamp in EntityNotification Key: ATLAS-2844 URL: https://issues.apache.org/jira/browse/ATLAS-2844 Project: Atlas Issue Type: Improvement Reporter: Graham Wallis If we add a timestamp to the EntityNotification it will allow a consumer of the notification to accurately specify the time that the event occurred, even after publication and subsequent consume through Kafka topic. This would improve precision. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis reopened ATLAS-1773: -- Resolved prematurely - reopening > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-17.patch, > ATLAS-1773-2018-08-22.patch, ATLAS-1773-2018-08-23.patch, > ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-08-23.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-17.patch, > ATLAS-1773-2018-08-22.patch, ATLAS-1773-2018-08-23.patch, > ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-08-22.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-17.patch, > ATLAS-1773-2018-08-22.patch, ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2808) Enable Atlas to store entity proxies
[ https://issues.apache.org/jira/browse/ATLAS-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis resolved ATLAS-2808. -- Resolution: Fixed Fix Version/s: 2.0.0 > Enable Atlas to store entity proxies > > > Key: ATLAS-2808 > URL: https://issues.apache.org/jira/browse/ATLAS-2808 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Fix For: 2.0.0 > > Attachments: ATLAS-2808-2018-08-16.patch > > > This feature will enable Atlas to store proxies for entities supplied as > relationship ends, to enable Atlas to participate in distributed metadata > sharing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16584006#comment-16584006 ] Graham Wallis commented on ATLAS-1773: -- Patch replaced. > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-17.patch, > ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-08-17.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-17.patch, > ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-08-02.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2808) Enable Atlas to store entity proxies
[ https://issues.apache.org/jira/browse/ATLAS-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16582576#comment-16582576 ] Graham Wallis commented on ATLAS-2808: -- Refreshed patch to address review comments. Review at https://reviews.apache.org/r/68188/ > Enable Atlas to store entity proxies > > > Key: ATLAS-2808 > URL: https://issues.apache.org/jira/browse/ATLAS-2808 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Attachments: ATLAS-2808-2018-08-16.patch > > > This feature will enable Atlas to store proxies for entities supplied as > relationship ends, to enable Atlas to participate in distributed metadata > sharing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2808) Enable Atlas to store entity proxies
[ https://issues.apache.org/jira/browse/ATLAS-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2808: - Attachment: ATLAS-2808-2018-08-16.patch > Enable Atlas to store entity proxies > > > Key: ATLAS-2808 > URL: https://issues.apache.org/jira/browse/ATLAS-2808 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Attachments: ATLAS-2808-2018-08-16.patch > > > This feature will enable Atlas to store proxies for entities supplied as > relationship ends, to enable Atlas to participate in distributed metadata > sharing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2808) Enable Atlas to store entity proxies
[ https://issues.apache.org/jira/browse/ATLAS-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2808: - Attachment: (was: ATLAS-2808-2012-08-03.patch) > Enable Atlas to store entity proxies > > > Key: ATLAS-2808 > URL: https://issues.apache.org/jira/browse/ATLAS-2808 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > > This feature will enable Atlas to store proxies for entities supplied as > relationship ends, to enable Atlas to participate in distributed metadata > sharing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2807) Re-evaluate classification propagation during entity delete
[ https://issues.apache.org/jira/browse/ATLAS-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578306#comment-16578306 ] Graham Wallis commented on ATLAS-2807: -- I still think this change should not be applied to all types of relationship - it is appropriate for those relationships in which the propagated classifications are effectively inherited - e.g. if you create a table by running a process on a dataset, then delete the dataset - in that case the generated table should (indeed, must) continue to be tagged eg as PII. But in a relationship of a transient nature you might only want the classifications to persist whilst the source entity exists and is related to the target entity. It seems that this change only considers the former, not the latter. > Re-evaluate classification propagation during entity delete > --- > > Key: ATLAS-2807 > URL: https://issues.apache.org/jira/browse/ATLAS-2807 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha, 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0 > > Attachments: > ATLAS-2807-Re-evaluate-classification-propagation-du-MASTER.patch, > Classification Propagation during entity delete1.pdf > > > The current behavior - when we delete an entity *f1*, all tags associate to > *f1* which got propagated > to downstream entities are removed – *PII* tag propagated to *process1* and > *t1* is removed > *Proposed Change* > _*Soft Delete:*_ > When entity *f1* is deleted, retain the propagated classification edges, so > the downstream entities > – *process1* and *t1* continue to have *PII* classification associated to them > _*Hard Delete:*_ > In cases of hard delete, the source entity (*f1*) is deleted from atlas, but > its classification vertex > (*PII*) continue to exist and will continue propagating to *process1* and > *t1*. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2787) Clean out redundant OMAG modulles
[ https://issues.apache.org/jira/browse/ATLAS-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis reassigned ATLAS-2787: Assignee: Graham Wallis > Clean out redundant OMAG modulles > - > > Key: ATLAS-2787 > URL: https://issues.apache.org/jira/browse/ATLAS-2787 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Minor > Fix For: 2.0.0 > > Attachments: ATLAS-2787-2018-07-12.patch > > > It would be good to clear out the OM modules that are no longer needed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2787) Clean out redundant OMAG modules
[ https://issues.apache.org/jira/browse/ATLAS-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis resolved ATLAS-2787. -- Resolution: Fixed Fix Version/s: 2.0.0 > Clean out redundant OMAG modules > > > Key: ATLAS-2787 > URL: https://issues.apache.org/jira/browse/ATLAS-2787 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Minor > Fix For: 2.0.0 > > Attachments: ATLAS-2787-2018-07-12.patch > > > It would be good to clear out the OM modules that are no longer needed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2787) Clean out redundant OMAG modules
[ https://issues.apache.org/jira/browse/ATLAS-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2787: - Summary: Clean out redundant OMAG modules (was: Clean out redundant OMAG modulles) > Clean out redundant OMAG modules > > > Key: ATLAS-2787 > URL: https://issues.apache.org/jira/browse/ATLAS-2787 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Minor > Fix For: 2.0.0 > > Attachments: ATLAS-2787-2018-07-12.patch > > > It would be good to clear out the OM modules that are no longer needed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568235#comment-16568235 ] Graham Wallis commented on ATLAS-1773: -- ATLAS-1773-2018-08-03.patch includes EntityProxy capability. Install ATLAS-2808 patch first, then ATLAS-1773-2018-08-03 patch, then you can saveRelationshipReferenceCopy with EntityProxy objects that are not already known to Atlas. > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-02.patch, > ATLAS-1773-2018-08-03.patch, ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-08-03.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-02.patch, > ATLAS-1773-2018-08-03.patch, ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2808) Enable Atlas to store entity proxies
[ https://issues.apache.org/jira/browse/ATLAS-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2808: - Attachment: ATLAS-2808-2012-08-03.patch > Enable Atlas to store entity proxies > > > Key: ATLAS-2808 > URL: https://issues.apache.org/jira/browse/ATLAS-2808 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > Attachments: ATLAS-2808-2012-08-03.patch > > > This feature will enable Atlas to store proxies for entities supplied as > relationship ends, to enable Atlas to participate in distributed metadata > sharing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2808) Enable Atlas to store entity proxies
Graham Wallis created ATLAS-2808: Summary: Enable Atlas to store entity proxies Key: ATLAS-2808 URL: https://issues.apache.org/jira/browse/ATLAS-2808 Project: Atlas Issue Type: Improvement Reporter: Graham Wallis This feature will enable Atlas to store proxies for entities supplied as relationship ends, to enable Atlas to participate in distributed metadata sharing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2807) Re-evaluate classification propagation during entity delete
[ https://issues.apache.org/jira/browse/ATLAS-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568010#comment-16568010 ] Graham Wallis commented on ATLAS-2807: -- Hi [~sarath.ku...@gmail.com] Thanks for providing the PDF which explains what this Jira is about. I have a question: does the desired behaviour depend on the nature of the relationship? I can see that where an entity has been created (t1 in your examples) then it probably should retain the tags pertaining to the entity and process from which it was created (even if the source of that lineage is subsequently deleted). But for other types of relationship it seems less obvious to me that we would want to retain the tags from the 'upstream' entity if it is deleted. > Re-evaluate classification propagation during entity delete > --- > > Key: ATLAS-2807 > URL: https://issues.apache.org/jira/browse/ATLAS-2807 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha, 1.0.0 >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian >Priority: Major > Fix For: 1.1.0 > > Attachments: > 0001-ATLAS-2807-Re-evaluate-classification-propagation-du.patch, > Classification Propagation during entity delete1.pdf > > > The current behavior - when we delete an entity *f1*, all tags associate to > *f1* which got propagated > to downstream entities are removed – *PII* tag propagated to *process1* and > *t1* is removed > *Proposed Change* > _*Soft Delete:*_ > When entity *f1* is deleted, retain the propagated classification edges, so > the downstream entities > – *process1* and *t1* continue to have *PII* classification associated to them > _*Hard Delete:*_ > In cases of hard delete, the source entity (*f1*) is deleted from atlas, but > its classification vertex > (*PII*) continue to exist and will continue propagating to *process1* and > *t1*. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (ATLAS-2803) Additions to AtlasEnumDef and AtlasRelationshipDef toString() methods
[ https://issues.apache.org/jira/browse/ATLAS-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis reassigned ATLAS-2803: Assignee: Graham Wallis Fix Version/s: 2.0.0 > Additions to AtlasEnumDef and AtlasRelationshipDef toString() methods > - > > Key: ATLAS-2803 > URL: https://issues.apache.org/jira/browse/ATLAS-2803 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Minor > Fix For: 2.0.0 > > Attachments: ATLAS-2803-2012-08-02.patch > > > The AtlasEnumDef toString() does not include the defaultValue of the enum. > The AtlasRelationshipDef toString() does not validate ends before > dereferencing them - causes NPEs in test scenarios -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2803) Additions to AtlasEnumDef and AtlasRelationshipDef toString() methods
[ https://issues.apache.org/jira/browse/ATLAS-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis resolved ATLAS-2803. -- Resolution: Fixed > Additions to AtlasEnumDef and AtlasRelationshipDef toString() methods > - > > Key: ATLAS-2803 > URL: https://issues.apache.org/jira/browse/ATLAS-2803 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Assignee: Graham Wallis >Priority: Minor > Fix For: 2.0.0 > > Attachments: ATLAS-2803-2012-08-02.patch > > > The AtlasEnumDef toString() does not include the defaultValue of the enum. > The AtlasRelationshipDef toString() does not validate ends before > dereferencing them - causes NPEs in test scenarios -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2803) Additions to AtlasEnumDef and AtlasRelationshipDef toString() methods
[ https://issues.apache.org/jira/browse/ATLAS-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2803: - Attachment: ATLAS-2803-2012-08-02.patch > Additions to AtlasEnumDef and AtlasRelationshipDef toString() methods > - > > Key: ATLAS-2803 > URL: https://issues.apache.org/jira/browse/ATLAS-2803 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Minor > Attachments: ATLAS-2803-2012-08-02.patch > > > The AtlasEnumDef toString() does not include the defaultValue of the enum. > The AtlasRelationshipDef toString() does not validate ends before > dereferencing them - causes NPEs in test scenarios -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2803) Additions to AtlasEnumDef and AtlasRelationshipDef toString() methods
Graham Wallis created ATLAS-2803: Summary: Additions to AtlasEnumDef and AtlasRelationshipDef toString() methods Key: ATLAS-2803 URL: https://issues.apache.org/jira/browse/ATLAS-2803 Project: Atlas Issue Type: Improvement Reporter: Graham Wallis The AtlasEnumDef toString() does not include the defaultValue of the enum. The AtlasRelationshipDef toString() does not validate ends before dereferencing them - causes NPEs in test scenarios -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-07-12.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-08-02.patch, > ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-08-02.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-07-12.patch, > ATLAS-1773-2018-08-02.patch, ATLAS-1799-nigel-fixup-20180718a,.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2796) Default Atlas configuration of graph lock wait time seems excessive
[ https://issues.apache.org/jira/browse/ATLAS-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563829#comment-16563829 ] Graham Wallis commented on ATLAS-2796: -- [~madhan.neethiraj] - thanks Madhan. The key thing is that the default value is very long and is what causes the 10s delays seen during mgmt commits. We could leave the default at 10s if there is a good reason for having it so long; but it means that anyone wanting reasonable performance would have to override the default. > Default Atlas configuration of graph lock wait time seems excessive > --- > > Key: ATLAS-2796 > URL: https://issues.apache.org/jira/browse/ATLAS-2796 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Major > > For some reason the default configuration sets a 10s timeout for internal > graph locks. > This seems to have been introduced in ATLAS-833. Does anyone know why such a > high value is needed? > I propose setting to to 100ms. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2796) Default Atlas configuration of graph lock wait time seems excessive
Graham Wallis created ATLAS-2796: Summary: Default Atlas configuration of graph lock wait time seems excessive Key: ATLAS-2796 URL: https://issues.apache.org/jira/browse/ATLAS-2796 Project: Atlas Issue Type: Improvement Reporter: Graham Wallis For some reason the default configuration sets a 10s timeout for internal graph locks. This seems to have been introduced in ATLAS-833. Does anyone know why such a high value is needed? I propose setting to to 100ms. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: ATLAS-1773-2018-07-12.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-07-12.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: Notes on running the OMRS stack including the Atlas OMRS connector.txt) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-07-12.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: ATLAS-1773-2018-06-07.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: Notes on running the OMRS stack including the Atlas OMRS > connector.txt > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: (was: RELATIONSHIP_DEFS_AS_ASSOCIATIONS.patch) > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: Notes on running the OMRS stack including the Atlas OMRS > connector.txt > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2787) Clean out redundant OMAG modulles
[ https://issues.apache.org/jira/browse/ATLAS-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2787: - Attachment: ATLAS-2787-2018-07-12.patch > Clean out redundant OMAG modulles > - > > Key: ATLAS-2787 > URL: https://issues.apache.org/jira/browse/ATLAS-2787 > Project: Atlas > Issue Type: Improvement >Reporter: Graham Wallis >Priority: Minor > Attachments: ATLAS-2787-2018-07-12.patch > > > It would be good to clear out the OM modules that are no longer needed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2787) Clean out redundant OMAG modulles
Graham Wallis created ATLAS-2787: Summary: Clean out redundant OMAG modulles Key: ATLAS-2787 URL: https://issues.apache.org/jira/browse/ATLAS-2787 Project: Atlas Issue Type: Improvement Reporter: Graham Wallis It would be good to clear out the OM modules that are no longer needed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-2774) Options for hard and soft delete of instances
[ https://issues.apache.org/jira/browse/ATLAS-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532886#comment-16532886 ] Graham Wallis commented on ATLAS-2774: -- Thanks David - useful comments One slight change to the original description above, that became apparent when I started to write some initial implementation and asked for clarification from Mandy - If Atlas is configured for soft delete, then an OMRS purgeEntity() or purgeRelationship() will insist that the entity or relationship has been soft-deleted before doing the purge. In this configuration an entity or relationship must be in DELETED state otherwise purge will refuse to hard delete. If Atlas is configured for hard delete, then purge will remove the entity or relationship regardless of its state - so it will remove an entity or relationship that is in ACTIVE (or DELETED state). > Options for hard and soft delete of instances > - > > Key: ATLAS-2774 > URL: https://issues.apache.org/jira/browse/ATLAS-2774 > Project: Atlas > Issue Type: New Feature >Reporter: Graham Wallis >Priority: Major > > *Overview* > For Entities and Relationships, the following delete behaviors are desired. > Atlas can be configured to offer hard delete (only). Alternatively it can be > configured to offer soft-delete. Configuration is achieved by setting the > delete handler configuration property (see atlas-application.properties) to > either the SoftDeleteHandlerV1 or the HardDeleteHandlerV1. The default (for > when the property is not set) is to use the SoftDeleteHandlerV1. > The AtlasEntityStoreV2 deleteById() and deleteByIds() and methods and the > AtlasRelationshipStoreV2 deleteById() method are sensitive to the above > configuration. When the configuration is soft these methods will perform a > soft delete; when it is hard they will perform a hard delete. > In addition to the above methods, the AtlasEntityStoreV2 and > AtlasRelationshipStoreV2 offer a (new) purgeById() method that ALWAYS > performs a hard delete. This is true regardless of which delete handler has > been configured. When the configuration is hard, the purgeById() methods and > deleteById() methods are essentially equivalent. When the configuration is > soft, the purgeById() methods continue to provide a hard delete capability. > The AtlasEntityStoreV2 deleteById(), deleteByIds() and purgeById() methods > will delete the specified entities and any relationships to which they are > connected. The AtlasRelationshipStoreV2 deleteById() and purgeById() methods > will delete the specified relationship. Deletion of a relationship may cause > an upate to an entity to which the relationhsip is connected, if it changes > the propagation of classifications, for example. > In a hard delete or purge operation, an affected entity and relationship will > be removed from the graph and will not be returned in response to any future > queries. This is true regardless of whether the affected entity or > relationship has already been soft deleted or not. i.e. it's status could > initially be ACTIVE or DELETED. Following the operation it will not exist. > In a soft delete, the affected entities and relationships (that initially > have status ACTIVE) are updated to set the status to DELETED. These instances > can still be returned from queries and searches if the appropriate control is > selected (to include deleted instances). Without that control selected they > will not be returned. > *Use Case for soft delete* > Soft delete provides a 'safe' means of deleting instances from the repository > whilst preserving an audit trail and (if supported by the repository) > enabling a deleted instance to be restored (to ACTIVE status). > *Use Cases for hard delete* > One use case for hard delete is to permanently remove soft-deleted items some > period of time after they were soft deleted. > Another use case for hard delete is to is to correct (clean up after) a > mistake in which a potentially large batch of incomplete/corrupted/wrong > metadata is loaded and needs to be fully removed. > *Use Scenario for an OMAS user* > An OMAS provides a delete function that does NOT offer the user a choice of > hard/soft. The OMAS's delete function will invoke the relevant soft delete > method provided by the OMRS - deleteEntity or deleteRelationship. These are > both soft delete methods. > The Atlas OMRS Connector's deleteEntity/deleteRelationship methods will check > whether Atlas is configured for hard or soft delete. If Atlas is configured > for hard delete then soft-delete is not possible, and the method will throw a > FunctionNotSupported exception which is caught by the OMAS. > On catching this exception the OMAS author should automatically escalate the > soft delete to a hard delete
[jira] [Updated] (ATLAS-2774) Options for hard and soft delete of instances
[ https://issues.apache.org/jira/browse/ATLAS-2774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-2774: - Description: *Overview* For Entities and Relationships, the following delete behaviors are desired. Atlas can be configured to offer hard delete (only). Alternatively it can be configured to offer soft-delete. Configuration is achieved by setting the delete handler configuration property (see atlas-application.properties) to either the SoftDeleteHandlerV1 or the HardDeleteHandlerV1. The default (for when the property is not set) is to use the SoftDeleteHandlerV1. The AtlasEntityStoreV2 deleteById() and deleteByIds() and methods and the AtlasRelationshipStoreV2 deleteById() method are sensitive to the above configuration. When the configuration is soft these methods will perform a soft delete; when it is hard they will perform a hard delete. In addition to the above methods, the AtlasEntityStoreV2 and AtlasRelationshipStoreV2 offer a (new) purgeById() method that ALWAYS performs a hard delete. This is true regardless of which delete handler has been configured. When the configuration is hard, the purgeById() methods and deleteById() methods are essentially equivalent. When the configuration is soft, the purgeById() methods continue to provide a hard delete capability. The AtlasEntityStoreV2 deleteById(), deleteByIds() and purgeById() methods will delete the specified entities and any relationships to which they are connected. The AtlasRelationshipStoreV2 deleteById() and purgeById() methods will delete the specified relationship. Deletion of a relationship may cause an upate to an entity to which the relationhsip is connected, if it changes the propagation of classifications, for example. In a hard delete or purge operation, an affected entity and relationship will be removed from the graph and will not be returned in response to any future queries. This is true regardless of whether the affected entity or relationship has already been soft deleted or not. i.e. it's status could initially be ACTIVE or DELETED. Following the operation it will not exist. In a soft delete, the affected entities and relationships (that initially have status ACTIVE) are updated to set the status to DELETED. These instances can still be returned from queries and searches if the appropriate control is selected (to include deleted instances). Without that control selected they will not be returned. *Use Case for soft delete* Soft delete provides a 'safe' means of deleting instances from the repository whilst preserving an audit trail and (if supported by the repository) enabling a deleted instance to be restored (to ACTIVE status). *Use Cases for hard delete* One use case for hard delete is to permanently remove soft-deleted items some period of time after they were soft deleted. Another use case for hard delete is to is to correct (clean up after) a mistake in which a potentially large batch of incomplete/corrupted/wrong metadata is loaded and needs to be fully removed. *Use Scenario for an OMAS user* An OMAS provides a delete function that does NOT offer the user a choice of hard/soft. The OMAS's delete function will invoke the relevant soft delete method provided by the OMRS - deleteEntity or deleteRelationship. These are both soft delete methods. The Atlas OMRS Connector's deleteEntity/deleteRelationship methods will check whether Atlas is configured for hard or soft delete. If Atlas is configured for hard delete then soft-delete is not possible, and the method will throw a FunctionNotSupported exception which is caught by the OMAS. On catching this exception the OMAS author should automatically escalate the soft delete to a hard delete by calling either of the mandatory OMRS purgeEntity() or purgeRelationship() methods. In the Atlas OMRS Connector these methods will invoke AtlasEntityStoreV2 purgeById() or AtlasRelationshipStoreV2 purgeById(). The effect of this is that if soft delete is not possible, a hard delete is used instead. An OMAS does NOT provide a purge capability to a non-privileged user, but a suitably expert OMRS or Atlas repository administrator can explicitly issue a purge call at the OMRS or Atlas interface, by calling purgeEntity() or purgeRelationship() (or the relevant Atlas store's purgeById() method). *Use Scenario for an Administrator* As highlighted above, a suitably expert repository Administrator can invoke the purgeEntity(), purgeRelationship() methods directly. They may need to do this to permanently remove instances following an earlier soft-delete and the timeout of a period of grace, or following a failed import or batch update. In addition to the above direct use by a repository administrator of the 'purge' methods, an Administrator could alternatively use the deleteEntity(), deleteRelationship() methods to perform soft deletes.
[jira] [Created] (ATLAS-2774) Options for hard and soft delete of instances
Graham Wallis created ATLAS-2774: Summary: Options for hard and soft delete of instances Key: ATLAS-2774 URL: https://issues.apache.org/jira/browse/ATLAS-2774 Project: Atlas Issue Type: New Feature Reporter: Graham Wallis *Overview* For Entities and Relationships, the following delete behaviors are desired. Atlas can be configured to offer hard delete (only). Alternatively it can be configured to offer soft-delete. Configuration is achieved by setting the delete handler configuration property (see atlas-application.properties) to either the SoftDeleteHandlerV1 or the HardDeleteHandlerV1. The default (for when the property is not set) is to use the SoftDeleteHandlerV1. The AtlasEntityStoreV2 deleteById() and deleteByIds() and methods and the AtlasRelationshipStoreV2 deleteById() method are sensitive to the above configuration. When the configuration is soft these methods will perform a soft delete; when it is hard they will perform a hard delete. In addition to the above methods, the AtlasEntityStoreV2 and AtlasRelationshipStoreV2 offer a (new) purgeById() method that ALWAYS performs a hard delete. This is true regardless of which delete handler has been configured. When the configuration is hard, the purgeById() methods and deleteById() methods are essentially equivalent. When the configuration is soft, the purgeById() methods continue to provide a hard delete capability. The AtlasEntityStoreV2 deleteById(), deleteByIds() and purgeById() methods will delete the specified entities and any relationships to which they are connected. The AtlasRelationshipStoreV2 deleteById() and purgeById() methods will delete the specified relationship. Deletion of a relationship may cause an upate to an entity to which the relationhsip is connected, if it changes the propagation of classifications, for example. In a hard delete or purge operation, an affected entity and relationship will be removed from the graph and will not be returned in response to any future queries. This is true regardless of whether the affected entity or relationship has already been soft deleted or not. i.e. it's status could initially be ACTIVE or DELETED. Following the operation it will not exist. In a soft delete, the affected entities and relationships (that initially have status ACTIVE) are updated to set the status to DELETED. These instances can still be returned from queries and searches if the appropriate control is selected (to include deleted instances). Without that control selected they will not be returned. *Use Case for soft delete* Soft delete provides a 'safe' means of deleting instances from the repository whilst preserving an audit trail and (if supported by the repository) enabling a deleted instance to be restored (to ACTIVE status). *Use Cases for hard delete* One use case for hard delete is to permanently remove soft-deleted items some period of time after they were soft deleted. Another use case for hard delete is to is to correct (clean up after) a mistake in which a potentially large batch of incomplete/corrupted/wrong metadata is loaded and needs to be fully removed. *Use Scenario for an OMAS user* An OMAS provides a delete function that does NOT offer the user a choice of hard/soft. The OMAS's delete function will invoke the relevant soft delete method provided by the OMRS - deleteEntity or deleteRelationship. These are both soft delete methods. The Atlas OMRS Connector's deleteEntity/deleteRelationship methods will check whether Atlas is configured for hard or soft delete. If Atlas is configured for hard delete then soft-delete is not possible, and the method will throw a FunctionNotSupported exception which is caught by the OMAS. On catching this exception the OMAS author should automatically escalate the soft delete to a hard delete by calling either of the mandatory OMRS purgeEntity() or purgeRelationship() methods. In the Atlas OMRS Connector these methods will invoke AtlasEntityStoreV2 purgeById() or AtlasRelationshipStoreV2 purgeById(). The effect of this is that if soft delete is not possible, a hard delete is used instead. An OMAS does NOT provide a purge capability to a non-privileged user, but a suitably expert OMRS or Atlas repository administrator can explicitly issue a purge call at the OMRS or Atlas interface, by calling purgeEntity() or purgeRelationship() (or the relevant Atlas store's purgeById() method). *Use Scenario for an Administrator* As highlighted above, a suitably expert repository Administrator can invoke the purgeEntity(), purgeRelationship() methods directly. They may need to do this to permanently remove instances following an earlier soft-delete and the timeout of a period of grace, or following a failed import or batch update. In addition to the above direct use by a repository administrator of
[jira] [Updated] (ATLAS-1773) Create the OMRS Connector for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Wallis updated ATLAS-1773: - Attachment: RELATIONSHIP_DEFS_AS_ASSOCIATIONS.patch > Create the OMRS Connector for Atlas > --- > > Key: ATLAS-1773 > URL: https://issues.apache.org/jira/browse/ATLAS-1773 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Graham Wallis >Priority: Major > Attachments: ATLAS-1773-2018-06-07.patch, Notes on running the OMRS > stack including the Atlas OMRS connector.txt, > RELATIONSHIP_DEFS_AS_ASSOCIATIONS.patch > > > This JIRA provides the definition of the OMRS Connector API and an > implementation of this API for a local Apache Atlas metadata repository and > for the OMRS REST API. > The OMRS Connector has 3 API groups > * The types API - this is the metadata API for a metadata repository > * The entity and relationships APIs that provide the type-agnostic interfaces > that can access any type - even those added dynamically > * The fine-grained type-safe APIs that are generated from the addons models > in the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
