[
https://issues.apache.org/jira/browse/ATLAS-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mandy Chessell updated ATLAS-1095:
----------------------------------
Summary: Open connector framework (was: Define Requirements: Data and
metadata association via open connector framework)
> Open connector framework
> ------------------------
>
> Key: ATLAS-1095
> URL: https://issues.apache.org/jira/browse/ATLAS-1095
> Project: Atlas
> Issue Type: New Feature
> Affects Versions: 0.8-incubating
> Reporter: Stephanie Hazlewood
> Assignee: Mandy Chessell
> Labels: VirtualDataConnector
>
> Atlas is intended to provide a common approach to data governance and lineage
> across all systems and data within an organization. Today Atlas provides
> access to metadata. A connector provides access to a data source. As
> connectors are the proxy of all data, they can also be explicit providers of
> metadata. An open connector framework is being proposed to provide access
> to both data and the metadata Atlas provides together – the framework being
> the point at which data and metadata can be associated. This will help to
> better the exchange of information between platforms. It also offers new
> opportunities for the consistent enforcement of the governance policies and
> rules (e.g., rules of visibility). Source connector/connection metadata
> provides the nucleus around which all other metadata describing the data
> builds.
> Introducing this framework:
> Provides the necessary broker capabilities for normalized access to (finding
> and instantiating) a connector instance.
> Provides extension API supporting both partial and incremental adoption of
> the framework by existing connector provider runtimes allowing connector
> providers/contributors to adapt what they have vs re-write.
> Introducing the notion of metadata-enabled open connectors:
> Provides an API for the normalized access to the metadata describing a
> connector (asset type, connection type)
> Provides base APIs for creating new connectors of different types and
> interaction styles.
> The key personas using the framework are the tool developers and developers.
> As a connector developer, I want to create a new connector (or register an
> existing connector) to plug into the framework so that I can retrieve and
> manage metadata about what the source provides and ensure data used from that
> source has governance policies (e.g., rules of visibility) consistently
> configured and enforced.
> The tool developer uses a connector available through the framework to
> implement an application. Leveraging the APIs of the connector framework
> applications will be able to find relevant sources systems and connect to
> them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
