atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mandy Chessell (JIRA)" <>
Subject [jira] [Updated] (ATLAS-1095) Open connector framework
Date Tue, 09 May 2017 19:59:04 GMT


Mandy Chessell updated ATLAS-1095:
    Attachment: Open Connector Framework - 9th May 2017.doc

This is an initial draft of the Open Connector Framework design - feedback welcome.

> Open connector framework
> ------------------------
>                 Key: ATLAS-1095
>                 URL:
>             Project: Atlas
>          Issue Type: New Feature
>    Affects Versions: 0.8-incubating
>            Reporter: Stephanie Hazlewood
>            Assignee: Mandy Chessell
>              Labels: VirtualDataConnector
>         Attachments: Open Connector Framework - 9th May 2017.doc
> Atlas provides a common approach to metadata management and governance across all systems
and data within an organization.  Today Atlas provides access to metadata.   A connector provides
access to a data source.  As connectors are the proxy of all data, they can also be explicit
providers of metadata.   
> This JIRA proposes an open connector framework to manage connectors that provide access
to both data and the metadata Atlas provides together through a single connector interface.
> This will help data tools to to better the exchange of information between platforms.
It also offers new opportunities for the consistent enforcement of the governance policies
and rules (e.g., rules of visibility).  Source connector/connection metadata provides the
nucleus around which all other metadata describing the data builds.  
> Introducing this framework:
> The Connector Broker is used to 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 APIs for metadata-enabled open connectors:
> Provides an API for the normalized access to the metadata describing a connector (asset
type, connection type).  This is called the Asset OMAS
> 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

View raw message