kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (KYLIN-3552) Data Source SDK to ingest data from different JDBC sources
Date Mon, 05 Nov 2018 02:59:00 GMT


ASF GitHub Bot commented on KYLIN-3552:

asfgit commented on issue #327: KYLIN-3552 add doc and blog
   Can one of the admins verify this patch?

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Data Source SDK to ingest data from different JDBC sources
> ----------------------------------------------------------
>                 Key: KYLIN-3552
>                 URL:
>             Project: Kylin
>          Issue Type: New Feature
>          Components: Query Engine, RDBMS Source
>            Reporter: youcheng.zhang
>            Assignee: youcheng.zhang
>            Priority: Major
>             Fix For: v2.6.0
>         Attachments: test_evidence_datasource.docx
> Kylin already supports JDBC source, but it takes much efforts to develop an implementation
to a new source engine, like supporting metadata sync, cube build and query pushdown. It’s
mainly because the SQL dialects and jdbc implementations between source engines are quite
> We propose to develop a data source sdk, which provides APIs to help developers handle
these dialect differences and easily implement an adaptor for one source engine. With this
SDK, users can achieve followings from a JDBC source:
>  # synchronize metadata and data from jdbc source.
>  # Build cube from jdbc source.
>  # query pushdown to jdbc source engine when cube is unmatched. 
> The SDK will define some interfaces of adaptors. To implement a new source, developers
only need to implement an adaptor for the source.
> To keep compatibly, we will keep the existing JDBC source module, and implement a new
JDBC source module as the caller of the SDK. Besides, we will also provide a pushdown implementation
class as the caller of SDK for pushdown scenarios.

This message was sent by Atlassian JIRA

View raw message