[
https://issues.apache.org/jira/browse/CALCITE-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792053#comment-16792053
]
Andrei Sereda commented on CALCITE-2815:
----------------------------------------
{quote}But the interface to the user is simple values. ...
If they can do it, why can't we?
{quote}
To your question why {{URL / File / Path / Properties}} are generally not
sufficient.
Let's say you access a service {{[http://acme.com|http://acme.com/]}} that one
day requires [JWT token|https://jwt.io/] for security and permission reasons.
Since that token expires, each request potentially needs different token (in
HTTP headers).
To generate JWT token you need to access third party service. Each user
generates token differently (some use kerberos some [secure
vault|https://www.vaultproject.io/]). It will be very hard and cumbersome to
encode that logic in JSON (for every use-case) Lowest common denominator seems
to be dependency on {{Supplier<String>}} (provided by user) which is a complex
object.
> 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)
