[ 
https://issues.apache.org/jira/browse/HIVE-22835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031299#comment-17031299
 ] 

Hive QA commented on HIVE-22835:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12992703/HIVE-22835.01.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 17965 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/20488/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/20488/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-20488/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12992703 - PreCommit-HIVE-Build

> 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)

Reply via email to