[ https://issues.apache.org/jira/browse/DRILL-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635622#comment-14635622 ]
ASF GitHub Bot commented on DRILL-3500: --------------------------------------- Github user jaltekruse commented on the pull request: https://github.com/apache/drill/pull/94#issuecomment-123445562 +1 > 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: Jason Altekruse > 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)