drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Altekruse (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-3500) Provide additional information while registering storage plugin optimizer rules
Date Thu, 23 Jul 2015 23:21:04 GMT

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

Jason Altekruse commented on DRILL-3500:

One thing I would add to point 2. Many of these options indicate if rules should be turned
on or not, however others provide configurable behaviors for particular rules. Writer of particular
rules should probably not have to look through the list of all rules that can be turned off,
but they should have access to these other options that may impact how they (the individual
rules) operate.

> Provide additional information while registering storage plugin optimizer rules
> -------------------------------------------------------------------------------
>                 Key: DRILL-3500
>                 URL: https://issues.apache.org/jira/browse/DRILL-3500
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Mehant Baid
>            Assignee: Mehant Baid
>             Fix For: 1.2.0
> Currently all the optimizer rules internal to Drill have access to QueryContext. This
is used by a few rules like PruneScanRule which invoke the interpreter to perform partition
pruning. However the rules that belong to specific storage plugins don't have access to this
information. This JIRA aims to do the following
> 1. Add a new interface OptimizerRulesContext that will be implemented by QueryContext.
It will contain all the information needed by the rules. This context will be passed to the
storage plugin method while getting the optimizer rules specific to that storage plugin.
> 2. Restrict existing internal rules to only accept OptimizerRulesContext instead of QueryContext
so information in QueryContext has better encapsulation.

This message was sent by Atlassian JIRA

View raw message