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

Posted to issues@hive.apache.org by "Zoltan Haindrich (Jira)" <ji...@apache.org> on 2020/06/02 16:57:00 UTC

[jira] [Commented] (HIVE-23404) Schedules in the past should be accepted

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

Zoltan Haindrich commented on HIVE-23404:
-----------------------------------------

[~jcamachorodriguez] Could you please take a look?

the "not null" constraint was added by mistake to the derby schema - it was not present for any other database

> Schedules in the past should be accepted
> ----------------------------------------
>
>                 Key: HIVE-23404
>                 URL: https://issues.apache.org/jira/browse/HIVE-23404
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Right now if a schedule in the past is set ; an Exception is thrown.
> However this behaviour can be argued...consider that at some point a schedule is created to run in say every day in 2020's december(but not after it). When the creation happens it's "okay"...but in case we reach 2021 it will be considered invalid..because there is no future execution



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