[
https://issues.apache.org/jira/browse/CALCITE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789969#comment-16789969
]
Julian Hyde commented on CALCITE-2815:
--------------------------------------
Re File and SplunkSchema. File is simple (immutable, and created from sets of
strings). SplunkSchema I regret.
I know that JNDI is hard to use. Let's drop that.
But consider that the internet, and the web, and file systems all manage to
work using addresses that are strings. Of course there are proxies, directory
services and caches under the covers. But the interface to the user is simple
values.
If they can do it, why can't we? (We can have complex behavior under the
covers, for performance etc.)
ConfigurableSchema looks promising. I gather that you are providing a mechanism
for a Schema instance to serialize itself so that we can create an equivalent
Schema instance on another JVM. But I don't understand how I would use take the
SchemaFactory from one schema and convert it to a SchemaFactory in another VM.
> GeodeSchemaFactory change to pass in clientCache using geode jndi context
> -------------------------------------------------------------------------
>
> Key: CALCITE-2815
> URL: https://issues.apache.org/jira/browse/CALCITE-2815
> Project: Calcite
> Issue Type: Improvement
> Components: geode
> Reporter: Sandeep Chada
> Assignee: Andrei Sereda
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> We need ability to pass clientCache to GeodeSchemaFactory create static
> function. In our application we already have clientCache pre created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
