[
https://issues.apache.org/jira/browse/HIVE-22781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17030288#comment-17030288
]
Hive QA commented on HIVE-22781:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12992617/HIVE-22781.02.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/20466/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/20466/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-20466/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12992617/HIVE-22781.02.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12992617 - 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
>
>
> 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)
