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

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/05/12 20:53:12 UTC

[jira] [Updated] (PHOENIX-2818) Optimize ORDERED group by

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

James Taylor updated PHOENIX-2818:
----------------------------------
    Attachment: PHOENIX-2818.patch

This is the one, [~tdsilva]. Please review.

> Optimize ORDERED group by
> -------------------------
>
>                 Key: PHOENIX-2818
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2818
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>         Attachments: PHOENIX-2818.patch
>
>
> We currently check each row against the previous row when we execute a GROUP BY in row key order. We only need to check the previous row at the boundary while it's the same as the first row(s) in the next scan, kind of a hybrid between the ConcatResultIterator and the GroupedResultIterator.



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