You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metamodel.apache.org by "Kasper Sørensen (JIRA)" <ji...@apache.org> on 2016/09/06 02:58:20 UTC

[jira] [Commented] (METAMODEL-1117) Storing metadata in Apache MetaModel / Exchange metadata with Apache Atlas

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

Kasper Sørensen commented on METAMODEL-1117:
--------------------------------------------

I would suggest starting in small pieces. For example by making a  tool that simply can generate (even just for bootstrapping/quick-start purposes) the type definitions as defined by Atlas: http://atlas.apache.org/TypeSystem.html

This would be a rather simple exercise of traversing a MetaModel DataContext object by going through methods such as

{code}
DataContext.getSchemas()
Schema.getTables()
Table.getXXX() // all the stuff that needs to be stored in the Atlas format
Table.getColumns()
Column.getXXX() // all the stuff that needs to be stored in the Atlas format
{code}

I like the idea by the way... I don't have much (any) experience with Apache Atlas, but if we can demonstrate something like this it could be a great way to bridge the two projects.

> Storing metadata in Apache MetaModel / Exchange metadata with Apache Atlas
> --------------------------------------------------------------------------
>
>                 Key: METAMODEL-1117
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-1117
>             Project: Apache MetaModel
>          Issue Type: Improvement
>            Reporter: Tariq
>
> Apache Atlas provides a metadata repository for storing metadata. It  enable enterprises to effectively and efficiently meet their compliance requirements within Hadoop and allows integration with the whole enterprise data ecosystem.
> Apache MetaModel allows query data using metadata and provides access to different data sources based on metadata. 
> It is missing the metadata catalogue component.  There is no API to store metadata using Apache MetaModel or no option to export metadata from Apache MetaModel to Apache Atlas.
> Providing API support for metadata exchange between Apache MetaModel & Apache Atlas will be a great addition and make both the tools more useful
> Providing an API storing metadata in Apache MetaModel or an API for exchanging the metadata to Apache Atlas will enable the application developers the following benefits: 
> 1) Make changes to metadata(schema) from within the Apache MetaModel.
> 3) Data classification based on metadata
> 2) Maintain a metadata repository within Apache MetaModel
> 4) Centralised auditing of the data
> 5) Browse and search metadata
> 6) Exporting metadata to 3rd party applications.
> Looking forward to feedback on this proposal.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)