[
https://issues.apache.org/jira/browse/PHOENIX-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated PHOENIX-1784:
---------------------------------
Labels: calcite (was: )
> Port existing Phoenix optimizations to Phoenix/Calcite integration
> ------------------------------------------------------------------
>
> Key: PHOENIX-1784
> URL: https://issues.apache.org/jira/browse/PHOENIX-1784
> Project: Phoenix
> Issue Type: Task
> Reporter: Maryann Xue
> Labels: calcite
> Original Estimate: 2,160h
> Remaining Estimate: 2,160h
>
> 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)
