[
https://issues.apache.org/jira/browse/PHOENIX-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983376#comment-13983376
]
Hudson commented on PHOENIX-951:
--------------------------------
SUCCESS: Integrated in Phoenix #220 (See
[https://builds.apache.org/job/Phoenix/220/])
PHOENIX-951 Don't push LIMIT as PageFilter for joins (maryannxue: rev
2c97b7b6483973d13860980be854fb9ad0cf774f)
* phoenix-core/src/main/java/org/apache/phoenix/execute/ScanPlan.java
* phoenix-core/src/main/java/org/apache/phoenix/join/HashJoinInfo.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/HashJoinRegionScanner.java
* phoenix-core/src/main/java/org/apache/phoenix/execute/HashJoinPlan.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/HashJoinIT.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/JoinCompiler.java
> 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
>
> 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)
