[
https://issues.apache.org/jira/browse/DRILL-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613837#comment-16613837
]
ASF GitHub Bot commented on DRILL-6381:
---------------------------------------
amansinha100 opened a new pull request #1466: DRILL-6381: Add support for index
based planning and execution
URL: https://github.com/apache/drill/pull/1466
- Please see [DRILL-6381](https://issues.apache.org/jira/browse/DRILL-6381)
for a description of the feature. For additional details please see the commit
messages. Wherever appropriate, Javadoc has been provided in the new code.
- This PR contains 5 commits and has contributions from several people who
have been listed as co-authors in individual commits.
- This PR introduces a dependency on MapR 6.0.1 (current apache master is on
v5.2.1) which in turn requires CentOS 7.x
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Add capability to do index based planning and execution
> -------------------------------------------------------
>
> Key: DRILL-6381
> URL: https://issues.apache.org/jira/browse/DRILL-6381
> Project: Apache Drill
> Issue Type: New Feature
> Components: Execution - Relational Operators, Query Planning &
> Optimization
> Reporter: Aman Sinha
> Assignee: Aman Sinha
> Priority: Major
> Fix For: 1.15.0
>
>
> If the underlying data source supports indexes (primary and secondary
> indexes), Drill should leverage those during planning and execution in order
> to improve query performance.
> On the planning side, Drill planner should be enhanced to provide an
> abstraction layer which express the index metadata and statistics. Further,
> a cost-based index selection is needed to decide which index(es) are
> suitable.
> On the execution side, appropriate operator enhancements would be needed to
> handle different categories of indexes such as covering, non-covering
> indexes, taking into consideration the index data may not be co-located with
> the primary table, i.e a global index.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
