[
https://issues.apache.org/jira/browse/CALCITE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794418#comment-16794418
]
Julian Hyde commented on CALCITE-2815:
--------------------------------------
Having non-serializable objects in the constructor of the Schema but not in the
SchemaFactory seems like a compromise I could live with. As long as the
SchemaFactory actually works.
For the record, I disagree that having a "back door" such as ThreadLocal or
using a directory service is necessarily more complex. The main functionality
is in terms of simple, serializable types, and that makes life easier for most
users. The back door is available for the people who need it.
> 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)
