Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Fri, 21 Jul 2017 17:55:00 +0000 (UTC)
From: "Arina Ielchiieva (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.13030655.1482827967000.304053.1500659700406@Atlassian.JIRA>
In-Reply-To: <JIRA.13030655.1482827967000@Atlassian.JIRA>
References: <JIRA.13030655.1482827967000@Atlassian.JIRA> <JIRA.13030655.1482827967983@jira-lw-us.apache.org>
Subject: [jira] [Updated] (DRILL-5165) wrong results - LIMIT ALL and OFFSET
 clause in same query
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 21 Jul 2017 17:55:06 -0000


     [ https://issues.apache.org/jira/browse/DRILL-5165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arina Ielchiieva updated DRILL-5165:
------------------------------------
    Labels:   (was: ready-to-commit)

> wrong results - LIMIT ALL and OFFSET clause in same query
> ---------------------------------------------------------
>
>                 Key: DRILL-5165
>                 URL: https://issues.apache.org/jira/browse/DRILL-5165
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Query Planning & Optimization
>    Affects Versions: 1.10.0
>            Reporter: Khurram Faraaz
>            Assignee: Chunhui Shi
>            Priority: Critical
>             Fix For: 1.12.0
>
>
> This issue was reported by a user on Drill's user list.
> Drill 1.10.0 commit ID : bbcf4b76
> I tried a similar query on apache Drill 1.10.0 and Drill returns wrong results when compared to Postgres, for a query that uses LIMIT ALL and OFFSET clause in the same query. We need to file a JIRA to track this issue.
> {noformat}
> 0: jdbc:drill:schema=dfs.tmp> select col_int from typeall_l order by 1 limit all offset 10;
> +----------+
> | col_int  |
> +----------+
> +----------+
> No rows selected (0.211 seconds)
> 0: jdbc:drill:schema=dfs.tmp> select col_int from typeall_l order by col_int limit all offset 10;
> +----------+
> | col_int  |
> +----------+
> +----------+
> No rows selected (0.24 seconds)
> {noformat}
> Query => select col_int from typeall_l limit all offset 10;
> Drill 1.10.0 returns 85 rows
> whereas for same query,
> postgres=# select col_int from typeall_l limit all offset 10;
> Postgres 9.3 returns 95 rows, which is the correct expected result.
> Query plan for above query that returns wrong results
> {noformat}
> 0: jdbc:drill:schema=dfs.tmp> explain plan for select col_int from typeall_l limit all offset 10;
> +------+------+
> | text | json |
> +------+------+
> | 00-00    Screen
> 00-01      Project(col_int=[$0])
> 00-02        SelectionVectorRemover
> 00-03          Limit(offset=[10])
> 00-04            Scan(groupscan=[ParquetGroupScan [entries=[ReadEntryWithPath [path=maprfs:///tmp/typeall_l]], selectionRoot=maprfs:/tmp/typeall_l, numFiles=1, usedMetadataFile=false, columns=[`col_int`]]])
> {noformat} 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)