[jira] [Commented] (ATLAS-1836) Area 0 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060839#comment-16060839 ] Mandy Chessell commented on ATLAS-1836: --- Comment from David Radley ([~davidrad]) made on the Wiki page: david radley Mandy Chessell . Some comments on Versioned Assets, I am wondering what I am missing and had some questions: I see that Versionable is a Referenceable and has a Version Guid, label and start and end time. The existing EntityDefs are Referencables and have a Version label. Do we need to have entityDefs that are not versioned? I assume the versionGuid refers to a Version artifact that has a Guid. Or is this guid unique to the entity - if so how is it useful and different from the existing entity guid? Maybe Verions are top level entities that need to be governed (controlled and managed consistently according to standard practices). It seems to me that we would want some sense of order in the versions so there is a the concept of lower and higher versions. Maybe this as simple as ordering the String. If there was a Version object - I assume it would handle the order. Presumably updates could only be made to an entityDef that make the version higher? Is there a scope for a particular version? Currently Atlas does not allow more than one EntityDef to exist with the same name. Are we suggesting that we could allow multiple active versions? If an entityDef is moved to a new version, I assume its relationships to supertypes and other entityDefs need to be copied from the newly cloned vertex to the historical vertex? We are likely going to need a new label for these version relationships. I suggest ActionLogEntry is changed from a structure to an entity. I assume (probably incorrectly) ActionLogEntry will end up an an entry in a log. If so, it should have the guid of the entityDef that the action occurred on. I am not sure what the version status means on the relationship - shouldn't the status of a version be on the versionable entity itself? Otherwise, if we say that the status on the relationship is ACTIVE, does this refer to the future or the previous version? Why is the previous Version relationship end not on versionable? In terms of the next steps to get this into Atlas, do we need the ActionLogEntry at the beginning? Maybe the new version attributes and the relationship could be added as a first step. If we order based on the version label string itself, we would ensure that only updates to higher versions occur and Atlas would create the version relationship when there is an update to version. > Area 0 of the open metadata model > - > > Key: ATLAS-1836 > URL: https://issues.apache.org/jira/browse/ATLAS-1836 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Mandy Chessell >Assignee: Mandy Chessell > Labels: OpenMetadata, VirtualDataConnector > > This task delivers the JSON files for the new models that describe types for > Area 0 in the open metadata model. This area covers base types. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1836) Area 0 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060841#comment-16060841 ] Mandy Chessell commented on ATLAS-1836: --- Reply to David Radley's comments abover Referenceable is part of the existing base model - not all entities are referenceable just as not all entities are versionable. The previous version may be a Referenceable if it was created before its type was upgraded to be versionable. We agreed in the review meeting for this area that the design for versioning should be covered with a separated design doc and JIRA however, these are the answers to your questions: A versionable entity instance needs a GUID for its version and a GUID for the entity. Each version of an entity instance would have the same entity GUID and a different version GUID. The GUID for the version will probably be the GUID that is managed by Atlas - and the one called VersionGUID would hold the common GUID of the entity. When a Versionable entity instance is updated, a copy of the vertex for itself and vertices for its structs are made into new vertices. These new vertices represent the previous version. The GUID of the new vertex will be the version's GUID. The new vertices are chained off of the current node as the PREVIOUS_VERSION. The vertices for the original versionable entity's properties are updated. Thus the entity GUID remains stable because the actual vertex of the active copy never changes. There would only ever be one active version of an entity instance at any one time. This is indicated in the VersionStatus. If we see more than one then there is a bug in the versioning code. ActionLogEntry is a set of properties - not an external log file. It is part of the entity - hence struct seems right for this - why would it be an independent entity? It is never referenced outside of the context of the entity. We need it now The status of the version determines which stage of the workflow that the entity is in - ACTIVE_VERSION means the version of the entity is active. DRAFT_VERSION means the version of the entity is still in draft because someone is still editting it etc ... I am not sure these questions are relevant in order to move the code forward now - they are just establishing that structures are in place. They should be set to reasonable defaults while versioning in not implemented. > Area 0 of the open metadata model > - > > Key: ATLAS-1836 > URL: https://issues.apache.org/jira/browse/ATLAS-1836 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Mandy Chessell >Assignee: Mandy Chessell > Labels: OpenMetadata, VirtualDataConnector > > This task delivers the JSON files for the new models that describe types for > Area 0 in the open metadata model. This area covers base types. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-1898) Initial commit to feature-odf branch
Mandy Chessell created ATLAS-1898: - Summary: Initial commit to feature-odf branch Key: ATLAS-1898 URL: https://issues.apache.org/jira/browse/ATLAS-1898 Project: Atlas Issue Type: Sub-task Components: atlas-core Reporter: Mandy Chessell This is the initial commit of the ODF code. The changes from the initial IBM code drop basically change java package names from com.ibm.iis.odf.* to org.apache.atlas.odf.*. There are still references to IBM Box directories where deployment scripts look for the Atlas build. these scripts need rethinking as we make the ODF a buildable component of Atlas -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1898) Initial commit to feature-odf branch
[ https://issues.apache.org/jira/browse/ATLAS-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1898: -- Attachment: 0001-ATLAS-1898-initial-commit-of-ODF.patch > Initial commit to feature-odf branch > > > Key: ATLAS-1898 > URL: https://issues.apache.org/jira/browse/ATLAS-1898 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Reporter: Mandy Chessell > Labels: open-metadata > Attachments: 0001-ATLAS-1898-initial-commit-of-ODF.patch > > > This is the initial commit of the ODF code. The changes from the initial IBM > code drop basically change java package names from com.ibm.iis.odf.* to > org.apache.atlas.odf.*. There are still references to IBM Box directories > where deployment scripts look for the Atlas build. these scripts need > rethinking as we make the ODF a buildable component of Atlas -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1898) Initial commit to feature-odf branch
[ https://issues.apache.org/jira/browse/ATLAS-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1898: -- Attachment: 0002-ATLAS-1898-initial-commit-of-ODF.patch > Initial commit to feature-odf branch > > > Key: ATLAS-1898 > URL: https://issues.apache.org/jira/browse/ATLAS-1898 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Reporter: Mandy Chessell > Labels: open-metadata > Attachments: 0001-ATLAS-1898-initial-commit-of-ODF.patch, > 0002-ATLAS-1898-initial-commit-of-ODF.patch > > > This is the initial commit of the ODF code. The changes from the initial IBM > code drop basically change java package names from com.ibm.iis.odf.* to > org.apache.atlas.odf.*. There are still references to IBM Box directories > where deployment scripts look for the Atlas build. these scripts need > rethinking as we make the ODF a buildable component of Atlas -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1839) Area 2 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066424#comment-16066424 ] Mandy Chessell commented on ATLAS-1839: --- Comments added by [~davidrad] to the wiki I think this model is very comprehensive. I had some minor observations: - Taxonomy is already used for the legacy model -so I cannot load a Classifaction with this name - I assume that the relationship attribute 'source' in Related Term should be of type ExternalReference not string - I think CategoryAnchor endname category should be categories to make is consistent with the plural terms in the GlossaryTerm equivalent. - i am wondering whether ISA should be IsA - this would seem more inline with the other capitalization. At the same time I notice the spine Object model uses capitalized forms for TYPEDBY - I wondered why these are capitalized. Is this a hangover from upper cased SQL names - or is there another reason? > Area 2 of the open metadata model > - > > Key: ATLAS-1839 > URL: https://issues.apache.org/jira/browse/ATLAS-1839 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Mandy Chessell >Assignee: Mandy Chessell > Labels: OpenMetadata, VirtualDataConnector > Attachments: 0005LinkedMediaTypes.json > > > This task delivers the JSON files for the new models that describe types for > Area 2 in the open metadata model. This area covers the glossary. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1839) Area 2 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068811#comment-16068811 ] Mandy Chessell commented on ATLAS-1839: --- I will change "Taxomony" to "IsTaxonomy" Source will have to be a string because structs are not allowed in the relationship attributes. Using capitalization has no influence from SQL. They are used on the relationship names to make the type of relationship stand out. When mixed case they were difficult to read. > Area 2 of the open metadata model > - > > Key: ATLAS-1839 > URL: https://issues.apache.org/jira/browse/ATLAS-1839 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Mandy Chessell >Assignee: Mandy Chessell > Labels: OpenMetadata, VirtualDataConnector > Attachments: 0210Glossary.json, 0220CategoryHierarchy.json, > 0230Terms.json, 0240Dictionary.json, 0250RelatedTerms.json > > > This task delivers the JSON files for the new models that describe types for > Area 2 in the open metadata model. This area covers the glossary. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1774) Create the OMRS Connector for IBM's Information Governance Catalog (IGC)
[ https://issues.apache.org/jira/browse/ATLAS-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1774: -- Summary: Create the OMRS Connector for IBM's Information Governance Catalog (IGC) (was: Create the OMRS Connector for IBM's Information Governance Catalog) > Create the OMRS Connector for IBM's Information Governance Catalog (IGC) > > > Key: ATLAS-1774 > URL: https://issues.apache.org/jira/browse/ATLAS-1774 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 0.9-incubating >Reporter: Mandy Chessell >Assignee: Mandy Chessell > > This JIRA provides a connector for IBM’s Information Governance Catalog that > implements the OMRS Connector API defined in JIRA ATLAS-1773. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (ATLAS-2617) Enable multiple annotation schemes for open metadata REST APIs
Mandy Chessell created ATLAS-2617: - Summary: Enable multiple annotation schemes for open metadata REST APIs Key: ATLAS-2617 URL: https://issues.apache.org/jira/browse/ATLAS-2617 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: 1.0.0-alpha Reporter: Mandy Chessell Assignee: Mandy Chessell Fix For: 1.0.0 The Atlas server is using the Spring framework and Jersey. The OMAG server is using spring boot. The annotations needed for each of these technologies is slightly different so we need to create a thin annotation class for each environment and delegate to the REST API logic from each annotation class. This affects the OMAG API, OMRS API and the OMAS APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2617) Enable multiple annotation schemes for open metadata REST APIs
[ https://issues.apache.org/jira/browse/ATLAS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-2617: -- Attachment: 0003-ATLAS-2617-Open-Metadata-annotation-files.patch > Enable multiple annotation schemes for open metadata REST APIs > -- > > Key: ATLAS-2617 > URL: https://issues.apache.org/jira/browse/ATLAS-2617 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > Attachments: 0003-ATLAS-2617-Open-Metadata-annotation-files.patch > > > The Atlas server is using the Spring framework and Jersey. The OMAG server > is using spring boot. The annotations needed for each of these technologies > is slightly different so we need to create a thin annotation class for each > environment and delegate to the REST API logic from each annotation class. > This affects the OMAG API, OMRS API and the OMAS APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ATLAS-2621) Validate properties against full supertype hierarchy (and change update instance events)
Mandy Chessell created ATLAS-2621: - Summary: Validate properties against full supertype hierarchy (and change update instance events) Key: ATLAS-2621 URL: https://issues.apache.org/jira/browse/ATLAS-2621 Project: Atlas Issue Type: Improvement Components: atlas-core Affects Versions: 1.0.0-alpha Reporter: Mandy Chessell Assignee: Mandy Chessell Fix For: 1.0.0 Daniella discovered that adding an entity which inherits its properties from super types fails validation. This is because the repository validator does not walk the supertype hierarchy. I also changes the update instance events to provide both the before and after version of the event so that the listener can understand what has changed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (ATLAS-2621) Validate properties against full supertype hierarchy (and change update instance events)
[ https://issues.apache.org/jira/browse/ATLAS-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-2621: -- Attachment: 0004-ATLAS-2621-fix-poperty-validation.patch > Validate properties against full supertype hierarchy (and change update > instance events) > > > Key: ATLAS-2621 > URL: https://issues.apache.org/jira/browse/ATLAS-2621 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > Attachments: 0004-ATLAS-2621-fix-poperty-validation.patch > > > Daniella discovered that adding an entity which inherits its properties from > super types fails validation. This is because the repository validator does > not walk the supertype hierarchy. > I also changes the update instance events to provide both the before and > after version of the event so that the listener can understand what has > changed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1754) Self-Service User Interfaces for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1754. --- Resolution: Duplicate This feature has been moved to Egeria: https://odpi.github.io/egeria/open-metadata-implementation/user-interfaces/ > Self-Service User Interfaces for Atlas > -- > > Key: ATLAS-1754 > URL: https://issues.apache.org/jira/browse/ATLAS-1754 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 1.0.0 > Environment: Providing access to Atlas metadata for information > consumers and data governance team. >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: BusinessUserUI > Attachments: Pharma - Personas - 17th June 2016.ppt, Pharma - > Personas and Roles in Action - 4th July 2016.pptx > > > Apache Atlas collects information about an organization's data assets. This > JIRA provides a role-based user interface to enable people in the > organization to locate, use, manage and govern these assets. The personas > that it will support are: > - Data scientists and citizen analysts (business people working with data) > wishing to locate and use data. > - Application developers wanting to use standard structures in their APIs > and to understand the rules that apply to the data they are processing with > the API. > - Data engineers and information architects supporting the data platforms > and integrations that support the business. These people use metadata to > create strong information supply chains that deliver data to the > organization. They also deploy analytics created by data scientists and > citizen analytics into production and build analytical processes themselves. > - Data owners (any role) wanting to improve the description of their data > asset, to classify their asset and to understand how their data assets are > being used. > - Governance team members from CDO, to data owners to data stewards and > custodians that define and monitor the metadata used to manage and govern the > data. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1765) Self-Service Catalog Search and Data Preview
[ https://issues.apache.org/jira/browse/ATLAS-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1765. --- Resolution: Fixed Business User Interface implementation moved to Egeria: see [https://github.com/odpi/egeria/tree/master/open-metadata-implementation/user-interfaces/access-services-user-interface.|http://example.com](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/user-interfaces/access-services-user-interface) > Self-Service Catalog Search and Data Preview > > > Key: ATLAS-1765 > URL: https://issues.apache.org/jira/browse/ATLAS-1765 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: BusinessUserUI, Self-Service-UIs, VirtualDataConnector > > This JIRA covers the development of the catalog search and preview of data > for data scientists and business users. It supports the search of the Atlas > metadata repository, display of search results, additional filtering and > drill down into details of the data sources, including a data preview option > if the end user has access permission. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1765) Self-Service Catalog Search and Data Preview
[ https://issues.apache.org/jira/browse/ATLAS-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542864#comment-16542864 ] Mandy Chessell commented on ATLAS-1765: --- New Jira number: [https://jira.odpi.org/browse/EGERIA-22|http://example.com]. > Self-Service Catalog Search and Data Preview > > > Key: ATLAS-1765 > URL: https://issues.apache.org/jira/browse/ATLAS-1765 > Project: Atlas > Issue Type: New Feature > Components: atlas-webui >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: BusinessUserUI, Self-Service-UIs, VirtualDataConnector > > This JIRA covers the development of the catalog search and preview of data > for data scientists and business users. It supports the search of the Atlas > metadata repository, display of search results, additional filtering and > drill down into details of the data sources, including a data preview option > if the end user has access permission. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1748) Automated Metadata Discovery
[ https://issues.apache.org/jira/browse/ATLAS-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1748. --- Resolution: Won't Fix This capability is now being delivered in Egeria https://jira.odpi.org/browse/EGERIA-27 > Automated Metadata Discovery > > > Key: ATLAS-1748 > URL: https://issues.apache.org/jira/browse/ATLAS-1748 > Project: Atlas > Issue Type: New Feature > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Priority: Major > > This JIRA proposes a framework for managing automated metadata discovery > analytics. The framework is called when Atlas receives a notification about > new or (significantly) updated data. It selects a discovery pipeline and > runs it. The discovery pipeline is a list of pluggable discovery components > that are called in sequence. The later components in the pipeline can access > the results of the previous components. The results of the pipeline are > added to the Apache Atlas metadata entry for the data source. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1847) Open Metadata and Governance
[ https://issues.apache.org/jira/browse/ATLAS-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551038#comment-16551038 ] Mandy Chessell commented on ATLAS-1847: --- After 9 months incubating the open metadata function in Apache Atlas, we jointly realized that it was ready to become its own project. The code is now managed in the Egeria project (https://github.com/odpi/egeria/) > Open Metadata and Governance > > > Key: ATLAS-1847 > URL: https://issues.apache.org/jira/browse/ATLAS-1847 > Project: Atlas > Issue Type: New Feature >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata, open-metadata > > This JIRA covers the architecture and tracking of the open metadata and > governance initiative for Apache Atlas. > Open metadata and governance is a moon-shot type of project to create a open > set of APIs, types and interchange protocols to allow all metadata > repositories to share and exchange metadata. From this common base, it adds > governance, discovery and access frameworks to automate the collection, > management and use of metadata across an enterprise. The result is an > enterprise catalog of data resources that are transparently assessed, > governed and used in order to deliver maximum value to the enterprise. > Delivering this capability as open source is a critical part of the project > since multiple vendors must buy into this ecosystem. They are not going to > do this if one organization dominates the technology base. Thus the open > metadata and governance technology must be freely available with an open > source governance model that allows a community of organizations and > practitioners to develop and evolve the base and then use it in their > offerings and deployments. > The proposal is to use Apache Atlas as the open source reference > implementation for open metadata and governance. Apache Alas will support an > open metadata and governance compliant repository plus provide the adapters > and interchange formats to allow other metadata repositories to connect into > the ecosystem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1847) Open Metadata and Governance
[ https://issues.apache.org/jira/browse/ATLAS-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1847. --- Resolution: Fixed Function moved to https://github.com/odpi/egeria > Open Metadata and Governance > > > Key: ATLAS-1847 > URL: https://issues.apache.org/jira/browse/ATLAS-1847 > Project: Atlas > Issue Type: New Feature >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata, open-metadata > > This JIRA covers the architecture and tracking of the open metadata and > governance initiative for Apache Atlas. > Open metadata and governance is a moon-shot type of project to create a open > set of APIs, types and interchange protocols to allow all metadata > repositories to share and exchange metadata. From this common base, it adds > governance, discovery and access frameworks to automate the collection, > management and use of metadata across an enterprise. The result is an > enterprise catalog of data resources that are transparently assessed, > governed and used in order to deliver maximum value to the enterprise. > Delivering this capability as open source is a critical part of the project > since multiple vendors must buy into this ecosystem. They are not going to > do this if one organization dominates the technology base. Thus the open > metadata and governance technology must be freely available with an open > source governance model that allows a community of organizations and > practitioners to develop and evolve the base and then use it in their > offerings and deployments. > The proposal is to use Apache Atlas as the open source reference > implementation for open metadata and governance. Apache Alas will support an > open metadata and governance compliant repository plus provide the adapters > and interchange formats to allow other metadata repositories to connect into > the ecosystem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1691) OMAS Interfaces for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1691. --- Resolution: Information Provided > OMAS Interfaces for Atlas > - > > Key: ATLAS-1691 > URL: https://issues.apache.org/jira/browse/ATLAS-1691 > Project: Atlas > Issue Type: Improvement >Reporter: Nigel Jones >Assignee: Mandy Chessell >Priority: Major > Labels: VirtualDataConnector > > The Open Metadata Access Services (OMAS) provide consumer specific interfaces > to the metadata repository. The hope is to have a community of vendor tools > developing around each OMAS interface. The OMAS interfaces are independent > from one another to allow each community to evolve their own API at their > pace. > Related Jira will cover the list of OMAS interfaces that are oriented to > particular tools & usage. > Each OMAS JIRA needs to cover: > * The Java and REST API for the OMAS call-response API > * The appropriate OMAS Event Publisher and Listener -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1691) OMAS Interfaces for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551195#comment-16551195 ] Mandy Chessell commented on ATLAS-1691: --- Implementation of OMASs moved to Egeria https://github.com/odpi/egeria > OMAS Interfaces for Atlas > - > > Key: ATLAS-1691 > URL: https://issues.apache.org/jira/browse/ATLAS-1691 > Project: Atlas > Issue Type: Improvement >Reporter: Nigel Jones >Assignee: Mandy Chessell >Priority: Major > Labels: VirtualDataConnector > > The Open Metadata Access Services (OMAS) provide consumer specific interfaces > to the metadata repository. The hope is to have a community of vendor tools > developing around each OMAS interface. The OMAS interfaces are independent > from one another to allow each community to evolve their own API at their > pace. > Related Jira will cover the list of OMAS interfaces that are oriented to > particular tools & usage. > Each OMAS JIRA needs to cover: > * The Java and REST API for the OMAS call-response API > * The appropriate OMAS Event Publisher and Listener -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1768) Create common types for Open Metadata
[ https://issues.apache.org/jira/browse/ATLAS-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1768. --- Resolution: Fixed The open metadata types are implemented in ODPi Egeria: https://odpi.github.io/egeria/open-metadata-publication/website/open-metadata-types/ > Create common types for Open Metadata > - > > Key: ATLAS-1768 > URL: https://issues.apache.org/jira/browse/ATLAS-1768 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata > > This JIRA describes a proposal for standard types for open metadata entities > and relationships. For example, glossaries, database definitions, rules, > policies, ... > The value of having standard definitions for metadata is to enable type safe > APIs and business level UIs plus be able to exchange metadata between > different instances of metadata repositories. > The implementation of these common types is divided into 8 areas: > * Area 0 - for extensions to Apache Atlas's base model > * Area 1 - for definitions of the data-related assets we are governing and > using > * Area 2 - for a glossary of meanings and semantic relationships > * Area 3 - for information about asset use, crowd-sourced definitions and > collaboration around the data-related assets > * Area 4 - for governance such as policies, rules and classifications > * Area 5 - for reference models and reference data > * Area 6 - for metadata discovery processes (see > https://issues.apache.org/jira/browse/ATLAS-1748) > * Area 7 - for lineage > Adaptation and flexibility are key in metadata environments so these common > definitions must be extensible - and we still need to support the ad hoc > definition of new types in Atlas. > Apache Atlas supports meta-types that are used in the definition of new > types. These are currently enumeration, struct, classification and entity. > JIRA https://issues.apache.org/jira/browse/ATLAS-1690 adds relationships to > this list. The open metadata models make use of all of these meta-types. > These are represented by sterotypes on the classes of the open metadata > definitions. > The Atlas wiki has the models as a set of linked pages which are probably the > easiest way to view the models. > Start here: > https://cwiki.apache.org/confluence/display/ATLAS/Building+out+the+Apache+Atlas+Typesystem -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1843) Area 6 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1843. --- Resolution: Fixed Area 6 models are delivered through Egeria: https://odpi.github.io/egeria/open-metadata-publication/website/open-metadata-types/Area-6-models.html > Area 6 of the open metadata model > - > > Key: ATLAS-1843 > URL: https://issues.apache.org/jira/browse/ATLAS-1843 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata > > This task delivers the JSON files for the new models that describe types for > Area 6 in the open metadata model. This area covers extensions to add > discovered metadata. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2246) Define OMRS Connector interface
[ https://issues.apache.org/jira/browse/ATLAS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2246. - > Define OMRS Connector interface > --- > > Key: ATLAS-2246 > URL: https://issues.apache.org/jira/browse/ATLAS-2246 > Project: Atlas > Issue Type: Sub-task > Components: atlas-intg >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Critical > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-2246-OMRS-Connector-API-plus-REST-and-IGC-Conn.patch, OMRS > Javadoc.zip > > > This task covers the creation of the OMRS Connector APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1846) Design and business lineage for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1846. --- Resolution: Fixed Design and business lineage is supported through Egeria > Design and business lineage for Atlas > - > > Key: ATLAS-1846 > URL: https://issues.apache.org/jira/browse/ATLAS-1846 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > > In governance there are many consumers of lineage. This Jira looks to > provide: > * Open APIs for registering and querying lineage from metadata repositories > and data movement engines that maintain their own lineage. > * Collection and correlation information about the design and expectation of > data flows that is linked to the operational logs to provide business context > to lineage. > * Lifecycle management of lineage data so lineage of key resources is > preserved while lineage of everything else is removed after a short period of > time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1847) Open Metadata and Governance
[ https://issues.apache.org/jira/browse/ATLAS-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1847. - > Open Metadata and Governance > > > Key: ATLAS-1847 > URL: https://issues.apache.org/jira/browse/ATLAS-1847 > Project: Atlas > Issue Type: New Feature >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata, open-metadata > > This JIRA covers the architecture and tracking of the open metadata and > governance initiative for Apache Atlas. > Open metadata and governance is a moon-shot type of project to create a open > set of APIs, types and interchange protocols to allow all metadata > repositories to share and exchange metadata. From this common base, it adds > governance, discovery and access frameworks to automate the collection, > management and use of metadata across an enterprise. The result is an > enterprise catalog of data resources that are transparently assessed, > governed and used in order to deliver maximum value to the enterprise. > Delivering this capability as open source is a critical part of the project > since multiple vendors must buy into this ecosystem. They are not going to > do this if one organization dominates the technology base. Thus the open > metadata and governance technology must be freely available with an open > source governance model that allows a community of organizations and > practitioners to develop and evolve the base and then use it in their > offerings and deployments. > The proposal is to use Apache Atlas as the open source reference > implementation for open metadata and governance. Apache Alas will support an > open metadata and governance compliant repository plus provide the adapters > and interchange formats to allow other metadata repositories to connect into > the ecosystem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1846) Design and business lineage for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1846. - > Design and business lineage for Atlas > - > > Key: ATLAS-1846 > URL: https://issues.apache.org/jira/browse/ATLAS-1846 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > > In governance there are many consumers of lineage. This Jira looks to > provide: > * Open APIs for registering and querying lineage from metadata repositories > and data movement engines that maintain their own lineage. > * Collection and correlation information about the design and expectation of > data flows that is linked to the operational logs to provide business context > to lineage. > * Lifecycle management of lineage data so lineage of key resources is > preserved while lineage of everything else is removed after a short period of > time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1845) Governance Definitions OMAS
[ https://issues.apache.org/jira/browse/ATLAS-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1845. --- Resolution: Fixed The Governance OMASs are being delivered through Egeria - see https://jira.odpi.org/browse/EGERIA-23 > Governance Definitions OMAS > --- > > Key: ATLAS-1845 > URL: https://issues.apache.org/jira/browse/ATLAS-1845 > Project: Atlas > Issue Type: New Feature >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > > This JIRA is for tracking the design and implementation of the OMAS > interfaces for defining a governance program. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1845) Governance Definitions OMAS
[ https://issues.apache.org/jira/browse/ATLAS-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1845. - > Governance Definitions OMAS > --- > > Key: ATLAS-1845 > URL: https://issues.apache.org/jira/browse/ATLAS-1845 > Project: Atlas > Issue Type: New Feature >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > > This JIRA is for tracking the design and implementation of the OMAS > interfaces for defining a governance program. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1844) Area 7 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1844. --- Resolution: Fixed Area 7 model is delivered through Egeria https://odpi.github.io/egeria/open-metadata-publication/website/open-metadata-types/Area-7-models.html > Area 7 of the open metadata model > - > > Key: ATLAS-1844 > URL: https://issues.apache.org/jira/browse/ATLAS-1844 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata > > This task delivers the JSON files for the new models that describe types for > Area 7 in the open metadata model. This area covers lineage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1844) Area 7 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1844. - > Area 7 of the open metadata model > - > > Key: ATLAS-1844 > URL: https://issues.apache.org/jira/browse/ATLAS-1844 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata > > This task delivers the JSON files for the new models that describe types for > Area 7 in the open metadata model. This area covers lineage. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (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 ] Mandy Chessell resolved ATLAS-1773. --- Resolution: Fixed The OMRS is delivered through Egeria: https://odpi.github.io/egeria/open-metadata-implementation/repository-services/ > 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] [Closed] (ATLAS-1775) Create Enterprise OMRS Connector
[ https://issues.apache.org/jira/browse/ATLAS-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1775. - > Create Enterprise OMRS Connector > > > Key: ATLAS-1775 > URL: https://issues.apache.org/jira/browse/ATLAS-1775 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-ATLAS-1775-Enterprise-OMRS-Connector-Initial-Impl-2.patch > > > The Enterprise OMRS Connector provides a connector that implements the OMRS > Connector API defined in JIRA ATLAS-1773 that is able to aggregate the > metadata from multiple metadata repositories in response to metadata requests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1829) OMRS Message Payloads with Event Listener and Publisher
[ https://issues.apache.org/jira/browse/ATLAS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1829. - > OMRS Message Payloads with Event Listener and Publisher > --- > > Key: ATLAS-1829 > URL: https://issues.apache.org/jira/browse/ATLAS-1829 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: VirtualDataConnector > > This JIRA covers the event support for OMRS. There is an OMRS Event > Publisher that publishes events relating to changing metadata in the Atlas > repository. These events follow the OMRS message payloads that are derived > from the Atlas type model. > OMRS Messages are published to the OMRS Topic in Kafka. > There is also an OMRS Event Listener that takes events from the OMRS Topic > and pushes them to an OMRS Connector if they are from a different repository > instance. > This JIRA complements ATLAS-1773 > (https://issues.apache.org/jira/browse/ATLAS-1773) OMRS REST Connector -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1829) OMRS Message Payloads with Event Listener and Publisher
[ https://issues.apache.org/jira/browse/ATLAS-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1829. --- Resolution: Fixed The OMRS Event hadling is supported in Egeria https://odpi.github.io/egeria/open-metadata-implementation/repository-services/ > OMRS Message Payloads with Event Listener and Publisher > --- > > Key: ATLAS-1829 > URL: https://issues.apache.org/jira/browse/ATLAS-1829 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: VirtualDataConnector > > This JIRA covers the event support for OMRS. There is an OMRS Event > Publisher that publishes events relating to changing metadata in the Atlas > repository. These events follow the OMRS message payloads that are derived > from the Atlas type model. > OMRS Messages are published to the OMRS Topic in Kafka. > There is also an OMRS Event Listener that takes events from the OMRS Topic > and pushes them to an OMRS Connector if they are from a different repository > instance. > This JIRA complements ATLAS-1773 > (https://issues.apache.org/jira/browse/ATLAS-1773) OMRS REST Connector -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1689) Virtual Data Connector Project
[ https://issues.apache.org/jira/browse/ATLAS-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1689. - > Virtual Data Connector Project > --- > > Key: ATLAS-1689 > URL: https://issues.apache.org/jira/browse/ATLAS-1689 > Project: Atlas > Issue Type: Improvement >Reporter: David Radley >Assignee: Mandy Chessell >Priority: Major > Labels: VirtualDataConnector > > Virtual Data Connector - this is a project to create a meta-data driven data > lake in which Apache Atlas is the meta-data store. > Create an open, metadata-driven virtual connector to data repositories – a > Data Virtualization Platform that will satisfy the following goals: > Give users one place to access each and every Data Lake repository > (search and discover) > Give users one search interface for both data and metadata inside the > Data Lake (search and discover) > To provide one place to look for and provision data for all kinds of end > users > To provide one place to build and maintain data security for all data > repositories inside the Data Lake -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1689) Virtual Data Connector Project
[ https://issues.apache.org/jira/browse/ATLAS-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1689. --- Resolution: Fixed The virtual data connector is delivered through Egeria https://odpi.github.io/egeria/open-metadata-resources/open-metadata-samples/ > Virtual Data Connector Project > --- > > Key: ATLAS-1689 > URL: https://issues.apache.org/jira/browse/ATLAS-1689 > Project: Atlas > Issue Type: Improvement >Reporter: David Radley >Assignee: Mandy Chessell >Priority: Major > Labels: VirtualDataConnector > > Virtual Data Connector - this is a project to create a meta-data driven data > lake in which Apache Atlas is the meta-data store. > Create an open, metadata-driven virtual connector to data repositories – a > Data Virtualization Platform that will satisfy the following goals: > Give users one place to access each and every Data Lake repository > (search and discover) > Give users one search interface for both data and metadata inside the > Data Lake (search and discover) > To provide one place to look for and provision data for all kinds of end > users > To provide one place to build and maintain data security for all data > repositories inside the Data Lake -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1828) Asset Catalog OMAS
[ https://issues.apache.org/jira/browse/ATLAS-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1828. --- Resolution: Fixed Asset catalog is delivered thrugh Egeria: https://odpi.github.io/egeria/open-metadata-implementation/access-services/ > Asset Catalog OMAS > -- > > Key: ATLAS-1828 > URL: https://issues.apache.org/jira/browse/ATLAS-1828 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1828-Asset-Catalog-OMAS.patch > > > This JIRA delivers the External API for catalog search applications. This > API is used by ATLAS-1765 (https://issues.apache.org/jira/browse/ATLAS-1765) > that provides the Self-Service Catalog Search and Data Preview UI. > This JIRA is dependent on ATLAS-1773 > (https://issues.apache.org/jira/browse/ATLAS-1773) that implements the OMRS > REST Connector -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1828) Asset Catalog OMAS
[ https://issues.apache.org/jira/browse/ATLAS-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1828. - > Asset Catalog OMAS > -- > > Key: ATLAS-1828 > URL: https://issues.apache.org/jira/browse/ATLAS-1828 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1828-Asset-Catalog-OMAS.patch > > > This JIRA delivers the External API for catalog search applications. This > API is used by ATLAS-1765 (https://issues.apache.org/jira/browse/ATLAS-1765) > that provides the Self-Service Catalog Search and Data Preview UI. > This JIRA is dependent on ATLAS-1773 > (https://issues.apache.org/jira/browse/ATLAS-1773) that implements the OMRS > REST Connector -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2621) Validate properties against full supertype hierarchy (and change update instance events)
[ https://issues.apache.org/jira/browse/ATLAS-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2621. - > Validate properties against full supertype hierarchy (and change update > instance events) > > > Key: ATLAS-2621 > URL: https://issues.apache.org/jira/browse/ATLAS-2621 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > Attachments: 0004-ATLAS-2621-fix-poperty-validation.patch > > > Daniella discovered that adding an entity which inherits its properties from > super types fails validation. This is because the repository validator does > not walk the supertype hierarchy. > I also changes the update instance events to provide both the before and > after version of the event so that the listener can understand what has > changed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2617) Enable multiple annotation schemes for open metadata REST APIs
[ https://issues.apache.org/jira/browse/ATLAS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2617. - > Enable multiple annotation schemes for open metadata REST APIs > -- > > Key: ATLAS-2617 > URL: https://issues.apache.org/jira/browse/ATLAS-2617 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > Attachments: 0003-ATLAS-2617-Open-Metadata-annotation-files.patch > > > The Atlas server is using the Spring framework and Jersey. The OMAG server > is using spring boot. The annotations needed for each of these technologies > is slightly different so we need to create a thin annotation class for each > environment and delegate to the REST API logic from each annotation class. > This affects the OMAG API, OMRS API and the OMAS APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2577) Add Governance Program OMAS module
[ https://issues.apache.org/jira/browse/ATLAS-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2577. - > Add Governance Program OMAS module > -- > > Key: ATLAS-2577 > URL: https://issues.apache.org/jira/browse/ATLAS-2577 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > This Jira adds the Governance Program OMAS. This interface provides the > ability to create a data strategy, define the requirements from regulations > and the governance program that supports them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2577) Add Governance Program OMAS module
[ https://issues.apache.org/jira/browse/ATLAS-2577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-2577. --- Resolution: Fixed The Governance Program OMS is delivered through Egeria: https://odpi.github.io/egeria/open-metadata-implementation/access-services/ > Add Governance Program OMAS module > -- > > Key: ATLAS-2577 > URL: https://issues.apache.org/jira/browse/ATLAS-2577 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > This Jira adds the Governance Program OMAS. This interface provides the > ability to create a data strategy, define the requirements from regulations > and the governance program that supports them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2617) Enable multiple annotation schemes for open metadata REST APIs
[ https://issues.apache.org/jira/browse/ATLAS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-2617. --- Resolution: Fixed > Enable multiple annotation schemes for open metadata REST APIs > -- > > Key: ATLAS-2617 > URL: https://issues.apache.org/jira/browse/ATLAS-2617 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > Attachments: 0003-ATLAS-2617-Open-Metadata-annotation-files.patch > > > The Atlas server is using the Spring framework and Jersey. The OMAG server > is using spring boot. The annotations needed for each of these technologies > is slightly different so we need to create a thin annotation class for each > environment and delegate to the REST API logic from each annotation class. > This affects the OMAG API, OMRS API and the OMAS APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2573) Add Connected Asset OMAS module
[ https://issues.apache.org/jira/browse/ATLAS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-2573. --- Resolution: Fixed The connected asset OMAS is delivered through Egeria: https://odpi.github.io/egeria/open-metadata-implementation/access-services/ > Add Connected Asset OMAS module > --- > > Key: ATLAS-2573 > URL: https://issues.apache.org/jira/browse/ATLAS-2573 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > The Connected Asset OMAS retrieves an asset's properties from the open > metadata repositories. It supports the OCF API for retrieving the connected > asset properties and supports the getAssetProperties of the Asset Consumer > OMAS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2573) Add Connected Asset OMAS module
[ https://issues.apache.org/jira/browse/ATLAS-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2573. - > Add Connected Asset OMAS module > --- > > Key: ATLAS-2573 > URL: https://issues.apache.org/jira/browse/ATLAS-2573 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > The Connected Asset OMAS retrieves an asset's properties from the open > metadata repositories. It supports the OCF API for retrieving the connected > asset properties and supports the getAssetProperties of the Asset Consumer > OMAS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2574) Add Asset Owner OMAS module
[ https://issues.apache.org/jira/browse/ATLAS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-2574. --- Resolution: Fixed The Asset Owner OMAS is delivered through Egeria https://odpi.github.io/egeria/open-metadata-implementation/access-services/ > Add Asset Owner OMAS module > --- > > Key: ATLAS-2574 > URL: https://issues.apache.org/jira/browse/ATLAS-2574 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > This Jira adds support for the Asset Owner OMAS. This module supports calls > for updating and classifying asset definitions, creating connections, > managing classifications, semantic assignments, licenses and certifications. > The asset owner also receives feedback on their asset -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2574) Add Asset Owner OMAS module
[ https://issues.apache.org/jira/browse/ATLAS-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2574. - > Add Asset Owner OMAS module > --- > > Key: ATLAS-2574 > URL: https://issues.apache.org/jira/browse/ATLAS-2574 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > This Jira adds support for the Asset Owner OMAS. This module supports calls > for updating and classifying asset definitions, creating connections, > managing classifications, semantic assignments, licenses and certifications. > The asset owner also receives feedback on their asset -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2575) Add Data Platform OMAS module
[ https://issues.apache.org/jira/browse/ATLAS-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-2575. --- Resolution: Fixed The Data Platform OMAS is delivered thorugh Egeria > Add Data Platform OMAS module > - > > Key: ATLAS-2575 > URL: https://issues.apache.org/jira/browse/ATLAS-2575 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > This Jira adds the Data Platform OMAS. This module supports the loading of > data asset metadata including Asset, Schemas and Lineage -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2575) Add Data Platform OMAS module
[ https://issues.apache.org/jira/browse/ATLAS-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2575. - > Add Data Platform OMAS module > - > > Key: ATLAS-2575 > URL: https://issues.apache.org/jira/browse/ATLAS-2575 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > This Jira adds the Data Platform OMAS. This module supports the loading of > data asset metadata including Asset, Schemas and Lineage -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2576) Add Community Profile OMAS module
[ https://issues.apache.org/jira/browse/ATLAS-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-2576. --- Resolution: Fixed The Community Profile OMAS is delivered through Egeria: https://odpi.github.io/egeria/open-metadata-implementation/access-services/ > Add Community Profile OMAS module > - > > Key: ATLAS-2576 > URL: https://issues.apache.org/jira/browse/ATLAS-2576 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > This Jira added the Community Profile OMAS. This module supports the > creating and maintenance of user profiles and their preferences. It also > supports the creation of communities, managing their memberships and > resources. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2576) Add Community Profile OMAS module
[ https://issues.apache.org/jira/browse/ATLAS-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2576. - > Add Community Profile OMAS module > - > > Key: ATLAS-2576 > URL: https://issues.apache.org/jira/browse/ATLAS-2576 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > This Jira added the Community Profile OMAS. This module supports the > creating and maintenance of user profiles and their preferences. It also > supports the creation of communities, managing their memberships and > resources. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1772) Create a data set connector
[ https://issues.apache.org/jira/browse/ATLAS-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1772. --- Resolution: Fixed The data set connector is delivered through Egeria: https://odpi.github.io/egeria/open-metadata-implementation/adapters/open-connectors/data-store-connectors/ > Create a data set connector > --- > > Key: ATLAS-1772 > URL: https://issues.apache.org/jira/browse/ATLAS-1772 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > > The Data Set Connector provides an OCF provider and connector implementation > for collections of files. These files may be structured or unstructured > data. The data set may be a set of files physically co-located (such as in > the same folder on disk) or files that have similar characteristics in a > larger collection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1772) Create a data set connector
[ https://issues.apache.org/jira/browse/ATLAS-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1772. - > Create a data set connector > --- > > Key: ATLAS-1772 > URL: https://issues.apache.org/jira/browse/ATLAS-1772 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > > The Data Set Connector provides an OCF provider and connector implementation > for collections of files. These files may be structured or unstructured > data. The data set may be a set of files physically co-located (such as in > the same folder on disk) or files that have similar characteristics in a > larger collection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1774) Create the OMRS Connector for IBM's Information Governance Catalog (IGC)
[ https://issues.apache.org/jira/browse/ATLAS-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1774. --- Resolution: Fixed The IGC Connector is delivered as part of Egeria: https://odpi.github.io/egeria/open-metadata-resources/open-metadata-demos/virtual-data-connector/ > Create the OMRS Connector for IBM's Information Governance Catalog (IGC) > > > Key: ATLAS-1774 > URL: https://issues.apache.org/jira/browse/ATLAS-1774 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > > This JIRA provides a connector for IBM’s Information Governance Catalog that > implements the OMRS Connector API defined in JIRA ATLAS-1773. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1774) Create the OMRS Connector for IBM's Information Governance Catalog (IGC)
[ https://issues.apache.org/jira/browse/ATLAS-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1774. - > Create the OMRS Connector for IBM's Information Governance Catalog (IGC) > > > Key: ATLAS-1774 > URL: https://issues.apache.org/jira/browse/ATLAS-1774 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > > This JIRA provides a connector for IBM’s Information Governance Catalog that > implements the OMRS Connector API defined in JIRA ATLAS-1773. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-2572) Add client for OMAG APIs
[ https://issues.apache.org/jira/browse/ATLAS-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-2572. --- Resolution: Fixed This feature is being tracked under https://jira.odpi.org/browse/EGERIA-50 > Add client for OMAG APIs > > > Key: ATLAS-2572 > URL: https://issues.apache.org/jira/browse/ATLAS-2572 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Fix For: 1.0.0 > > > This Jira adds the Java client class and the changes necessary to the > omag-api component to support it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2585) Fix invalid validation of typeGUID on some OMRS Connector calls
[ https://issues.apache.org/jira/browse/ATLAS-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2585. - > Fix invalid validation of typeGUID on some OMRS Connector calls > --- > > Key: ATLAS-2585 > URL: https://issues.apache.org/jira/browse/ATLAS-2585 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 1.0.0-alpha >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: VirtualDataConnector > Fix For: 1.0.0 > > Attachments: 0002-ATLAS-2585-Fix-up-validation-of-TypDef-GUIDs.patch > > > Some of the OMRS Connector methods are throwing an exception if the TypeGUID > supplied is null. Null should mean "any type" and should work ok. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2298) OCF Database Connector
[ https://issues.apache.org/jira/browse/ATLAS-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2298. - > OCF Database Connector > -- > > Key: ATLAS-2298 > URL: https://issues.apache.org/jira/browse/ATLAS-2298 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Maryna Strelchuk >Assignee: Yao Li >Priority: Major > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-2298-12-04-2018.patch, OCF Database Connector > - JIRA.pdf, java doc.zip > > > Code review is available in https://reviews.apache.org/r/65435/ > This Jira is focused on development of the OCF Database Connector. > The OCF Database Connector is the subclass of OCF Connector and it is > designed especially for connection to database to retrieve data. It provides > the OCFDatabaseConnector as a basic class for other implementations for > various databases. > Here we implement a connector for Gaian (GaianOCFConnector) as an example for > using OCF Database Connector. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1839) Area 3 of the open metadata model - including the Glossary
[ https://issues.apache.org/jira/browse/ATLAS-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1839. - > Area 3 of the open metadata model - including the Glossary > -- > > Key: ATLAS-1839 > URL: https://issues.apache.org/jira/browse/ATLAS-1839 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: David Radley >Priority: Major > Labels: OpenMetadata, VirtualDataConnector > Attachments: ATLAS1839-1.patch, ATLAS1839-2.patch, ATLAS1839-3.patch, > ATLAS1839.patch > > > This task delivers the JSON files for the new models that describe types for > Area 3 in the open metadata model. This area covers the glossary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-2029) Enhance classificationDef create to include a list of entities it supports
[ https://issues.apache.org/jira/browse/ATLAS-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-2029. - > Enhance classificationDef create to include a list of entities it supports > -- > > Key: ATLAS-2029 > URL: https://issues.apache.org/jira/browse/ATLAS-2029 > Project: Atlas > Issue Type: Sub-task > Components: atlas-core >Reporter: David Radley >Assignee: David Radley >Priority: Major > Labels: VirtualDataConnector > Fix For: 1.0.0 > > Attachments: ATLAS-2029-1.patch, ATLAS-2029-2.patch, > ATLAS-2029-3.patch, ATLAS-2029.patch, ATLAS2029-4.patch, ATLAS2029-5.patch > > > Committed to master: > http://git-wip-us.apache.org/repos/asf/atlas/commit/586b5eb2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1840) Area 3 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1840. - > Area 3 of the open metadata model > - > > Key: ATLAS-1840 > URL: https://issues.apache.org/jira/browse/ATLAS-1840 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata, VirtualDataConnector > Fix For: 1.0.0 > > > This task delivers the JSON files for the new models that describe types for > Area 2 in the open metadata model. This area covers collaboration, projects > and communities -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1841) Area 4 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1841. - > Area 4 of the open metadata model > - > > Key: ATLAS-1841 > URL: https://issues.apache.org/jira/browse/ATLAS-1841 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata, VirtualDataConnector > Fix For: 1.0.0 > > > This task delivers the JSON files for the new models that describe types for > Area 4 in the open metadata model. This area covers governance. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1842) Area 5 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1842. - > Area 5 of the open metadata model > - > > Key: ATLAS-1842 > URL: https://issues.apache.org/jira/browse/ATLAS-1842 > Project: Atlas > Issue Type: Task > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata, VirtualDataConnector > > This task delivers the JSON files for the new models that describe types for > Area 5 in the open metadata model. This area covers standards, reference data > and models. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1837) OCF definitions for Area 1 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1837. - > OCF definitions for Area 1 of the open metadata model > - > > Key: ATLAS-1837 > URL: https://issues.apache.org/jira/browse/ATLAS-1837 > Project: Atlas > Issue Type: Task >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata, VirtualDataConnector > > This task delivers the JSON files for the new models that describe types for > the open connector framework in Area 1 in the open metadata model. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1838) Area 1 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1838. - > Area 1 of the open metadata model > - > > Key: ATLAS-1838 > URL: https://issues.apache.org/jira/browse/ATLAS-1838 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell >Priority: Major > Labels: OpenMetadata, VirtualDataConnector > > This task delivers the JSON files for the new models that describe types for > Area 1 in the open metadata model. This area covers Asset and Connector types. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1836) Area 0 of the open metadata model
[ https://issues.apache.org/jira/browse/ATLAS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1836. - > Area 0 of the open metadata model > - > > Key: ATLAS-1836 > URL: https://issues.apache.org/jira/browse/ATLAS-1836 > Project: Atlas > Issue Type: Task > Components: atlas-core >Reporter: Mandy Chessell >Assignee: David Radley >Priority: Major > Labels: OpenMetadata, VirtualDataConnector > Attachments: ATLAS-1836-1.patch, ATLAS-1836.patch, ATLAS1836-2.patch, > ATLAS1836-3.patch, ATLAS1836-4.patch, ATLAS1836-5.patch > > > This task delivers the JSON files for the new models that describe types for > Area 0 in the open metadata model. This area covers base types. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1830) IGC Event Mapper
[ https://issues.apache.org/jira/browse/ATLAS-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1830. - > IGC Event Mapper > > > Key: ATLAS-1830 > URL: https://issues.apache.org/jira/browse/ATLAS-1830 > Project: Atlas > Issue Type: Sub-task > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Jerry He >Priority: Major > Labels: VirtualDataConnector > > This component listens for events from IBM's Information Governance Catalog > and converts them into OMRS Event Messages and posts them onto the OMRS Topic > in Kafka. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1830) IGC Event Mapper
[ https://issues.apache.org/jira/browse/ATLAS-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1830. --- Resolution: Fixed Delivered through Egeria > IGC Event Mapper > > > Key: ATLAS-1830 > URL: https://issues.apache.org/jira/browse/ATLAS-1830 > Project: Atlas > Issue Type: Sub-task > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Jerry He >Priority: Major > Labels: VirtualDataConnector > > This component listens for events from IBM's Information Governance Catalog > and converts them into OMRS Event Messages and posts them onto the OMRS Topic > in Kafka. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1712) Asset OMAS
[ https://issues.apache.org/jira/browse/ATLAS-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1712. --- Resolution: Fixed Delivered in Egeria > Asset OMAS > -- > > Key: ATLAS-1712 > URL: https://issues.apache.org/jira/browse/ATLAS-1712 > Project: Atlas > Issue Type: New Feature >Reporter: Maryna Strelchuk >Priority: Major > Labels: VirtualDataConnector > > Asset OMAS is part of the API for a connector that returns the asset > metadata. Asset OMAS used by the virtualizer component when constructing the > view metadata. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1711) Information View OMAS
[ https://issues.apache.org/jira/browse/ATLAS-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1711. --- Resolution: Fixed Deleivered in Egeria > Information View OMAS > - > > Key: ATLAS-1711 > URL: https://issues.apache.org/jira/browse/ATLAS-1711 > Project: Atlas > Issue Type: New Feature >Reporter: Maryna Strelchuk >Assignee: Maryna Strelchuk >Priority: Major > Labels: VirtualDataConnector > > Information View OMAS manages the creation and maintenance of View metadata. > and is called by the Virtualizer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1701) Swagger
[ https://issues.apache.org/jira/browse/ATLAS-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1701. --- Resolution: Fixed Delivered in Egeria > Swagger > --- > > Key: ATLAS-1701 > URL: https://issues.apache.org/jira/browse/ATLAS-1701 > Project: Atlas > Issue Type: Sub-task >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1712) Asset OMAS
[ https://issues.apache.org/jira/browse/ATLAS-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1712. - > Asset OMAS > -- > > Key: ATLAS-1712 > URL: https://issues.apache.org/jira/browse/ATLAS-1712 > Project: Atlas > Issue Type: New Feature >Reporter: Maryna Strelchuk >Priority: Major > Labels: VirtualDataConnector > > Asset OMAS is part of the API for a connector that returns the asset > metadata. Asset OMAS used by the virtualizer component when constructing the > view metadata. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1702) documentation
[ https://issues.apache.org/jira/browse/ATLAS-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1702. - > documentation > - > > Key: ATLAS-1702 > URL: https://issues.apache.org/jira/browse/ATLAS-1702 > Project: Atlas > Issue Type: Sub-task >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1711) Information View OMAS
[ https://issues.apache.org/jira/browse/ATLAS-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1711. - > Information View OMAS > - > > Key: ATLAS-1711 > URL: https://issues.apache.org/jira/browse/ATLAS-1711 > Project: Atlas > Issue Type: New Feature >Reporter: Maryna Strelchuk >Assignee: Maryna Strelchuk >Priority: Major > Labels: VirtualDataConnector > > Information View OMAS manages the creation and maintenance of View metadata. > and is called by the Virtualizer. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1702) documentation
[ https://issues.apache.org/jira/browse/ATLAS-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1702. --- Resolution: Fixed Delivered in Egeria > documentation > - > > Key: ATLAS-1702 > URL: https://issues.apache.org/jira/browse/ATLAS-1702 > Project: Atlas > Issue Type: Sub-task >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1410) V2 Glossary Function
[
https://issues.apache.org/jira/browse/ATLAS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandy Chessell resolved ATLAS-1410.
---
Resolution: Fixed
Delivered in Egeria
> V2 Glossary Function
>
>
> Key: ATLAS-1410
> URL: https://issues.apache.org/jira/browse/ATLAS-1410
> Project: Atlas
> Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
> Labels: VirtualDataConnector
> Attachments: Atlas Glossary V2 proposal v1.0.pdf, Atlas Glossary V2
> proposal v1.1.pdf, Atlas Glossary V2 proposal v1.2.pdf, Atlas Glossary V2
> proposal v1.3.pdf, Atlas Glossary V2 proposal v1.4.pdf
>
>
> The BaseResourceDefinition uses the AttributeDefintion class from typesystem.
> There are newer more funcitonal versions of this capability in the atlas-intg
> project. This Jira is changing over the glossary implementation to the newer
> entity / type classes.
> Instread of the instanceProperties and collectionProperties in the
> BaseResourceDefintions we should use something in this sort of style :
> "
> AtlasEntityDef deptTypeDef =
> AtlasTypeUtil.createClassTypeDef(DEPARTMENT_TYPE,
> "Department"+_description, ImmutableSet.of(),
> AtlasTypeUtil.createRequiredAttrDef("name", "string"),
> new AtlasAttributeDef("employees",
> String.format("array<%s>", "Person"), true,
> AtlasAttributeDef.Cardinality.SINGLE, 0, 1,
> false, false,
>
> Collections.emptyList()));
> AtlasEntityDef personTypeDef =
> AtlasTypeUtil.createClassTypeDef("Person", "Person"+_description,
> ImmutableSet.of(),
> AtlasTypeUtil.createRequiredAttrDef("name", "string"),
> AtlasTypeUtil.createOptionalAttrDef("address", "Address"),
> AtlasTypeUtil.createOptionalAttrDef("birthday", "date"),
> AtlasTypeUtil.createOptionalAttrDef("hasPets", "boolean"),
> AtlasTypeUtil.createOptionalAttrDef("numberOfCars", "byte"),
> AtlasTypeUtil.createOptionalAttrDef("houseNumber", "short"),
> AtlasTypeUtil.createOptionalAttrDef("carMileage", "int"),
> AtlasTypeUtil.createOptionalAttrDef("age", "float"),
> "
> For the parent child relationships with glossary categories and terms we
> should be able to have the type system manage edge deletion. As part of this,
> we will need to investigate whether we could get rid of the disconnect and
> connect methods added in ATLAS-1186
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ATLAS-1410) V2 Glossary Function
[
https://issues.apache.org/jira/browse/ATLAS-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandy Chessell closed ATLAS-1410.
-
> V2 Glossary Function
>
>
> Key: ATLAS-1410
> URL: https://issues.apache.org/jira/browse/ATLAS-1410
> Project: Atlas
> Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>Priority: Major
> Labels: VirtualDataConnector
> Attachments: Atlas Glossary V2 proposal v1.0.pdf, Atlas Glossary V2
> proposal v1.1.pdf, Atlas Glossary V2 proposal v1.2.pdf, Atlas Glossary V2
> proposal v1.3.pdf, Atlas Glossary V2 proposal v1.4.pdf
>
>
> The BaseResourceDefinition uses the AttributeDefintion class from typesystem.
> There are newer more funcitonal versions of this capability in the atlas-intg
> project. This Jira is changing over the glossary implementation to the newer
> entity / type classes.
> Instread of the instanceProperties and collectionProperties in the
> BaseResourceDefintions we should use something in this sort of style :
> "
> AtlasEntityDef deptTypeDef =
> AtlasTypeUtil.createClassTypeDef(DEPARTMENT_TYPE,
> "Department"+_description, ImmutableSet.of(),
> AtlasTypeUtil.createRequiredAttrDef("name", "string"),
> new AtlasAttributeDef("employees",
> String.format("array<%s>", "Person"), true,
> AtlasAttributeDef.Cardinality.SINGLE, 0, 1,
> false, false,
>
> Collections.emptyList()));
> AtlasEntityDef personTypeDef =
> AtlasTypeUtil.createClassTypeDef("Person", "Person"+_description,
> ImmutableSet.of(),
> AtlasTypeUtil.createRequiredAttrDef("name", "string"),
> AtlasTypeUtil.createOptionalAttrDef("address", "Address"),
> AtlasTypeUtil.createOptionalAttrDef("birthday", "date"),
> AtlasTypeUtil.createOptionalAttrDef("hasPets", "boolean"),
> AtlasTypeUtil.createOptionalAttrDef("numberOfCars", "byte"),
> AtlasTypeUtil.createOptionalAttrDef("houseNumber", "short"),
> AtlasTypeUtil.createOptionalAttrDef("carMileage", "int"),
> AtlasTypeUtil.createOptionalAttrDef("age", "float"),
> "
> For the parent child relationships with glossary categories and terms we
> should be able to have the type system manage edge deletion. As part of this,
> we will need to investigate whether we could get rid of the disconnect and
> connect methods added in ATLAS-1186
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (ATLAS-520) Temporal / Versioning support for Atlas metadata
[ https://issues.apache.org/jira/browse/ATLAS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-520. -- Resolution: Fixed Delivered in Egeria > Temporal / Versioning support for Atlas metadata > > > Key: ATLAS-520 > URL: https://issues.apache.org/jira/browse/ATLAS-520 > Project: Atlas > Issue Type: Wish >Affects Versions: trunk >Reporter: Nigel Jones >Priority: Major > Labels: VirtualDataConnector > > With Atlas storing metadata & lineage data , from a governance perspective we > would like to ask questons such as > - what different data sources were used to produce this report last year > compared to this year? > - how was this salary column in the employee table classified on 6 Apr 2015? > These queries are needed to support audit, and to aid in process improvement > + root cause analysis > To do so we need temporal support in atlas. A query should be able to > indicate the point in time that it applies to. This means keeping track of > times, versions within atlas. Potentially this means not just the nodes in > the graph, but the edges too, however this can mean an ever increasing graph > which can get out of control. > opening up this JIRA to enable an evaluation/ discussion of what we might be > able to do -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1692) Introduce the ability to relate a type to any type
[ https://issues.apache.org/jira/browse/ATLAS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1692. --- Resolution: Fixed > Introduce the ability to relate a type to any type > > > Key: ATLAS-1692 > URL: https://issues.apache.org/jira/browse/ATLAS-1692 > Project: Atlas > Issue Type: Improvement >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > > Introduce a hierarchy of types. So every type inherits from a base type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1692) Introduce the ability to relate a type to any type
[ https://issues.apache.org/jira/browse/ATLAS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1692. - > Introduce the ability to relate a type to any type > > > Key: ATLAS-1692 > URL: https://issues.apache.org/jira/browse/ATLAS-1692 > Project: Atlas > Issue Type: Improvement >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > > Introduce a hierarchy of types. So every type inherits from a base type. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1690) Introduce top level relationships
[ https://issues.apache.org/jira/browse/ATLAS-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1690. --- Resolution: Fixed > Introduce top level relationships > - > > Key: ATLAS-1690 > URL: https://issues.apache.org/jira/browse/ATLAS-1690 > Project: Atlas > Issue Type: Improvement >Reporter: David Radley >Assignee: David Radley >Priority: Major > Labels: VirtualDataConnector > Attachments: Atlas Relationships proposal v1.0.pdf, Atlas > Relationships proposal v1.1.pdf, Atlas Relationships proposal v1.10.pdf, > Atlas Relationships proposal v1.2.pdf, Atlas Relationships proposal v1.3.pdf, > Atlas Relationships proposal v1.4.pdf, Atlas Relationships proposal v1.5.pdf, > Atlas Relationships proposal v1.6.pdf, Atlas Relationships proposal v1.7.pdf, > Atlas Relationships proposal v1.8.pdf, Atlas Relationships proposal v1.9.pdf, > Atlas_RelationDef_Json_Structure_v1.pdf > > > Introduce top level relationships including support for > -many to many relationships > - relationship names including the name for both ends and the relationship. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1831) Virtualiser to dynamically configure an information virtualization layer
[ https://issues.apache.org/jira/browse/ATLAS-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1831. - > Virtualiser to dynamically configure an information virtualization layer > > > Key: ATLAS-1831 > URL: https://issues.apache.org/jira/browse/ATLAS-1831 > Project: Atlas > Issue Type: New Feature > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Yao Li >Priority: Major > Labels: VirtualDataConnector > Attachments: 0008-ATLAS-1831-29-03-2018.patch, Virtualiser Summary - > JIRA.pdf, java doc.zip > > > Code review is available in [https://reviews.apache.org/r/66174/] > This component listens for events from the Information View OMAS event > publisher built by ATLAS-1711 > (https://issues.apache.org/jira/browse/ATLAS-1711) to detect changes to > relational data assets and configures an information virtualization tool > (Gaian in the first instance) to create/maintain a view that maps to the > physical data asset. It also populates Information View metadata (using the > Information View OMAS API) for each of the views it creates. > RANGER-1485 (https://issues.apache.org/jira/browse/RANGER-1485) will also > configure Gaian with enforcement logic to apply data protection rules to the > data when queries are made to the views. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1700) Add constraints to JAVA API
[ https://issues.apache.org/jira/browse/ATLAS-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1700. - > Add constraints to JAVA API > --- > > Key: ATLAS-1700 > URL: https://issues.apache.org/jira/browse/ATLAS-1700 > Project: Atlas > Issue Type: Sub-task >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > > Add constraints to JAVA API for the Glossary. There are some constraints that > can be captured using the constraints in the type model. For the Glossary > API, there are restrictions that cannot be captured in the type model. I am > thinking of constraints like: > - policing that we do not allow a category to be updated to have a parent as > one of its descendants. > - policing that we do not allow a category from another glossary to be added > under our category > - policing that we do not allow a category to be updated, such that the > category tree contains categories from more than one glossary. > - restricting terms under a category to have unique names (we need to get > consensus as to whether this is something we would like) > > These sorts of restrictions need to policed in the Java code - as there is no > place for them in the model. For the Glossary, we are looking to add a new > OMAS layer around the base Atlas entity APIs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1831) Virtualiser to dynamically configure an information virtualization layer
[ https://issues.apache.org/jira/browse/ATLAS-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1831. --- Resolution: Fixed Delivered through Egeria > Virtualiser to dynamically configure an information virtualization layer > > > Key: ATLAS-1831 > URL: https://issues.apache.org/jira/browse/ATLAS-1831 > Project: Atlas > Issue Type: New Feature > Components: atlas-intg >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Yao Li >Priority: Major > Labels: VirtualDataConnector > Attachments: 0008-ATLAS-1831-29-03-2018.patch, Virtualiser Summary - > JIRA.pdf, java doc.zip > > > Code review is available in [https://reviews.apache.org/r/66174/] > This component listens for events from the Information View OMAS event > publisher built by ATLAS-1711 > (https://issues.apache.org/jira/browse/ATLAS-1711) to detect changes to > relational data assets and configures an information virtualization tool > (Gaian in the first instance) to create/maintain a view that maps to the > physical data asset. It also populates Information View metadata (using the > Information View OMAS API) for each of the views it creates. > RANGER-1485 (https://issues.apache.org/jira/browse/RANGER-1485) will also > configure Gaian with enforcement logic to apply data protection rules to the > data when queries are made to the views. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1700) Add constraints to JAVA API
[ https://issues.apache.org/jira/browse/ATLAS-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1700. --- Resolution: Fixed Delivered through Egeria > Add constraints to JAVA API > --- > > Key: ATLAS-1700 > URL: https://issues.apache.org/jira/browse/ATLAS-1700 > Project: Atlas > Issue Type: Sub-task >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > > Add constraints to JAVA API for the Glossary. There are some constraints that > can be captured using the constraints in the type model. For the Glossary > API, there are restrictions that cannot be captured in the type model. I am > thinking of constraints like: > - policing that we do not allow a category to be updated to have a parent as > one of its descendants. > - policing that we do not allow a category from another glossary to be added > under our category > - policing that we do not allow a category to be updated, such that the > category tree contains categories from more than one glossary. > - restricting terms under a category to have unique names (we need to get > consensus as to whether this is something we would like) > > These sorts of restrictions need to policed in the Java code - as there is no > place for them in the model. For the Glossary, we are looking to add a new > OMAS layer around the base Atlas entity APIs. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1699) Add REST API
[ https://issues.apache.org/jira/browse/ATLAS-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1699. --- Resolution: Fixed Delivered through Egeria > Add REST API > > > Key: ATLAS-1699 > URL: https://issues.apache.org/jira/browse/ATLAS-1699 > Project: Atlas > Issue Type: Sub-task >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > > Add constraints to JAVA API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1699) Add REST API
[ https://issues.apache.org/jira/browse/ATLAS-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1699. - > Add REST API > > > Key: ATLAS-1699 > URL: https://issues.apache.org/jira/browse/ATLAS-1699 > Project: Atlas > Issue Type: Sub-task >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > > Add constraints to JAVA API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (ATLAS-1693) Improve Classifications to introduce Classification Schemes
[ https://issues.apache.org/jira/browse/ATLAS-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell resolved ATLAS-1693. --- Resolution: Fixed Delivered through Egeria > Improve Classifications to introduce Classification Schemes > --- > > Key: ATLAS-1693 > URL: https://issues.apache.org/jira/browse/ATLAS-1693 > Project: Atlas > Issue Type: Improvement >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > > Improve Classifications to introduce Classification Schemes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (ATLAS-1693) Improve Classifications to introduce Classification Schemes
[ https://issues.apache.org/jira/browse/ATLAS-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell closed ATLAS-1693. - > Improve Classifications to introduce Classification Schemes > --- > > Key: ATLAS-1693 > URL: https://issues.apache.org/jira/browse/ATLAS-1693 > Project: Atlas > Issue Type: Improvement >Reporter: David Radley >Priority: Major > Labels: VirtualDataConnector > > Improve Classifications to introduce Classification Schemes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ATLAS-1828) Catalog OMAS
[ https://issues.apache.org/jira/browse/ATLAS-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276656#comment-16276656 ] Mandy Chessell commented on ATLAS-1828: --- Hello Maryna - I think this is a good idea - to make it easier to mach up the Jiras with the wiki > Catalog OMAS > > > Key: ATLAS-1828 > URL: https://issues.apache.org/jira/browse/ATLAS-1828 > Project: Atlas > Issue Type: New Feature > Components: atlas-core >Affects Versions: 1.0.0 >Reporter: Mandy Chessell >Assignee: Mandy Chessell > Labels: VirtualDataConnector > > This JIRA delivers the External API for catalog search applications. This > API is used by ATLAS-1765 (https://issues.apache.org/jira/browse/ATLAS-1765) > that provides the Self-Service Catalog Search and Data Preview UI. > This JIRA is dependent on ATLAS-1773 > (https://issues.apache.org/jira/browse/ATLAS-1773) that implements the OMRS > REST Connector -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1095) Open connector framework
[ https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1095: -- Attachment: 0001-ATLAS-1095-final-code-drop-for-OCF.patch > Open connector framework > > > Key: ATLAS-1095 > URL: https://issues.apache.org/jira/browse/ATLAS-1095 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Stephanie Hazlewood >Assignee: Mandy Chessell > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1095-final-code-drop-for-OCF.patch, OCF > Javadoc.zip, Open Connector Framework - 20th June 2017.doc, Open Connector > Framework - 9th May 2017.doc > > > Atlas provides a common approach to metadata management and governance across > all systems and data within an organization. Today Atlas provides access to > metadata. A connector provides access to a data source. As connectors are > the proxy of all data, they can also be explicit providers of metadata. > This JIRA proposes an open connector framework to manage connectors that > provide access to both data and the metadata Atlas provides together through > a single connector interface. > This will help data tools to to better the exchange of information between > platforms. It also offers new opportunities for the consistent enforcement of > the governance policies and rules (e.g., rules of visibility). Source > connector/connection metadata provides the nucleus around which all other > metadata describing the data builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1095) Open connector framework
[ https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1095: -- Attachment: (was: 0001-ATLAS-1095-initial-code-drop-for-OCF-with-fixes-from.patch) > Open connector framework > > > Key: ATLAS-1095 > URL: https://issues.apache.org/jira/browse/ATLAS-1095 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Stephanie Hazlewood >Assignee: Mandy Chessell > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1095-final-code-drop-for-OCF.patch, OCF > Javadoc.zip, Open Connector Framework - 20th June 2017.doc, Open Connector > Framework - 9th May 2017.doc > > > Atlas provides a common approach to metadata management and governance across > all systems and data within an organization. Today Atlas provides access to > metadata. A connector provides access to a data source. As connectors are > the proxy of all data, they can also be explicit providers of metadata. > This JIRA proposes an open connector framework to manage connectors that > provide access to both data and the metadata Atlas provides together through > a single connector interface. > This will help data tools to to better the exchange of information between > platforms. It also offers new opportunities for the consistent enforcement of > the governance policies and rules (e.g., rules of visibility). Source > connector/connection metadata provides the nucleus around which all other > metadata describing the data builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1095) Open connector framework
[ https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1095: -- Attachment: (was: ATLAS-1095.patch) > Open connector framework > > > Key: ATLAS-1095 > URL: https://issues.apache.org/jira/browse/ATLAS-1095 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Stephanie Hazlewood >Assignee: Mandy Chessell > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1095-final-code-drop-for-OCF.patch, OCF > Javadoc.zip, Open Connector Framework - 20th June 2017.doc, Open Connector > Framework - 9th May 2017.doc > > > Atlas provides a common approach to metadata management and governance across > all systems and data within an organization. Today Atlas provides access to > metadata. A connector provides access to a data source. As connectors are > the proxy of all data, they can also be explicit providers of metadata. > This JIRA proposes an open connector framework to manage connectors that > provide access to both data and the metadata Atlas provides together through > a single connector interface. > This will help data tools to to better the exchange of information between > platforms. It also offers new opportunities for the consistent enforcement of > the governance policies and rules (e.g., rules of visibility). Source > connector/connection metadata provides the nucleus around which all other > metadata describing the data builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1095) Open connector framework
[ https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1095: -- Attachment: (was: 0001-ATLAS-1095-final-code-drop-for-OCF.patch) > Open connector framework > > > Key: ATLAS-1095 > URL: https://issues.apache.org/jira/browse/ATLAS-1095 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Stephanie Hazlewood >Assignee: Mandy Chessell > Labels: VirtualDataConnector > Attachments: OCF Javadoc.zip, Open Connector Framework - 20th June > 2017.doc, Open Connector Framework - 9th May 2017.doc > > > Atlas provides a common approach to metadata management and governance across > all systems and data within an organization. Today Atlas provides access to > metadata. A connector provides access to a data source. As connectors are > the proxy of all data, they can also be explicit providers of metadata. > This JIRA proposes an open connector framework to manage connectors that > provide access to both data and the metadata Atlas provides together through > a single connector interface. > This will help data tools to to better the exchange of information between > platforms. It also offers new opportunities for the consistent enforcement of > the governance policies and rules (e.g., rules of visibility). Source > connector/connection metadata provides the nucleus around which all other > metadata describing the data builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1095) Open connector framework
[ https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1095: -- Attachment: 0001-ATLAS-1095-final-code-drop-for-OCF.patch > Open connector framework > > > Key: ATLAS-1095 > URL: https://issues.apache.org/jira/browse/ATLAS-1095 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Stephanie Hazlewood >Assignee: Mandy Chessell > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1095-final-code-drop-for-OCF.patch, OCF > Javadoc.zip, Open Connector Framework - 20th June 2017.doc, Open Connector > Framework - 9th May 2017.doc > > > Atlas provides a common approach to metadata management and governance across > all systems and data within an organization. Today Atlas provides access to > metadata. A connector provides access to a data source. As connectors are > the proxy of all data, they can also be explicit providers of metadata. > This JIRA proposes an open connector framework to manage connectors that > provide access to both data and the metadata Atlas provides together through > a single connector interface. > This will help data tools to to better the exchange of information between > platforms. It also offers new opportunities for the consistent enforcement of > the governance policies and rules (e.g., rules of visibility). Source > connector/connection metadata provides the nucleus around which all other > metadata describing the data builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1095) Open connector framework
[ https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1095: -- Attachment: (was: OCF Javadoc.zip) > Open connector framework > > > Key: ATLAS-1095 > URL: https://issues.apache.org/jira/browse/ATLAS-1095 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Stephanie Hazlewood >Assignee: Mandy Chessell > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1095-final-code-drop-for-OCF.patch, OCF > JavaDoc.zip, Open Connector Framework - 20th June 2017.doc, Open Connector > Framework - 9th May 2017.doc > > > Atlas provides a common approach to metadata management and governance across > all systems and data within an organization. Today Atlas provides access to > metadata. A connector provides access to a data source. As connectors are > the proxy of all data, they can also be explicit providers of metadata. > This JIRA proposes an open connector framework to manage connectors that > provide access to both data and the metadata Atlas provides together through > a single connector interface. > This will help data tools to to better the exchange of information between > platforms. It also offers new opportunities for the consistent enforcement of > the governance policies and rules (e.g., rules of visibility). Source > connector/connection metadata provides the nucleus around which all other > metadata describing the data builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1095) Open connector framework
[ https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1095: -- Attachment: OCF JavaDoc.zip > Open connector framework > > > Key: ATLAS-1095 > URL: https://issues.apache.org/jira/browse/ATLAS-1095 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Stephanie Hazlewood >Assignee: Mandy Chessell > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1095-final-code-drop-for-OCF.patch, OCF > JavaDoc.zip, Open Connector Framework - 20th June 2017.doc, Open Connector > Framework - 9th May 2017.doc > > > Atlas provides a common approach to metadata management and governance across > all systems and data within an organization. Today Atlas provides access to > metadata. A connector provides access to a data source. As connectors are > the proxy of all data, they can also be explicit providers of metadata. > This JIRA proposes an open connector framework to manage connectors that > provide access to both data and the metadata Atlas provides together through > a single connector interface. > This will help data tools to to better the exchange of information between > platforms. It also offers new opportunities for the consistent enforcement of > the governance policies and rules (e.g., rules of visibility). Source > connector/connection metadata provides the nucleus around which all other > metadata describing the data builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ATLAS-1095) Open connector framework
[ https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16323811#comment-16323811 ] Mandy Chessell commented on ATLAS-1095: --- I have added the ConnectorCheckedException to the disconnect() method. When I make the changes to private Map additionalProperties = new HashMap<>(); in Additional properties, IntelliJ says adding the "String, Object" in new HashMap(); is obsolete and should be removed. Is it causing an error? > Open connector framework > > > Key: ATLAS-1095 > URL: https://issues.apache.org/jira/browse/ATLAS-1095 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Stephanie Hazlewood >Assignee: Mandy Chessell > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1095-final-code-drop-for-OCF.patch, OCF > JavaDoc.zip, Open Connector Framework - 20th June 2017.doc, Open Connector > Framework - 9th May 2017.doc > > > Atlas provides a common approach to metadata management and governance across > all systems and data within an organization. Today Atlas provides access to > metadata. A connector provides access to a data source. As connectors are > the proxy of all data, they can also be explicit providers of metadata. > This JIRA proposes an open connector framework to manage connectors that > provide access to both data and the metadata Atlas provides together through > a single connector interface. > This will help data tools to to better the exchange of information between > platforms. It also offers new opportunities for the consistent enforcement of > the governance policies and rules (e.g., rules of visibility). Source > connector/connection metadata provides the nucleus around which all other > metadata describing the data builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1095) Open connector framework
[ https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1095: -- Attachment: (was: 0001-ATLAS-1095-final-code-drop-for-OCF.patch) > Open connector framework > > > Key: ATLAS-1095 > URL: https://issues.apache.org/jira/browse/ATLAS-1095 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Stephanie Hazlewood >Assignee: Mandy Chessell > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1095-final-code-drop-for-OCF.patch, OCF > JavaDoc.zip, Open Connector Framework - 20th June 2017.doc, Open Connector > Framework - 9th May 2017.doc > > > Atlas provides a common approach to metadata management and governance across > all systems and data within an organization. Today Atlas provides access to > metadata. A connector provides access to a data source. As connectors are > the proxy of all data, they can also be explicit providers of metadata. > This JIRA proposes an open connector framework to manage connectors that > provide access to both data and the metadata Atlas provides together through > a single connector interface. > This will help data tools to to better the exchange of information between > platforms. It also offers new opportunities for the consistent enforcement of > the governance policies and rules (e.g., rules of visibility). Source > connector/connection metadata provides the nucleus around which all other > metadata describing the data builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ATLAS-1095) Open connector framework
[ https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mandy Chessell updated ATLAS-1095: -- Attachment: 0001-ATLAS-1095-final-code-drop-for-OCF.patch > Open connector framework > > > Key: ATLAS-1095 > URL: https://issues.apache.org/jira/browse/ATLAS-1095 > Project: Atlas > Issue Type: New Feature >Affects Versions: 1.0.0 >Reporter: Stephanie Hazlewood >Assignee: Mandy Chessell > Labels: VirtualDataConnector > Attachments: 0001-ATLAS-1095-final-code-drop-for-OCF.patch, OCF > JavaDoc.zip, Open Connector Framework - 20th June 2017.doc, Open Connector > Framework - 9th May 2017.doc > > > Atlas provides a common approach to metadata management and governance across > all systems and data within an organization. Today Atlas provides access to > metadata. A connector provides access to a data source. As connectors are > the proxy of all data, they can also be explicit providers of metadata. > This JIRA proposes an open connector framework to manage connectors that > provide access to both data and the metadata Atlas provides together through > a single connector interface. > This will help data tools to to better the exchange of information between > platforms. It also offers new opportunities for the consistent enforcement of > the governance policies and rules (e.g., rules of visibility). Source > connector/connection metadata provides the nucleus around which all other > metadata describing the data builds. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
