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

Hive QA commented on HIVE-22781:
--------------------------------



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

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

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

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

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: 12993107 - PreCommit-HIVE-Build

> Add ability to immediately execute a scheduled query
> ----------------------------------------------------
>
>                 Key: HIVE-22781
>                 URL: https://issues.apache.org/jira/browse/HIVE-22781
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>         Attachments: HIVE-22781.01.patch, HIVE-22781.02.patch, 
> HIVE-22781.03.patch, HIVE-22781.04.patch, HIVE-22781.04.patch, 
> HIVE-22781.04.patch, HIVE-22781.05.patch, HIVE-22781.05.patch
>
>
> there are some differences when the system invokes the scheduled query / the 
> user executes it in a shell - forcing the schedule to run might be usefull in 
> developing/debugging schedules
> something like:
> {code}
> alter scheduled query a execute
> {code}



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

Reply via email to