[jira] [Commented] (PHOENIX-2300) Support the use of secondary indexes in Drill

["Julian Hyde (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PHOENIX-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940401#comment-14940401 ] 

Julian Hyde commented on PHOENIX-2300:
--------------------------------------

Phoenix introduces indexes into the plan via a planning step that models indexes as a kind of materialized views. We need to package up Phoenix's planning process into a series of steps that Drill can call, and this would be one of the steps.

Calcite has an abstraction called [Program|http://calcite.incubator.apache.org/apidocs/org/apache/calcite/tools/Program.html] that is basically a step in a multi-phase planning process. I think Drill should extend its storage plugin SPI and allow plugins to declare programs to be run at various points in the planning process. Drill would define multiple phases analogous to how Maven defines phases 'generate-sources', 'compile', 'test' etc.

> Support the use of secondary indexes in Drill
> ---------------------------------------------
>
>                 Key: PHOENIX-2300
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2300
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>              Labels: drill
>
> In the Phoenix/Calcite world, secondary indexes are modeled as materialized views. We need to figure out in the Phoenix/Drill world how to get Drill to use materialized views.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)