[
https://issues.apache.org/jira/browse/DRILL-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Nadeau updated DRILL-698:
---------------------------------
Fix Version/s: (was: 1.0.0-BETA1)
Future
> Register scan-specific optimization rules using register() in RelNode
> interface.
> --------------------------------------------------------------------------------
>
> Key: DRILL-698
> URL: https://issues.apache.org/jira/browse/DRILL-698
> Project: Apache Drill
> Issue Type: Improvement
> Components: Query Planning & Optimization
> Reporter: Jinfeng Ni
> Assignee: Jinfeng Ni
> Priority: Minor
> Fix For: Future
>
>
> Currently, drill will get all the storage-engine-specific rules in
> StoragePluginRegistry, and register all the rules (HBase, Hive, etc) with the
> optimizer planner. This means even the query only refers a Hive table, the
> optimizer may still have rule for other storage-engine.
> In stead, we should register the storage-engine-specific rules using
> interface RelNode's register() method, when we know a scan is for one
> particular storage-engine. This will avoid the issue that optimizer has more
> than necessary rules in its rule queue.
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
