You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/05/05 00:10:12 UTC

[jira] [Commented] (DRILL-4657) Rank() will return wrong results if a frame of data is too big (more than 2 batches)

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

ASF GitHub Bot commented on DRILL-4657:
---------------------------------------

GitHub user adeneche opened a pull request:

    https://github.com/apache/drill/pull/499

    DRILL-4657: Rank() will return wrong results if a frame of data is to…

    …o big (more than 2 batches)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/adeneche/incubator-drill DRILL-4657

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/499.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #499
    
----
commit bd8b8edfa6f9b919c29edc52c1ca2a2d147372ba
Author: adeneche <ad...@gmail.com>
Date:   2016-05-04T19:08:36Z

    DRILL-4657: Rank() will return wrong results if a frame of data is too big (more than 2 batches)

----


> Rank() will return wrong results if a frame of data is too big (more than 2 batches)
> ------------------------------------------------------------------------------------
>
>                 Key: DRILL-4657
>                 URL: https://issues.apache.org/jira/browse/DRILL-4657
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Relational Operators
>    Affects Versions: 1.3.0
>            Reporter: Deneche A. Hakim
>            Assignee: Deneche A. Hakim
>            Priority: Critical
>             Fix For: 1.7.0
>
>
> When you run a query with RANK, and one particular frame is too long to fit in 2 batches of data, you will get wrong result.
> I was able to reproduce the issue in a unit test, thanks to the fact that we can control the size of the batches processed by the window operator. I will post a fix soon along with the unit test



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)