You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@griffin.apache.org by "Chitral Verma (Jira)" <ji...@apache.org> on 2020/08/15 07:51:00 UTC

[jira] [Assigned] (GRIFFIN-302) Standardize Data Connectors

     [ https://issues.apache.org/jira/browse/GRIFFIN-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chitral Verma reassigned GRIFFIN-302:
-------------------------------------

    Assignee: Chitral Verma

> Standardize Data Connectors
> ---------------------------
>
>                 Key: GRIFFIN-302
>                 URL: https://issues.apache.org/jira/browse/GRIFFIN-302
>             Project: Griffin
>          Issue Type: Improvement
>            Reporter: Chitral Verma
>            Assignee: Chitral Verma
>            Priority: Major
>              Labels: features, improvement
>
> Currently, the Data Connectors have a hierarchy - Batch and Streaming. BatchDataConnector and StreamingDataConnector are further extended in individual classes for each distinct data source (example: MySql, Avro, ElasticSearch etc). This hierarchy has lead to a lot of duplicated code across individual Batch Sources and DataConnectors in general.
> I propose here a different hierarchy based on type of DataSource (example FileBased: see [GRIFFIN-297|https://issues.apache.org/jira/browse/GRIFFIN-297], JDBCBased etc). Additionally, we can have certain user facing abstractions, which the end users can extend to implement their own DataConnectors and make them available via `spark.jars` property.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)