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

ASF GitHub Bot logged work on HIVE-23404:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Jun/20 19:13
            Start Date: 02/Jun/20 19:13
    Worklog Time Spent: 10m 
      Work Description: kgyrtkirk merged pull request #1051:
URL: https://github.com/apache/hive/pull/1051


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 440398)
    Time Spent: 20m  (was: 10m)

> 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
>         Attachments: HIVE-23404.01.patch
>
>          Time Spent: 20m
>  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)

Reply via email to