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

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

                Author: ASF GitHub Bot
            Created on: 07/Oct/19 23:46
            Start Date: 07/Oct/19 23:46
    Worklog Time Spent: 10m 
      Work Description: jcamachor commented on pull request #794: HIVE-21884
URL: https://github.com/apache/hive/pull/794#discussion_r332263137
 
 

 ##########
 File path: 
standalone-metastore/metastore-common/src/main/java/org/apache/hadoop/hive/metastore/conf/MetastoreConf.java
 ##########
 @@ -667,6 +667,19 @@ public static ConfVars getMetaConf(String name) {
     RUNTIME_STATS_MAX_AGE("runtime.stats.max.age", 
"hive.metastore.runtime.stats.max.age", 86400 * 3, TimeUnit.SECONDS,
         "Stat entries which are older than this are removed."),
 
+    SCHEDULED_QUERIES_CRON_SYNTAX("scheduled.queries.cron.syntax", 
"hive.metastore.scheduled.queries.cron.syntax",
+        "QUARTZ", new StringSetValidator("UNIX", "QUARTZ", "CRON4J", "SPRING"),
+        "Defines the format of the schedule expressions to be used in 
scheduled queries."),
+    
SCHEDULED_QUERIES_EXECUTION_PROGRESS_TIMEOUT("scheduled.queries.execution.timeout",
+        "hive.metastore.scheduled.queries.progress.timeout", 120, 
TimeUnit.SECONDS,
+        "If a scheduled query is not making progress for this amount of time 
it will be considered TIMED_OUT"),
+    
SCHEDULED_QUERIES_EXECUTION_MAINT_TASK_FREQUENCY("scheduled.queries.execution.maint.task.frequency",
+        "hive.metastore.scheduled.queries.execution.clean.frequency", 60, 
TimeUnit.SECONDS,
+        "Interval of scheduled query maintenance task. Which removes 
executions above max age; and marks executions as timed out if the condition is 
met"),
+    SCHEDULED_QUERIES_EXECUTION_MAX_AGE("scheduled.queries.execution.max.age",
+        "hive.metastore.scheduled.queries.execution.max.age", 3 * 86400, 
TimeUnit.SECONDS,
 
 Review comment:
   This is three days. I think we should set it longer since sometimes it may 
take more than three days to dig into a problem... We can set this to one month 
by default? If there are too many events, maybe we can have two different 
intervals, one for deleting `EXECUTING` events (more often) and one of the rest 
(less often)?
 
----------------------------------------------------------------
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: 324725)
    Time Spent: 2h 10m  (was: 2h)

> Scheduled query support
> -----------------------
>
>                 Key: HIVE-21884
>                 URL: https://issues.apache.org/jira/browse/HIVE-21884
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-21844.04.patch, HIVE-21844.05.patch, 
> HIVE-21844.06.patch, HIVE-21844.07.patch, HIVE-21844.08.patch, 
> HIVE-21844.09.patch, HIVE-21844.15.patch, HIVE-21844.19.patch, 
> HIVE-21884.01.patch, HIVE-21884.02.patch, HIVE-21884.03.patch, 
> HIVE-21884.09.patch, HIVE-21884.10.patch, HIVE-21884.10.patch, 
> HIVE-21884.11.patch, HIVE-21884.12.patch, HIVE-21884.13.patch, 
> HIVE-21884.14.patch, HIVE-21884.14.patch, HIVE-21884.14.patch, 
> HIVE-21884.16.patch, HIVE-21884.17.patch, HIVE-21884.18.patch, 
> HIVE-21884.20.patch, Scheduled queries2.pdf
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> design document:
> https://docs.google.com/document/d/1mJSFdJi_1cbxJTXC9QvGw2rQ3zzJkNfxOO6b5esmyCE/edit#
> in case the google doc is not reachable:  [^Scheduled queries2.pdf] 



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

Reply via email to