[
https://issues.apache.org/jira/browse/DRILL-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955810#comment-14955810
]
Jacques Nadeau commented on DRILL-3929:
---------------------------------------
Phoenix simply treats the alternative plan as a materialized view. Basically
you register with calcite an equivalence relationship between some SQL and a
base table. Then both are costed. I think that is a much cleaner approach
instead of trying to fit the behavior into a rule. In this case, the covering
or not covering scan would be with join with the base table would be an
alternative. From there, all the standard rules can be used to prune columns,
etc.
As a side point on this, I also think we need to fix the HBase pushdown so it
behaves more like the JDBC plugin, using a new convention for supported
operations instead of trying to determine all multinode patterns (scan >
project > filter, scan > filter > project, scan > project, scan > filter, etc).
> Support the ability to query database tables using external indices
> ------------------------------------------------------------------------------
>
> Key: DRILL-3929
> URL: https://issues.apache.org/jira/browse/DRILL-3929
> Project: Apache Drill
> Issue Type: New Feature
> Components: Execution - Relational Operators, Query Planning &
> Optimization
> Reporter: Aman Sinha
> Assignee: Aman Sinha
>
> This is a placeholder for adding support in Drill to query database tables
> using external indices. I will add more details about the use case and a
> preliminary design proposal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
