We’d love if JdbcSort could handle fetch and offset (and generate appropriate SQL for its target dialect). In fact we have a JIRA case already: https://issues.apache.org/jira/browse/CALCITE-1265 <https://issues.apache.org/jira/browse/CALCITE-1265>
> On Jun 1, 2017, at 8:33 AM, Muhammad Gelbana <m.gelb...@gmail.com> wrote: > > This line says > <https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/adapter/jdbc/JdbcRules.java#L542> > that offset and fetch isn't supported while this issue > <https://issues.apache.org/jira/browse/CALCITE-1010> suggests otherwise. > > How is this possible ? > > In my case, I want to convert a *LogicalSort* node to a *JdbcSort > <https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/adapter/jdbc/JdbcRules.java#L552>* > node but *JdbcSort* doesn't support SQL limits\offsets. > > So if I need to convert *LogicalSort* nodes to a Jdbc node that supports > limits\offsets, what node should I use ? > > *---------------------* > *Muhammad Gelbana* > http://www.linkedin.com/in/mgelbana
