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

Bridget Bevens commented on DRILL-6381:
---------------------------------------

Added the following content to the Apache Drill docs:
 created content and posted to https://drill.apache.org/docs/querying-indexes/
with the following supporting pages:
https://drill.apache.org/docs/querying-indexes-introduction/
https://drill.apache.org/docs/queries-that-qualify-for-index-based-query-plans/
https://drill.apache.org/docs/types-of-indexes/
https://drill.apache.org/docs/index-selection/
https://drill.apache.org/docs/designing-indexes-for-your-queries/
https://drill.apache.org/docs/configuring-index-planning/
https://drill.apache.org/docs/verifying-index-use/

Please let me know if I need to make any changes.

Thanks,
Bridget

> 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
>              Labels: doc-complete, ready-to-commit
>             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)

Reply via email to