You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Tariq (JIRA)" <ji...@apache.org> on 2016/09/03 07:52:20 UTC
[jira] [Updated] (ATLAS-1157) Stroing metadata in Apache MetaModel
/ Exchange metadata with Apache Atlas
[ https://issues.apache.org/jira/browse/ATLAS-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tariq updated ATLAS-1157:
-------------------------
Summary: Stroing metadata in Apache MetaModel / Exchange metadata with Apache Atlas (was: feature)
> Stroing metadata in Apache MetaModel / Exchange metadata with Apache Atlas
> --------------------------------------------------------------------------
>
> Key: ATLAS-1157
> URL: https://issues.apache.org/jira/browse/ATLAS-1157
> Project: Atlas
> 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)