You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Miklos Gergely (Jira)" <ji...@apache.org> on 2020/02/05 17:57:00 UTC

[jira] [Updated] (HIVE-22835) Extract Executor from Driver

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

Miklos Gergely updated HIVE-22835:
----------------------------------
    Attachment: HIVE-22835.01.patch

> Extract Executor from Driver
> ----------------------------
>
>                 Key: HIVE-22835
>                 URL: https://issues.apache.org/jira/browse/HIVE-22835
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Miklos Gergely
>            Assignee: Miklos Gergely
>            Priority: Major
>             Fix For: 4.0.0
>
>         Attachments: HIVE-22835.01.patch
>
>
> The Driver class contains ~600 lines of code responsible for executing the command. That means that from the Query Plan as input the appropriate tasks should be executed. This is a thing done by the execute function, which is ~300 lines long, and also has some sub functions to help this task. All these codes should be put into a separate class, where it can do it's job without getting mixed with the other codes in the Driver.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)