calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Di Spaltro (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CALCITE-1171) Limit N on JdbcSchema pushdown doesn't seem to work
Date Sat, 26 Mar 2016 02:26:25 GMT
Dan Di Spaltro created CALCITE-1171:
---------------------------------------

             Summary: 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


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
(v6.3.4#6332)

Mime
View raw message