[CALCITE-1171] Limit N on JdbcSchema pushdown doesn't seem to work

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Fix Version/s: 1.16.0
• Component/s: avatica, core
• Assignee: Julian Hyde
• Reporter: Dan Di Spaltro
• Created: 26/Mar/16 02:25
• Updated: 29/Apr/19 17:14
• Resolved: 26/Jan/18 02:06

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?

Issue Links

• duplicates: CALCITE-1265 In JDBC adapter, push OFFSET and FETCH to data source
• relates to: CALCITE-1265 In JDBC adapter, push OFFSET and FETCH to data source