[
https://issues.apache.org/jira/browse/CALCITE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360725#comment-15360725
]
Kasper Sørensen commented on CALCITE-1304:
------------------------------------------
I have done a short research just to see what kind of struggles we will face
when applying the Calcite SPI to MetaModel. I've raised METAMODEL-1099 because
currently the MetaModel API is pretty much programmatically driven and it seems
the Calcite API is driven by properties/JSON when instantiating the schemas and
such. We've done that before for our Spring module, but that effort should be
made reusable also for Calcite.
On the spelling, don't worry we have little or no convention so I am happy to
say adapter :) Sometimes I might say "connector", "MetaModel module" or
"DataContext implementation" regarding the same.
> 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)
