You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "James Turton (Jira)" <ji...@apache.org> on 2021/12/23 12:55:00 UTC

[jira] [Commented] (DRILL-8090) LIMIT clause is pushed down to an invalid OFFSET-FETCH clause for MS SQL Server

    [ https://issues.apache.org/jira/browse/DRILL-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464535#comment-17464535 ] 

James Turton commented on DRILL-8090:
-------------------------------------

[~cgivre] has theorised that SQL dialect information is being mishandled by Drill in that Drill sets up the storage-jdbc with the correct dialect but by the time the batch reader executes an incorrect dialect has come into effect.  In the context of this ticket, this could mean that Drill is at some point forgetting that the SQL it needs to generate should be T-SQL.

> LIMIT clause is pushed down to an invalid OFFSET-FETCH clause for MS SQL Server 
> --------------------------------------------------------------------------------
>
>                 Key: DRILL-8090
>                 URL: https://issues.apache.org/jira/browse/DRILL-8090
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 1.19.0
>            Reporter: James Turton
>            Priority: Major
>
> In MS SQL Server, ORDER BY is mandatory for using OFFSET and FETCH clauses.  Drill (or Calcite) does not include an ORDER BY clause in the SQL it generates for a LIMIT clause.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)