[
https://issues.apache.org/jira/browse/DRILL-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628780#comment-14628780
]
ASF GitHub Bot commented on DRILL-3500:
---------------------------------------
GitHub user mehant opened a pull request:
https://github.com/apache/drill/pull/94
DRILL-3500: Add OptimizerRulesContext which exposes information neede…
…d by storage plugin specific optimizer rules
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mehant/drill hive_pp_1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/94.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #94
----
commit 5969dc7f45fe750e0c87f4a157e1bf798866f210
Author: Mehant Baid <[email protected]>
Date: 2015-07-15T21:30:16Z
DRILL-3500: Add OptimizerRulesContext which exposes information needed by
storage plugin specific optimizer rules
----
> 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
(v6.3.4#6332)
