hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Steinbach (JIRA)" <>
Subject [jira] Updated: (HIVE-924) Extract LogicalPlan and PhysicalPlan classes from SemanticAnalysis class
Date Fri, 20 Nov 2009 01:26:39 GMT


Carl Steinbach updated HIVE-924:

    Attachment: HIVE-924.patch

- Split SemanticAnalyzer into DMLSemanticAnalyzer, LogicalPlan, LogicalPlanGenerator, PhysicalPlan,
and PhysicalPlanGenerator classes.

- Removed ParseContext class.

- Refactored GenMRProcContext.

- Fixed several cases of classes that were exposing their internal mutable state.


- Consolidate everything under a QueryCompiler class.

> Extract LogicalPlan and PhysicalPlan classes from SemanticAnalysis class
> ------------------------------------------------------------------------
>                 Key: HIVE-924
>                 URL:
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>            Reporter: 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.

View raw message