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 2014/05/02 05:55:14 UTC

[jira] [Resolved] (PHOENIX-951) Don't push LIMIT as PageFilter for joins

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

James Taylor resolved PHOENIX-951.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 4.1
                   3.1
                   5.0.0

Fixed by [~maryannxue]. Nice work!

> Don't push LIMIT as PageFilter for joins
> ----------------------------------------
>
>                 Key: PHOENIX-951
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-951
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 3.0.0, 4.0.0
>            Reporter: James Taylor
>            Assignee: Maryann Xue
>            Priority: Minor
>             Fix For: 5.0.0, 3.1, 4.1
>
>
> When a join has a limit, you can't push the limit through a PageFilter since you might not get a match when you join the LHS to the RHS. I think ideally you'd want to push the LIMIT to the ScanRegionObserver (or GroupedAggregateRegionObserver) and then stop the inner scan when the limit is reached. There's a similar optimize for a GROUP BY that has a LIMIT with no ORDER BY.



--
This message was sent by Atlassian JIRA
(v6.2#6252)