You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Maryann Xue (JIRA)" <ji...@apache.org> on 2015/03/28 04:23:52 UTC
[jira] [Created] (PHOENIX-1784) Port existing Phoenix optimizations
to Calcite integration
Maryann Xue created PHOENIX-1784:
------------------------------------
Summary: Port existing Phoenix optimizations to Calcite integration
Key: PHOENIX-1784
URL: https://issues.apache.org/jira/browse/PHOENIX-1784
Project: Phoenix
Issue Type: Task
Reporter: Maryann Xue
A lot of optimizations are already included in Calcite default rules, but there are still a few Phoenix-specific high-level optimizations that we need to implement as rules and make sure they are reflected in the tree's cost.
A simple example can be PhoenixFilterTableScanMergeRule, which pushes a Filter operator into a PhoenixTableScan so that the filter can be converted to an HBase Filter or more optimally a SkipScanFilter or even a point look-up.
Please refer to sub-tasks for individual optimizations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)