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

[jira] [Commented] (QUICKSTEP-76) LIP Filter Does not Work in the distributed version

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

ASF GitHub Bot commented on QUICKSTEP-76:
-----------------------------------------

Github user jianqiao commented on the issue:

    https://github.com/apache/incubator-quickstep/pull/249
  
    LGTM! Merging.


> LIP Filter Does not Work in the distributed version
> ---------------------------------------------------
>
>                 Key: QUICKSTEP-76
>                 URL: https://issues.apache.org/jira/browse/QUICKSTEP-76
>             Project: Apache Quickstep
>          Issue Type: Bug
>          Components: Distributed Query Execution
>            Reporter: Zuyu Zhang
>         Attachments: test.sql
>
>
> In the distributed version where Ensemble are consist of multiple Shiftboss, a query w/ non-partitioned hash join whose probe relation is non-stored may get incorrect result, because a SelectWorkOrder on a block from the probe relation may be scheduled on a Shiftboss other than the one that has executed BuildHashJoin. Thus the LIP filter in the SelectWorkOrder has not initialized by BuildHashJoin, and would incorrectly produce no outputs.
> There is a quick fix to schedule SelectWorkOrder on the probe relation only on the Shiftboss that has executed BuildHashJoin.
> As for a partitioned hash join, there are two cases. If the stored probe relation does not need repartition, no changes needed (as no SelectWorkOrder needed). Otherwise, each SelectWorkOrder should be scheduled on the Shiftboss that has executed BuildHashWorkOrder with the same partition id.



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