[
https://issues.apache.org/jira/browse/CALCITE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504268#comment-14504268
]
Julian Hyde commented on CALCITE-661:
-------------------------------------
To fetch rows on the client side you need to (a) fetch over an RPC, then the
server needs to decode the JSON fetch request and somehow get rows on the
server side by (b) call into the JDBC driver of the source system or (c) asking
Calcite. So, the full request requires either (a) + (b) or (a) + (c).
(a) is RemoteMeta.fetch; (b) is JdbcMeta.fetch, and (c) is
CalciteMetaImpl.fetch.
> Remote fetch in Calcite JDBC driver
> -----------------------------------
>
> Key: CALCITE-661
> URL: https://issues.apache.org/jira/browse/CALCITE-661
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.1.0-incubating
> Reporter: YeongWei
> Assignee: Julian Hyde
> Fix For: 1.3.0-incubating
>
> Attachments: CALCITE-661-test.patch, CALCITE-661.patch
>
>
> During a CalciteMetaImpl#prepare execute from preparedStatement, the
> Signature Object created from parseQuery method is not being set into the
> created StatementHandle Object
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
