Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-1171

Limit N on JdbcSchema pushdown doesn't seem to work

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: 1.16.0
    • Component/s: avatica, core
    • Labels:
      None

      Description

      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?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                julianhyde Julian Hyde
                Reporter:
                dispalt Dan Di Spaltro
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: