You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Carl Steinbach (JIRA)" <ji...@apache.org> on 2010/01/27 21:19:34 UTC

[jira] Assigned: (HIVE-924) Extract LogicalPlan and PhysicalPlan classes from SemanticAnalysis class

     [ https://issues.apache.org/jira/browse/HIVE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carl Steinbach reassigned HIVE-924:
-----------------------------------

    Assignee: Carl Steinbach

> Extract LogicalPlan and PhysicalPlan classes from SemanticAnalysis class
> ------------------------------------------------------------------------
>
>                 Key: HIVE-924
>                 URL: https://issues.apache.org/jira/browse/HIVE-924
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>            Reporter: Carl Steinbach
>            Assignee: Carl Steinbach
>         Attachments: HIVE-924.patch
>
>
> Currently the SemanticAnalyzer class handles semantic analysis, as well as logical plan generation and physical plan generation. I think it would be beneficial to extract distinct LogicalPlan and PhysicalPlan classes from the SemanticAnalyzer, and have the query processing phase be coordinated by a QueryCompiler class that would be responsible for triggering the parsing, semantic analysis, logical plan generation, optimization, and physical plan generation phases. This proposed reorganization of components would help to isolate the state of each phase, and would also bring the source into closer alignment with the description of the query compiler in the Hive design document on the wiki.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.