You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metamodel.apache.org by "David Morales (JIRA)" <ji...@apache.org> on 2014/10/29 17:49:34 UTC
[jira] [Commented] (METAMODEL-52) Expose MetaModel DataContexts
through a JDBC compliant Driver
[ https://issues.apache.org/jira/browse/METAMODEL-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14188556#comment-14188556 ]
David Morales commented on METAMODEL-52:
----------------------------------------
Very interesting topic¡ Presto has already a similar feature, managing catalogs so that you can connect to different data stores.
http://prestodb.io/docs/current/installation/jdbc.html
And it will be quite useful in order to connect metamodel to BI / ETL tools (pentaho?)
> Expose MetaModel DataContexts through a JDBC compliant Driver
> -------------------------------------------------------------
>
> Key: METAMODEL-52
> URL: https://issues.apache.org/jira/browse/METAMODEL-52
> Project: Metamodel
> Issue Type: New Feature
> Reporter: Kasper Sørensen
> Assignee: Kasper Sørensen
> Priority: Minor
>
> Maybe a wild idea, but one that tickles my curiousity: Would it make sense to build a JDBC driver that allows exposing DataContexts as if they are normal relational databases. Since we now have a SQL parser in place and also have a solid metadata API, we should be able to quite easily adapt to the JDBC API.
> Although I don't particularly like the JDBC API, it would make MetaModel very accessible for everyone who already knows JDBC. That way we can immediately offer connectivity to all of our datastores through a wellknown API. (And hopefully over time those users will start being more interested in the native MetaModel API).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)