[
https://issues.apache.org/jira/browse/CALCITE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358279#comment-15358279
]
Julian Hyde edited comment on CALCITE-1304 at 7/1/16 4:52 PM:
--------------------------------------------------------------
If I'm understanding this correctly, the idea is that there would be a separate
MetaModel adapter in Calcite. In this case the adapter would need to convert
the query into the MetaModel query API. MetaModel in turn will need to
construct native calls to the underlying datastore. I can't imagine there won't
be _some_ loss of efficiency here, although hopefully fairly negligible.
was (Author: michaelmior):
If I'm understanding this correctly, the idea is that there would be a separate
Metamodel adapter in Calcite. In this case the adapter would need to convert
the query into the Metamodel query API. Metamodel in turn will need to
construct native calls to the underlying datastore. I can't imagine there won't
be _some_ loss of efficiency here, although hopefully fairly negligible.
> Add wrapper for Apache MetaModel adapters
> -----------------------------------------
>
> Key: CALCITE-1304
> URL: https://issues.apache.org/jira/browse/CALCITE-1304
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> Apache MetaModel has adapters for a lot of data sources. It would be great if
> those adapters could be re-used as Calcite adapters (and potentially Drill
> adapters also). I was speaking to [~kaspersor] (MetaModel PMC member) today
> and he likes the idea.
> I don't know whether there would be any loss of efficiency going through a
> wrapper, but I suspect not.
> Note: MetaModel uses the spelling "adaptor" but let's continue to spell the
> word "adapter" in Calcite.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
