[
https://issues.apache.org/jira/browse/KYLIN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744605#comment-16744605
]
ASF subversion and git services commented on KYLIN-3552:
--------------------------------------------------------
Commit ed5d565f02f40c27197e603124a402ce597fd9d9 in kylin's branch
refs/heads/document from edouardzyc
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=ed5d565 ]
KYLIN-3552 add doc and blog
> Data Source SDK to ingest data from different JDBC sources
> ----------------------------------------------------------
>
> Key: KYLIN-3552
> URL: https://issues.apache.org/jira/browse/KYLIN-3552
> 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 different.
> 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
(v7.6.3#76005)
