[
https://issues.apache.org/jira/browse/CALCITE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16780940#comment-16780940
]
Julian Hyde commented on CALCITE-2815:
--------------------------------------
[~asereda] commented on the PR, "If we go JNDI route (see [dev
list|https://lists.apache.org/thread.html/8c255842f5c8885d772c27546d5fe12dd4e2f2d124ac6ad221e47519@%3Cdev.calcite.apache.org%3E])
I would like to review this PR once again"
Yes, absolutely.
You and I seem to be on opposite sides of the debate. I advocate for only
primitive values (or lists/maps therefore) whereas you would like to pass
objects. Do you think we can reach consensus?
> 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
> 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)
