You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Hongze Zhang (JIRA)" <ji...@apache.org> on 2019/04/29 17:15:08 UTC
[jira] [Closed] (CALCITE-1171) Limit N on JdbcSchema pushdown
doesn't seem to work
[ https://issues.apache.org/jira/browse/CALCITE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hongze Zhang closed CALCITE-1171.
---------------------------------
The issue was resolved but not closed in the given fix version. Closing now.
> Limit N on JdbcSchema pushdown doesn't seem to work
> ---------------------------------------------------
>
> Key: CALCITE-1171
> URL: https://issues.apache.org/jira/browse/CALCITE-1171
> Project: Calcite
> Issue Type: Bug
> Components: avatica, core
> Reporter: Dan Di Spaltro
> Assignee: Julian Hyde
> Priority: Minor
> Fix For: 1.16.0
>
>
> I am exploring the code and came across this situation which I can't decide if it's intended or not. Programatically, I create a JdbcSchema on a Calcite driver connection, and then execute a single query. I have a breakpoint in the postgres driver, because I wanted to see how the queries end up before they're sent to PG. So I started simple, select * from X id = 'foo', which works great. Then I did a select * from X limit 10. And I noticed I was getting the correct number of rows back, but when sending to PG it would just send select * from X and then looks like the enumerable code (linq4j) would then chop off the results. Is there a way to change this behavior, or is this intended?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)