You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@quickstep.apache.org by "Jianqiao Zhu (JIRA)" <ji...@apache.org> on 2017/03/25 04:51:41 UTC
[jira] [Closed] (QUICKSTEP-69) Query optimization with ExactFilter.
[ https://issues.apache.org/jira/browse/QUICKSTEP-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jianqiao Zhu closed QUICKSTEP-69.
---------------------------------
Resolution: Implemented
The feature has been implemented with PR #172.
> Query optimization with ExactFilter.
> ------------------------------------
>
> Key: QUICKSTEP-69
> URL: https://issues.apache.org/jira/browse/QUICKSTEP-69
> Project: Apache Quickstep
> Issue Type: Improvement
> Components: Query Optimizer, Relational Operators, Utility
> Reporter: Jianqiao Zhu
> Assignee: Jianqiao Zhu
>
> This is a follow-up optimization based on the facility provided by LIPFilters. Note that LIP (lookahead information passing) filter is an optimization that we can inject bloom filters (created somewhere else) into Select/HashJoin/Aggregate operators to pre-filter the input relations.
> This PR strength-reduces HashJoins (including inner/semi/anti joins) into FilterJoins. The semantics of a FilterJoin is simple: if certain conditions are met, we can build a bit vector from the build side and use the bit vector to FILTER the probe side.
> The execution part is slightly more optimized: a FIlterJoin will not always be converted into a SelectOperator plus a LIPFilter as its semantics indicates. Instead, in most situations we can avoid creating the SelectOperator and attach the LIPFilter properly to some downstream operators -- thus avoid unnecessary materialization of intermediate relations.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)