Re: [DRAFT] Board report for Apache Atlas: March 2019
Hello Madhan, This reasoning makes sense. But it is worrying that no new committers are becoming long term contributors to the project. May be there would be more motivation for new committers to continue contributions if there was a definition of what makes a "deserving committer". I am sure it is different in many cases, but just some examples might help? For example, sustained contributions over x months etc. Building up the number of experienced active committers that are progressing to be PMC members would help spread the load of mentoring new contributors and committers as the community grows. This in turn could help accelerate the growth of the community. All the best Mandy _______ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: mandy_chess...@uk.ibm.com LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49 Assistant: Janet Brooks - jsbrook...@uk.ibm.com From: Madhan Neethiraj To: "dev@atlas.apache.org" Date: 14/03/2019 08:18 Subject:Re: [DRAFT] Board report for Apache Atlas: March 2019 Mandy, Consistent contribution over period of time is the key criteria to become a committer and then PMC. As you noted, Atlas PMC has been moving contributors to committers based on their sustained involvement and contributions in the project. While new folks continue to join the community and make awesome contributions, there has been reduced engagement from recent committers; hence no recent additions to PMC. Atlas PMC will continue to look for contributions and engagements, and will offer PMC role to deserving committers. Thanks, Madhan On 3/13/19, 11:58 PM, "Mandy Chessell" wrote: Dear All, Looking at the reports month by month, the code activity and the growth in the number of contributors/committers is looking very healthy. We can see contributors moving to committer status. However it does look strange that no new committer has been promoted to the PMC for nearly 2 years. The board may see that as a possible problem in the operation of the community? Perhaps it would be helpful to send out some hints to the community on what a committer has to do to be considered for the PMC? All the best Mandy _______ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: mandy_chess...@uk.ibm.com LinkedIn: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_pub_mandy-2Dchessell_22_897_a49=DwIFaQ=jf_iaSHvJObTbx-siA1ZOg=DEupm0k8-ppAmw6rImSmuE_tc4KzDG1cSUr7Fo_5T8Q=eM0zeUMK6bFkqsyYHusC0ngwXvc8Hq-20ilHH3qg0qo=LnLxL1nchbM5UsTaoA4ZbA77oKCZ9N3w79llRs4ATns= Assistant: Janet Brooks - jsbrook...@uk.ibm.com From: Nixon Rodrigues To: dev@atlas.apache.org Date: 14/03/2019 05:17 Subject:Re: [DRAFT] Board report for Apache Atlas: March 2019 Madhan thanks for draft, It looks good. Slight correction in needed in 2.0.0 release date. >> 2.0.0plan to release by 12/31/2018 Nixon On Thu, Mar 14, 2019 at 6:50 AM Madhan Neethiraj wrote: > Atlas team, > > > > Please review the draft board report below and send your feedback/comments. > > > > Thanks, > > Madhan > > > > > > ## Description: > > Apache Atlas is a scalable and extensible set of core foundational > > governance services that enables enterprises to effectively and > efficiently > > meet their compliance requirements within Hadoop and allows integration > with > > the complete enterprise data ecosystem > > > > ## Issues: > > There are no issues requiring board attention at this time. > > > > ## Activity: > > - significant updates to lineage UI - faster rendering, searchability, > option to hide entities, highlight selected entity path, .. > > - added option to ignore/prune metadata for temporary/staging Hive tables > > - support for custom icons per entity-type > > - significant performance improvements during create/update of entities > > - added support for notifications on relationship changes > > - model updates to remove use of ownedRef/inverseRef constraints > > - enhancements to enable Atlas
Re: [DRAFT] Board report for Apache Atlas: March 2019
Dear All, Looking at the reports month by month, the code activity and the growth in the number of contributors/committers is looking very healthy. We can see contributors moving to committer status. However it does look strange that no new committer has been promoted to the PMC for nearly 2 years. The board may see that as a possible problem in the operation of the community? Perhaps it would be helpful to send out some hints to the community on what a committer has to do to be considered for the PMC? All the best Mandy ___ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: mandy_chess...@uk.ibm.com LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49 Assistant: Janet Brooks - jsbrook...@uk.ibm.com From: Nixon Rodrigues To: dev@atlas.apache.org Date: 14/03/2019 05:17 Subject:Re: [DRAFT] Board report for Apache Atlas: March 2019 Madhan thanks for draft, It looks good. Slight correction in needed in 2.0.0 release date. >> 2.0.0plan to release by 12/31/2018 Nixon On Thu, Mar 14, 2019 at 6:50 AM Madhan Neethiraj wrote: > Atlas team, > > > > Please review the draft board report below and send your feedback/comments. > > > > Thanks, > > Madhan > > > > > > ## Description: > > Apache Atlas is a scalable and extensible set of core foundational > > governance services that enables enterprises to effectively and > efficiently > > meet their compliance requirements within Hadoop and allows integration > with > > the complete enterprise data ecosystem > > > > ## Issues: > > There are no issues requiring board attention at this time. > > > > ## Activity: > > - significant updates to lineage UI - faster rendering, searchability, > option to hide entities, highlight selected entity path, .. > > - added option to ignore/prune metadata for temporary/staging Hive tables > > - support for custom icons per entity-type > > - significant performance improvements during create/update of entities > > - added support for notifications on relationship changes > > - model updates to remove use of ownedRef/inverseRef constraints > > - enhancements to enable Atlas to be a reference implementation for > Egeria > - working on 2.0.0 release, to support Hadoop 3, HBase 2, Solr 7, Kafka > 2, Hive 3 > > > > ## Health report: > > - 5 new contributors added in last 3 months: Aadarsh, Binit, Le Ma, > Sridhar K, Sridhar S > > > > ## PMC changes: > > - Currently 33 PMC members > > - No new PMC members added in last 3 months > > - Last PMC member addition was on 6/21/2017 > > > > ## Committer base changes: > > - Currently 38 committers > > - No new committers added in last 3 months > > - Last addition to committer role was on 10/15/2018 > > > > ## Releases: > > 2.0.0plan to release by 12/31/2018 > > 0.8.3was released on 10/31/2018 > > 1.1.0was released on 09/17/2018 > > 1.0.0was released on 06/02/2018 > > 0.8.2was released on 02/05/2018 > > 1.0.0-alpha was released on 01/25/2018 > > 0.8.1was released on 08/29/2017 > > 0.8-incubating was released on 03/16/2017 > > 0.7.1-incubating was released on 01/26/2017 > > 0.7-incubating was released on 07/09/2016 > > 0.6-incubating was released on 12/31/2015 > > 0.5-incubating was released on 07/11/2015 > > > > Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: Consensus for migration of git repositories to gitbox
Thank you Apoorv :) +1 to be proactive about the migration. All the best Mandy ___ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: mandy_chess...@uk.ibm.com LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49 Assistant: Janet Brooks - jsbrook...@uk.ibm.com From: Apoorv Naik To: dev Date: 10/01/2019 07:20 Subject:Consensus for migration of git repositories to gitbox Hi Atlas devs, There's an ASF initiative to migrate the git-wip-us-apache.org repositories to the gitbox server before Feb 7, after which it'll be mass migrated without a warning. I volunteer to take this migration effort to avoid any disruption to commit activity. PMCs and committers, please share your +1 or -1 vote for this move (this is the first step in starting the migration) *Apoorv Naik* Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
[jira] [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] [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-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-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] [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-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] [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] [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] [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-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-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] [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-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-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] [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] [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] [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] [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-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-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] [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-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-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] [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-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-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-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-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-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] [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-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-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-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-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-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-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-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] [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] [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] [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] [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] [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-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-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] [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] [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] [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-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-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] [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] [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-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-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-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] [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] [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-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-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] [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] [Commented] (ATLAS-1691) OMAS Interfaces for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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-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] [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] [Commented] (ATLAS-1847) Open Metadata and Governance
[ https://issues.apache.org/jira/browse/ATLAS-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [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=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-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] [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)
Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67083/#review203262 --- omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java Lines 336 (patched) <https://reviews.apache.org/r/67083/#comment285364> If we are using plurals then why is this not "cohorts"? omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java Lines 425 (patched) <https://reviews.apache.org/r/67083/#comment285365> Should this be "cohorts"? - Mandy Chessell On May 16, 2018, 3:49 p.m., Bogdan Sava wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67083/ > --- > > (Updated May 16, 2018, 3:49 p.m.) > > > Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy > Chessell, and Ruxandra Rosu. > > > Repository: atlas > > > Description > --- > > Create configuration for OMAG API in Atlas > > > Diffs > - > > om-fwk-ocf/pom.xml 8b1cefd > omag-api/pom.xml 2338286 > > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java > dd19018 > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java > ebc9f2a > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java > 1a15215 > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java > c2950c4 > omag-server/pom.xml 527c5c3 > > omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java > 88397de > omag-server/src/main/resources/application.properties PRE-CREATION > omas-assetconsumer/pom.xml 29935e7 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java > 80a98f5 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java > > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > 967be5a > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java > PRE-CREATION > omas-connectedasset/README.md 2f431df > omas-connectedasset/pom.xml 219c972 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java > 8ae6c37 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java > PRE-CREATION > omrs/pom.xml 50b9898 > > omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java > 7ae87c6 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java > 5948482 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > 3f85317 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > ccf0de6 > webapp/pom.xml 03b8408 > webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 > webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION > webapp/src/main/webapp/WEB-INF/web.xml 23dc063 > > > Diff: https://reviews.apache.org/r/67083/diff/4/ > > > Testing > --- > > Create configuration for OMAG API in Atlas using Spring MVC Dispatcher > servlet. > > > Change base URL for the API to "/open-metadata/access-services" > > > Clean maven unused dependenies > > The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665 > > > File Attachments > > > Added apache licence to a properties file > > https://reviews.apache.org/media/uploaded/files/2018/05/11/77fbc4f6-b16a-42f9-983c-261f70f3ca9f__0002-ATLAS-2665-Added-apache-licence-to-properties-file.patch > 0003-ATLAS-2665-comments-fixed.patch > > https://reviews.apache.org/media/uploaded/files/2018/05/11/004f018b-1ee5-4da1-91d4-b50f4913298d__0003-ATLAS-2665-comments-fixed.patch > ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch > > https://reviews.apache.org/media/uploaded/files/2018/05/14/160f8499-661d-4fa9-8ce1-afe4bd88b723__ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch > > > Thanks, > > Bogdan Sava > >
Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67083/#review203261 --- omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java Lines 363 (patched) <https://reviews.apache.org/r/67083/#comment285363> This should be access-services because it supplies the configuration for all access services - Mandy Chessell On May 16, 2018, 3:49 p.m., Bogdan Sava wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67083/ > --- > > (Updated May 16, 2018, 3:49 p.m.) > > > Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy > Chessell, and Ruxandra Rosu. > > > Repository: atlas > > > Description > --- > > Create configuration for OMAG API in Atlas > > > Diffs > - > > om-fwk-ocf/pom.xml 8b1cefd > omag-api/pom.xml 2338286 > > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java > dd19018 > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java > ebc9f2a > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java > 1a15215 > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java > c2950c4 > omag-server/pom.xml 527c5c3 > > omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java > 88397de > omag-server/src/main/resources/application.properties PRE-CREATION > omas-assetconsumer/pom.xml 29935e7 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java > 80a98f5 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java > > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > 967be5a > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java > PRE-CREATION > omas-connectedasset/README.md 2f431df > omas-connectedasset/pom.xml 219c972 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java > 8ae6c37 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java > PRE-CREATION > omrs/pom.xml 50b9898 > > omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java > 7ae87c6 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java > 5948482 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > 3f85317 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > ccf0de6 > webapp/pom.xml 03b8408 > webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 > webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION > webapp/src/main/webapp/WEB-INF/web.xml 23dc063 > > > Diff: https://reviews.apache.org/r/67083/diff/4/ > > > Testing > --- > > Create configuration for OMAG API in Atlas using Spring MVC Dispatcher > servlet. > > > Change base URL for the API to "/open-metadata/access-services" > > > Clean maven unused dependenies > > The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665 > > > File Attachments > > > Added apache licence to a properties file > > https://reviews.apache.org/media/uploaded/files/2018/05/11/77fbc4f6-b16a-42f9-983c-261f70f3ca9f__0002-ATLAS-2665-Added-apache-licence-to-properties-file.patch > 0003-ATLAS-2665-comments-fixed.patch > > https://reviews.apache.org/media/uploaded/files/2018/05/11/004f018b-1ee5-4da1-91d4-b50f4913298d__0003-ATLAS-2665-comments-fixed.patch > ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch > > https://reviews.apache.org/media/uploaded/files/2018/05/14/160f8499-661d-4fa9-8ce1-afe4bd88b723__ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch > > > Thanks, > > Bogdan Sava > >
Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67083/#review203260 --- omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java Lines 187 (patched) <https://reviews.apache.org/r/67083/#comment285362> This should be /access-services/mode since it affects all access services - Mandy Chessell On May 16, 2018, 3:49 p.m., Bogdan Sava wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67083/ > --- > > (Updated May 16, 2018, 3:49 p.m.) > > > Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy > Chessell, and Ruxandra Rosu. > > > Repository: atlas > > > Description > --- > > Create configuration for OMAG API in Atlas > > > Diffs > - > > om-fwk-ocf/pom.xml 8b1cefd > omag-api/pom.xml 2338286 > > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java > dd19018 > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java > ebc9f2a > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java > 1a15215 > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java > c2950c4 > omag-server/pom.xml 527c5c3 > > omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java > 88397de > omag-server/src/main/resources/application.properties PRE-CREATION > omas-assetconsumer/pom.xml 29935e7 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java > 80a98f5 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java > > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > 967be5a > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java > PRE-CREATION > omas-connectedasset/README.md 2f431df > omas-connectedasset/pom.xml 219c972 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java > 8ae6c37 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java > PRE-CREATION > omrs/pom.xml 50b9898 > > omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java > 7ae87c6 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java > 5948482 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > 3f85317 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > ccf0de6 > webapp/pom.xml 03b8408 > webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 > webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION > webapp/src/main/webapp/WEB-INF/web.xml 23dc063 > > > Diff: https://reviews.apache.org/r/67083/diff/4/ > > > Testing > --- > > Create configuration for OMAG API in Atlas using Spring MVC Dispatcher > servlet. > > > Change base URL for the API to "/open-metadata/access-services" > > > Clean maven unused dependenies > > The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665 > > > File Attachments > > > Added apache licence to a properties file > > https://reviews.apache.org/media/uploaded/files/2018/05/11/77fbc4f6-b16a-42f9-983c-261f70f3ca9f__0002-ATLAS-2665-Added-apache-licence-to-properties-file.patch > 0003-ATLAS-2665-comments-fixed.patch > > https://reviews.apache.org/media/uploaded/files/2018/05/11/004f018b-1ee5-4da1-91d4-b50f4913298d__0003-ATLAS-2665-comments-fixed.patch > ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch > > https://reviews.apache.org/media/uploaded/files/2018/05/14/160f8499-661d-4fa9-8ce1-afe4bd88b723__ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch > > > Thanks, > > Bogdan Sava > >
Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas
> On May 11, 2018, 10:34 a.m., David Radley wrote: > > omag-server/src/main/java/org/apache/atlas/omag/application/OMAGServerAdminResource.java > > Lines 510 (patched) > > <https://reviews.apache.org/r/67083/diff/1/?file=2019875#file2019875line510> > > > > OMAGInvalidParameterException is a checked excpetion so would need to > > be specified on the method signature. I think we need to remove all of the > > comments indicating that the this method can throw exceptions as it can now > > only return the void response, which contains the error details. It is wrong to remove the comments about the exceptions that are passed in the response object. - Mandy --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67083/#review202910 --- On May 16, 2018, 3:49 p.m., Bogdan Sava wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67083/ > --- > > (Updated May 16, 2018, 3:49 p.m.) > > > Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy > Chessell, and Ruxandra Rosu. > > > Repository: atlas > > > Description > --- > > Create configuration for OMAG API in Atlas > > > Diffs > - > > om-fwk-ocf/pom.xml 8b1cefd > omag-api/pom.xml 2338286 > > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java > dd19018 > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java > ebc9f2a > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java > 1a15215 > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java > c2950c4 > omag-server/pom.xml 527c5c3 > > omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java > 88397de > omag-server/src/main/resources/application.properties PRE-CREATION > omas-assetconsumer/pom.xml 29935e7 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java > 80a98f5 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java > > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > 967be5a > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java > PRE-CREATION > omas-connectedasset/README.md 2f431df > omas-connectedasset/pom.xml 219c972 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java > 8ae6c37 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java > PRE-CREATION > omrs/pom.xml 50b9898 > > omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java > 7ae87c6 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java > 5948482 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > 3f85317 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > ccf0de6 > webapp/pom.xml 03b8408 > webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 > webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION > webapp/src/main/webapp/WEB-INF/web.xml 23dc063 > > > Diff: https://reviews.apache.org/r/67083/diff/4/ > > > Testing > --- > > Create configuration for OMAG API in Atlas using Spring MVC Dispatcher > servlet. > > > Change base URL for the API to "/open-metadata/access-services" > > > Clean maven unused dependenies > > The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665 > > > File Attachments > --
Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas
Hello Graham, Bogdan We still need two interfaces for the OMAG Admin - one for the OMAG Server and one for Atlas Server. The Atlas Server one should turn on the Atlas Graph repository connector once open metadata is enabled. There should not be an API call to do this. The OMAG Server should support none, in-memory and repository proxy modes for the local repository. All the best Mandy ___ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: mandy_chess...@uk.ibm.com LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49 Assistant: Janet Brooks - jsbrook...@uk.ibm.com From: Graham Wallis <graham_wal...@uk.ibm.com> To: Mandy Chessell <mandy_chess...@uk.ibm.com>, Graham Wallis <graham_wal...@uk.ibm.com>, Daniela Otelea <daniela-valentina.ote...@ing.com>, Ruxandra Rosu <ruxandra-gabriela.r...@ing.com>, David Radley <david...@apache.org> Cc: Bogdan Sava <bogdan-mihail.s...@ing.com>, atlas <d...@atlas.incubator.apache.org> Date: 16/05/2018 14:52 Subject:Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas Sent by:Graham Wallis <nore...@reviews.apache.org> This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67083/ Hi Bogdan I just raised 3 issues - but they are all related. The key one is that I need to be able to set repository mode to LOCAL_GRAPH_REPOSITORY (for running in Atlas). This method was removed when there were two versions of the REST wrapper (one for inside Atlas, another for the OMAG Server). Now we have one wrapper I need a way of setting the local graph mode. The other two issues are just to accommodate the addition of the above and make them consistent. - Graham Wallis On May 15th, 2018, 1:35 p.m. UTC, Bogdan Sava wrote: Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy Chessell, and Ruxandra Rosu. By Bogdan Sava. Updated May 15, 2018, 1:35 p.m. Repository: atlas Description Create configuration for OMAG API in Atlas Testing Create configuration for OMAG API in Atlas using Spring MVC Dispatcher servlet. Change base URL for the API to "/open-metadata/access-services" Clean maven unused dependenies The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665 Diffs om-fwk-ocf/pom.xml (8b1cefd) omag-api/pom.xml (2338286) omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java (dd19018) omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java (PRE-CREATION) omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java (PRE-CREATION) omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java (ebc9f2a) omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java (PRE-CREATION) omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java (1a15215) omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java (c2950c4) omag-server/pom.xml (527c5c3) omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java (88397de) omag-server/src/main/resources/application.properties (PRE-CREATION) omas-assetconsumer/pom.xml (29935e7) omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java (80a98f5) omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java () omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java (967be5a) omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java (PRE-CREATION) omas-connectedasset/README.md (2f431df) omas-connectedasset/pom.xml (219c972) omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java (8ae6c37) omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java (PRE-CREATION) omrs/pom.xml (50b9898) omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java (7ae87c6) omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java (5948482) omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java (PRE-CREATION) omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java (3f85317) omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java (ccf0de6) webapp/pom.xml (03b8408) webapp/src/main/webapp/WEB-INF/applicationContext.xml (2ecd8d1) webapp/src/main/webapp/WEB-INF/openM
Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas
> On May 16, 2018, 1:48 p.m., Graham Wallis wrote: > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java > > Lines 231 (patched) > > <https://reviews.apache.org/r/67083/diff/3/?file=2023012#file2023012line231> > > > > We also need a method for the LOCAL_GRAPH_REPOSITORY. > > > > The URI should be "/local-repository/mode/local-graph-repository" > > > > The method should be "setGraphLocalRepository" (even though that sounds > > a bit weird it would be consistent with the others - change then all to > > setLocalRepositoryXXX() if you prefer). > > > > The body of the method should be: > > return adminAPI.setLocalRepositoryMode(userId, serverName, > > LocalRepositoryMode.LOCAL_GRAPH_REPOSITORY); The setting of the local graph repository should not be an external callable API. It is only valid in the Atlas server - and in which case it should always be set as soon as the open metadata function is turned on - basically we still need 2 APIs administration. - Mandy --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67083/#review203219 --- On May 15, 2018, 1:35 p.m., Bogdan Sava wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67083/ > --- > > (Updated May 15, 2018, 1:35 p.m.) > > > Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy > Chessell, and Ruxandra Rosu. > > > Repository: atlas > > > Description > --- > > Create configuration for OMAG API in Atlas > > > Diffs > - > > om-fwk-ocf/pom.xml 8b1cefd > omag-api/pom.xml 2338286 > > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java > dd19018 > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java > ebc9f2a > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java > 1a15215 > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java > c2950c4 > omag-server/pom.xml 527c5c3 > > omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java > 88397de > omag-server/src/main/resources/application.properties PRE-CREATION > omas-assetconsumer/pom.xml 29935e7 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java > 80a98f5 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java > > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > 967be5a > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java > PRE-CREATION > omas-connectedasset/README.md 2f431df > omas-connectedasset/pom.xml 219c972 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java > 8ae6c37 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java > PRE-CREATION > omrs/pom.xml 50b9898 > > omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java > 7ae87c6 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java > 5948482 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > 3f85317 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > ccf0de6 > webapp/pom.xml 03b8408 > webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 > webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION > webapp/src/main/webapp/WEB-INF/web.xml 23dc063 > > > D
Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas
> On May 15, 2018, 3:53 p.m., David Radley wrote: > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java > > Lines 1143 (patched) > > <https://reviews.apache.org/r/67083/diff/3/?file=2023010#file2023010line1143> > > > > javadoc of exceptions mismatches the code. It is important this matches > > as it will be the basis of the the swagger. This is the same for many > > methods The Javadoc is correct in the patch. Notice there is no @throws tag. The Javadoc lists the possible responses (including exceptions) that can be returned in the response structure. - Mandy --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67083/#review203130 --- On May 15, 2018, 1:35 p.m., Bogdan Sava wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67083/ > --- > > (Updated May 15, 2018, 1:35 p.m.) > > > Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy > Chessell, and Ruxandra Rosu. > > > Repository: atlas > > > Description > --- > > Create configuration for OMAG API in Atlas > > > Diffs > - > > om-fwk-ocf/pom.xml 8b1cefd > omag-api/pom.xml 2338286 > > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java > dd19018 > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java > ebc9f2a > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java > 1a15215 > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java > c2950c4 > omag-server/pom.xml 527c5c3 > > omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java > 88397de > omag-server/src/main/resources/application.properties PRE-CREATION > omas-assetconsumer/pom.xml 29935e7 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java > 80a98f5 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java > > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > 967be5a > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java > PRE-CREATION > omas-connectedasset/README.md 2f431df > omas-connectedasset/pom.xml 219c972 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java > 8ae6c37 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java > PRE-CREATION > omrs/pom.xml 50b9898 > > omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java > 7ae87c6 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java > 5948482 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > 3f85317 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > ccf0de6 > webapp/pom.xml 03b8408 > webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 > webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION > webapp/src/main/webapp/WEB-INF/web.xml 23dc063 > > > Diff: https://reviews.apache.org/r/67083/diff/3/ > > > Testing > --- > > Create configuration for OMAG API in Atlas using Spring MVC Dispatcher > servlet. > > > Change base URL for the API to "/open-metadata/access-services" > > > Clean maven unused dependenies > > The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665 > > > File Attachments > > > Added apache licence to a proper
Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas
> On May 15, 2018, 3:53 p.m., David Radley wrote: > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > > Line 230 (original), 211 (patched) > > <https://reviews.apache.org/r/67083/diff/3/?file=2023021#file2023021line230> > > > > this change have removed the PathVariable and RequestParam annotations, > > it looks like we have lost inforration about which parameters are > > PathVariables and which are RequestParams > > Mandy Chessell wrote: > It is correct that the annotations have been removed from this file - the > annotation should be in the Resource file The patch is correct without changes - Mandy --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67083/#review203130 --- On May 15, 2018, 1:35 p.m., Bogdan Sava wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67083/ > --- > > (Updated May 15, 2018, 1:35 p.m.) > > > Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy > Chessell, and Ruxandra Rosu. > > > Repository: atlas > > > Description > --- > > Create configuration for OMAG API in Atlas > > > Diffs > - > > om-fwk-ocf/pom.xml 8b1cefd > omag-api/pom.xml 2338286 > > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java > dd19018 > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java > ebc9f2a > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java > 1a15215 > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java > c2950c4 > omag-server/pom.xml 527c5c3 > > omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java > 88397de > omag-server/src/main/resources/application.properties PRE-CREATION > omas-assetconsumer/pom.xml 29935e7 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java > 80a98f5 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java > > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > 967be5a > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java > PRE-CREATION > omas-connectedasset/README.md 2f431df > omas-connectedasset/pom.xml 219c972 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java > 8ae6c37 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java > PRE-CREATION > omrs/pom.xml 50b9898 > > omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java > 7ae87c6 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java > 5948482 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > 3f85317 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > ccf0de6 > webapp/pom.xml 03b8408 > webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 > webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION > webapp/src/main/webapp/WEB-INF/web.xml 23dc063 > > > Diff: https://reviews.apache.org/r/67083/diff/3/ > > > Testing > --- > > Create configuration for OMAG API in Atlas using Spring MVC Dispatcher > servlet. > > > Change base URL for the API to "/open-metadata/access-services" > > > Clean maven unused dependenies > > The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665 > > > File Attachments >
Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas
> On May 15, 2018, 3:53 p.m., David Radley wrote: > > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java > > Line 180 (original), 181 (patched) > > <https://reviews.apache.org/r/67083/diff/3/?file=2023008#file2023008line188> > > > > you have remove the throws clause in the latest patch but the javadoc > > is left in. I suggest leaving in the throws clause. I think they are there > > to indicate these are the exceptions that any validation code we add in the > > future might throw The Javadoc does not have the @throws tag in it any more. The documentation you see describes the different responses supported by the VoidResponse structure. The Javadoc in the patch is correct. - Mandy --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67083/#review203130 --- On May 15, 2018, 1:35 p.m., Bogdan Sava wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67083/ > --- > > (Updated May 15, 2018, 1:35 p.m.) > > > Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy > Chessell, and Ruxandra Rosu. > > > Repository: atlas > > > Description > --- > > Create configuration for OMAG API in Atlas > > > Diffs > - > > om-fwk-ocf/pom.xml 8b1cefd > omag-api/pom.xml 2338286 > > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java > dd19018 > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java > ebc9f2a > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java > 1a15215 > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java > c2950c4 > omag-server/pom.xml 527c5c3 > > omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java > 88397de > omag-server/src/main/resources/application.properties PRE-CREATION > omas-assetconsumer/pom.xml 29935e7 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java > 80a98f5 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java > > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > 967be5a > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java > PRE-CREATION > omas-connectedasset/README.md 2f431df > omas-connectedasset/pom.xml 219c972 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java > 8ae6c37 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java > PRE-CREATION > omrs/pom.xml 50b9898 > > omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java > 7ae87c6 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java > 5948482 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > 3f85317 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > ccf0de6 > webapp/pom.xml 03b8408 > webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 > webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION > webapp/src/main/webapp/WEB-INF/web.xml 23dc063 > > > Diff: https://reviews.apache.org/r/67083/diff/3/ > > > Testing > --- > > Create configuration for OMAG API in Atlas using Spring MVC Dispatcher > servlet. > > > Change base URL for the API to "/open-metadata/access-services" > > > Clean maven unused dependenies > > The Jira issue is https://issues.apache.org/jira/bro
Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas
> On May 15, 2018, 3:53 p.m., David Radley wrote: > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > > Line 230 (original), 211 (patched) > > <https://reviews.apache.org/r/67083/diff/3/?file=2023021#file2023021line230> > > > > this change have removed the PathVariable and RequestParam annotations, > > it looks like we have lost inforration about which parameters are > > PathVariables and which are RequestParams It is correct that the annotations have been removed from this file - the annotation should be in the Resource file - Mandy --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67083/#review203130 --- On May 15, 2018, 1:35 p.m., Bogdan Sava wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/67083/ > --- > > (Updated May 15, 2018, 1:35 p.m.) > > > Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy > Chessell, and Ruxandra Rosu. > > > Repository: atlas > > > Description > --- > > Create configuration for OMAG API in Atlas > > > Diffs > - > > om-fwk-ocf/pom.xml 8b1cefd > omag-api/pom.xml 2338286 > > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java > dd19018 > omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java > ebc9f2a > > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java > PRE-CREATION > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java > 1a15215 > > omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java > c2950c4 > omag-server/pom.xml 527c5c3 > > omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java > 88397de > omag-server/src/main/resources/application.properties PRE-CREATION > omas-assetconsumer/pom.xml 29935e7 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java > 80a98f5 > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java > > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java > 967be5a > > omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java > PRE-CREATION > omas-connectedasset/README.md 2f431df > omas-connectedasset/pom.xml 219c972 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java > 8ae6c37 > > omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java > PRE-CREATION > omrs/pom.xml 50b9898 > > omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java > 7ae87c6 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java > 5948482 > > omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > 3f85317 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > ccf0de6 > webapp/pom.xml 03b8408 > webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 > webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION > webapp/src/main/webapp/WEB-INF/web.xml 23dc063 > > > Diff: https://reviews.apache.org/r/67083/diff/3/ > > > Testing > --- > > Create configuration for OMAG API in Atlas using Spring MVC Dispatcher > servlet. > > > Change base URL for the API to "/open-metadata/access-services" > > > Clean maven unused dependenies > > The Jira issue is https://issues.apache.org/jira/browse/ATLAS-2665 > > > File Attachments > > > Added apache licence to a properties file > >
[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] [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)
Re: Review Request 66784: ATLAS2604 Minor fixups to open metadata archive types
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/66784/#review202055 --- Ship it! Ship It! - Mandy Chessell On April 26, 2018, 2:37 p.m., David Radley wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/66784/ > --- > > (Updated April 26, 2018, 2:37 p.m.) > > > Review request for atlas, Madhan Neethiraj and Mandy Chessell. > > > Bugs: ATLAS2604 > https://issues.apache.org/jira/browse/ATLAS2604 > > > Repository: atlas > > > Description > --- > > ATLAS2604 Minor fixups to open metadata archive types to avoid duplicate > attributes due to relationship end names. > > > Diffs > - > > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveBuilder.java > 5902c4202 > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveHelper.java > 42d2d8746 > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java > faab96cac > omrs/src/main/java/org/apache/atlas/omrs/ffdc/OMRSErrorCode.java 351c910e3 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/66784/diff/3/ > > > Testing > --- > > Ran junit that failed without the patch applied. I ran this in Intellij using > the Maven view to run the test phase on the OMRS module. This successfully > ran the test. > > > Thanks, > > David Radley > >
Re: Cassandra support for Atlas v1.0
+1 for option 3 too All the best Mandy ___ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: mandy_chess...@uk.ibm.com LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49 Assistant: Janet Brooks - jsbrook...@uk.ibm.com From: Nixon Rodrigues <nixon.rodrig...@freestoneinfotech.com> To: dev@atlas.apache.org Date: 27/04/2018 06:01 Subject:Re: Cassandra support for Atlas v1.0 +1 for option #3 Cassandra as a store is good option for development purpose. Nixon On Fri, Apr 27, 2018, 1:07 AM Madhan Neethiraj <mad...@apache.org> wrote: > David - I agree on option #3 for 1.0 release. > > Thanks, > Madhan > > > > > On 4/26/18, 9:14 AM, "David Radley" <david_rad...@uk.ibm.com> wrote: > > Hi there, > We had a meeting to discuss how we would like to document the embedded > Cassandra support in Atlas v1.0. We talked of 3 options : > > 1) Include it in the code base but do not document. > 2) Document it as a tech preview > 3) Document it in the same way as the embedded solr and hbase build. > That > means it will be document as being supported for development, but not > in > production. > > My preference is option 3). Are there any objections to this approach? > many thanks, David. > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with > number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 > 3AU > > > >
[jira] [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-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)
Re: Review Request 66784: ATLAS2604 Minor fixups to open metadata archive types
> On April 26, 2018, 1:41 p.m., Mandy Chessell wrote: > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveBuilder.java > > Lines 563 (patched) > > <https://reviews.apache.org/r/66784/diff/2/?file=2012330#file2012330line563> > > > > Please use code layout consistent with the rest of file. For example - placement of braces - Mandy --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/66784/#review202004 --- On April 26, 2018, 12:57 p.m., David Radley wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/66784/ > --- > > (Updated April 26, 2018, 12:57 p.m.) > > > Review request for atlas, Madhan Neethiraj and Mandy Chessell. > > > Bugs: ATLAS2604 > https://issues.apache.org/jira/browse/ATLAS2604 > > > Repository: atlas > > > Description > --- > > ATLAS2604 Minor fixups to open metadata archive types to avoid duplicate > attributes due to relationship end names. > > > Diffs > - > > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveBuilder.java > 5902c4202 > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveHelper.java > 42d2d8746 > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java > faab96cac > omrs/src/main/java/org/apache/atlas/omrs/ffdc/OMRSErrorCode.java 351c910e3 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/66784/diff/2/ > > > Testing > --- > > Ran junit that failed without the patch applied. I ran this in Intellij using > the Maven view to run the test phase on the OMRS module. This successfully > ran the test. > > > Thanks, > > David Radley > >
Re: Review Request 66784: ATLAS2604 Minor fixups to open metadata archive types
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/66784/#review202005 --- omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveBuilder.java Line 705 (original), 761 (patched) <https://reviews.apache.org/r/66784/#comment283666> This is a good addition - Mandy Chessell On April 26, 2018, 12:57 p.m., David Radley wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/66784/ > --- > > (Updated April 26, 2018, 12:57 p.m.) > > > Review request for atlas, Madhan Neethiraj and Mandy Chessell. > > > Bugs: ATLAS2604 > https://issues.apache.org/jira/browse/ATLAS2604 > > > Repository: atlas > > > Description > --- > > ATLAS2604 Minor fixups to open metadata archive types to avoid duplicate > attributes due to relationship end names. > > > Diffs > - > > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveBuilder.java > 5902c4202 > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveHelper.java > 42d2d8746 > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java > faab96cac > omrs/src/main/java/org/apache/atlas/omrs/ffdc/OMRSErrorCode.java 351c910e3 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/66784/diff/2/ > > > Testing > --- > > Ran junit that failed without the patch applied. I ran this in Intellij using > the Maven view to run the test phase on the OMRS module. This successfully > ran the test. > > > Thanks, > > David Radley > >
Re: Review Request 66784: ATLAS2604 Minor fixups to open metadata archive types
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/66784/#review202004 --- omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveBuilder.java Lines 66 (patched) <https://reviews.apache.org/r/66784/#comment283664> Please use the same comment style and the rest of the code omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveBuilder.java Lines 563 (patched) <https://reviews.apache.org/r/66784/#comment283665> Please use code layout consistent with the rest of file. - Mandy Chessell On April 26, 2018, 12:57 p.m., David Radley wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/66784/ > --- > > (Updated April 26, 2018, 12:57 p.m.) > > > Review request for atlas, Madhan Neethiraj and Mandy Chessell. > > > Bugs: ATLAS2604 > https://issues.apache.org/jira/browse/ATLAS2604 > > > Repository: atlas > > > Description > --- > > ATLAS2604 Minor fixups to open metadata archive types to avoid duplicate > attributes due to relationship end names. > > > Diffs > - > > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveBuilder.java > 5902c4202 > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/OMRSArchiveHelper.java > 42d2d8746 > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java > faab96cac > omrs/src/main/java/org/apache/atlas/omrs/ffdc/OMRSErrorCode.java 351c910e3 > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > PRE-CREATION > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/66784/diff/2/ > > > Testing > --- > > Ran junit that failed without the patch applied. I ran this in Intellij using > the Maven view to run the test phase on the OMRS module. This successfully > ran the test. > > > Thanks, > > David Radley > >
Re: Review Request 66784: ATLAS2604 Minor fixups to open metadata archive types
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/66784/#review201902 --- omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java Lines 35 (patched) <https://reviews.apache.org/r/66784/#comment283522> This code is not in the most effective place. It only ensures the open metadata types do not have duplicate attributes for an entity and only after the archive is built. It should be in the archive builder ensuring that no archives can be built with duplicate names. It should also be in the repository content manager validating that types from different archives do not cause an entity to have duplicate properties. This test code should be removed and reformatted to run in the main OMRS code. - Mandy Chessell On April 24, 2018, 8:48 p.m., David Radley wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/66784/ > --- > > (Updated April 24, 2018, 8:48 p.m.) > > > Review request for atlas, Madhan Neethiraj and Mandy Chessell. > > > Bugs: ATLAS2604 > https://issues.apache.org/jira/browse/ATLAS2604 > > > Repository: atlas > > > Description > --- > > ATLAS2604 Minor fixups to open metadata archive types to avoid duplicate > attributes due to relationship end names. > > > Diffs > - > > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java > faab96cac > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/66784/diff/1/ > > > Testing > --- > > Ran junit that failed without the patch applied. I ran this in Intellij using > the Maven view to run the test phase on the OMRS module. This successfully > ran the test. > > > Thanks, > > David Radley > >
Re: Dependent component versions for 1.0 release
Dear all, I think we should move to the latest level of the spring framework/boot All the best Mandy ___ Mandy Chessell CBE FREng CEng FBCS IBM Distinguished Engineer Master Inventor Member of the IBM Academy of Technology Visiting Professor, Department of Computer Science, University of Sheffield Email: mandy_chess...@uk.ibm.com LinkedIn: http://www.linkedin.com/pub/mandy-chessell/22/897/a49 Assistant: Janet Brooks - jsbrook...@uk.ibm.com From: Nigel Jones <nigel.l.jo...@gmail.com> To: <dev@atlas.apache.org> Date: 24/04/2018 17:01 Subject:Re: Dependent component versions for 1.0 release On 2018/04/24 13:04:59, Graham Wallis <graham_wal...@uk.ibm.com> wrote: > Do we need to include anything about development versions including Maven, > Java, etc? I think it would be worth mentioning in readme/ wiki build, though now we have the maven-enforcer in place we know the min prereq java is java 8 update 151 & maven 3.5.0 which aren't far off (latest 172 - jdk 11/18.10 is next lts and could be 'interesting', and maven 3.5.3) Post-release I think there's a few other questions about specific component versions (and pom standardization where it makes sense), but I wouldn't change anything close to release
Re: Review Request 66784: ATLAS2604 Minor fixups to open metadata archive types
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/66784/#review201859 --- omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java Line 10962 (original), 10962 (patched) <https://reviews.apache.org/r/66784/#comment283470> attributesTypedBy is clearer omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java Line 10963 (original), 10963 (patched) <https://reviews.apache.org/r/66784/#comment283471> The description should be a sentence in English. This means it starts with a captial letter and does not include camel-case words. I would keep the description the same. - Mandy Chessell On April 24, 2018, 8:48 p.m., David Radley wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/66784/ > --- > > (Updated April 24, 2018, 8:48 p.m.) > > > Review request for atlas, Madhan Neethiraj and Mandy Chessell. > > > Bugs: ATLAS2604 > https://issues.apache.org/jira/browse/ATLAS2604 > > > Repository: atlas > > > Description > --- > > ATLAS2604 Minor fixups to open metadata archive types to avoid duplicate > attributes due to relationship end names. > > > Diffs > - > > > omrs/src/main/java/org/apache/atlas/omrs/archivemanager/opentypes/OpenMetadataTypesArchive.java > faab96cac > > omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/66784/diff/1/ > > > Testing > --- > > Ran junit that failed without the patch applied. I ran this in Intellij using > the Maven view to run the test phase on the OMRS module. This successfully > ran the test. > > > Thanks, > > David Radley > >
[jira] [Updated] (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 updated ATLAS-2585: -- Attachment: 0002-ATLAS-2585-Fix-up-validation-of-TypDef-GUIDs.patch > 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 > 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)
