[
https://issues.apache.org/jira/browse/DRILL-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978820#comment-14978820
]
Aman Sinha commented on DRILL-3929:
-----------------------------------
Discussed the Phoenix integration with Calcite more on the dev list and through
a google hangout. See discussion on Drill dev list:
http://mail-archives.apache.org/mod_mbox/drill-dev/201510.mbox/%3ccajrw0orh+wfa2gfzgbglbrkqk9m6y4_aor5kh_rxhaag0cb...@mail.gmail.com%3e
The approach to use projections and rely on materialized view rewrite in
Calcite is predicated on how exactly does Calcite do the MV matching and
rewrites. There are at least 2 pending JIRAs: CALCITE-772 and CALCITE-773
that are known items that are needed for the phoenix integration.
However, I think even if they are addressed, the basic idea of converting each
index column predicate into a join would not work well for Drill. It will
add substantially to the join planning cost, which is not needed since we can
do the secondary index planning during physical planning stage rather than
logical planning.
> 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)
