This is an automated email from the ASF dual-hosted git repository.
kirs pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new 45555c2b5d63 Remove wrong document version (#520)
45555c2b5d63 is described below
commit 45555c2b5d63a6f9dde71a6b574aa7c6a93477c6
Author: Calvin Kirs <acm_ch...@yeah.net>
AuthorDate: Mon Apr 8 15:14:18 2024 +0800
Remove wrong document version (#520)
---
.../version-2.0/admin-manual/query-admin/job.md | 169 ---------------------
.../version-2.0/admin-manual/query-admin/job.md | 156 -------------------
versioned_sidebars/version-2.0-sidebars.json | 3 +-
3 files changed, 1 insertion(+), 327 deletions(-)
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/admin-manual/query-admin/job.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/admin-manual/query-admin/job.md
deleted file mode 100644
index 1e7a39c75972..000000000000
---
a/i18n/zh-CN/docusaurus-plugin-content-docs/version-2.0/admin-manual/query-admin/job.md
+++ /dev/null
@@ -1,169 +0,0 @@
----
-{
- "title": "Job 调度",
- "language": "zh-CN"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-
-Doris Job 是根据既定计划运行的任务，用于在特定时间或指定时间间隔触发预定义的操作，从而帮助我们自动执行一些任务。从功能上来讲，它类似于操作系统上的
定时任务（如：Linux 中的 cron、Windows 中的计划任务）。
-
-Job 有两种类型：`ONE_TIME` 和 `RECURRING`。其中 `ONE_TIME` 类型的 Job
会在指定的时间点触发，它主要用于一次性任务，而 `RECURRING` 类型的 Job 会在指定的时间间隔内循环触发，此方式主要用于周期性执行的任务。
`RECURRING` 类型的 Job 可指定开始时间，结束时间，即 `STARTS\ENDS`, 如果不指定开始时间，则默认首次执行时间为当前时间 +
一次调度周期。如果指定结束时间，则 task 执行完成如果达到结束时间（或超过，或下次执行周期会超过结束时间）则更新为 FINISHED 状态，此时不会再产生
Task。
-
-JOB 共 4 种状态（`RUNNING`,`STOPPED`,`PAUSED`,`FINISHED`,），初始状态为 RUNNING，RUNNING
状态的 JOB 会根据既定的调度周期去生成 TASK 执行，Job 执行完成达到结束时间则状态变更为 `FINISHED`.
-
-- RUNNING 状态的 JOB 可以被 pause，即暂停，此时不会再生成 Task。
-
-- PAUSE 状态的 JOB 可以通过 RESUME 操作来恢复运行，更改为 RUNNING 状态。
-
-- STOP 状态的 JOB 由用户主动触发，此时会 Cancel 正在运行中的作业，然后删除 JOB。
-
-- Finished 状态的 JOB 会保留在系统中 24 H，24H 后会被删除。
-
-JOB 只描述作业信息，执行会生成 TASK，TASK 状态分为 PENDING，RUNNING，SUCCEESS,FAILED,CANCELED。
-
-- PENDING 表示到达触发时间了但是等待资源
-
-- 分配到资源后状态变更为 RUNNING
-
-- 执行成功/失败即变更为 SUCCESS/FAILED
-
-- CANCELED 即取消状态
-
-- TASK 持久化最终 SUCCESS/FAILED 这两个状态，其他状态运行中可以查到，但是如果重启则不可见
-
-- TASK 只保留最新的 100 条记录
-
-## 权限
-
-- 目前仅支持 *ADMIN* 权限执行此操作。
-
-## 语法
-
-```SQL
-CREATE
- JOB
- job_name
- ON SCHEDULE schedule
- [COMMENT 'string']
- DO sql_body;
-
-schedule: {
- AT timestamp
- | EVERY interval
- [STARTS timestamp ]
- [ENDS timestamp ]
-}
-
-interval:
- quantity { WEEK | DAY | HOUR | MINUTE }
-```
-
-一条有效的 Job 语句必须包含以下内容
-
-- 关键字 CREATE JOB 加上作业名称，它在一个 db 中标识唯一事件。JOB 名称必须是全局唯一的，如果已经存在同名的
JOB，则会报错。我们保留了 *inner_* 前缀在系统内部使用，因此用户不能创建以 *inner_* 开头的名称。
-
-- ON SCHEDULE 子句，它指定了 Job 作业的类型和触发时间以及频率。
-
-- DO 子句，它指定了 Job 作业触发时需要执行的操作，即一条 SQL 语句。
-
-## 举例
-
-下面是一个简单的例子。
-
-```SQL
-CREATE JOB my_job ON SCHEDULE EVERY 1 MINUTE DO INSERT INTO db1.tbl1 SELECT *
FROM db2.tbl2;
-```
-
-该语句表示创建一个名为 my_job 的作业，每分钟执行一次，执行的操作是将 db2.tbl2 中的数据导入到 db1.tbl1 中。
-
-SCHEDULE 语句用于定义作业的执行时间，频率以及持续时间，它可以指定一次性作业或者周期性作业。
-
-- **AT timestamp**
-
- 格式：'YYYY-MM-DD HH:MM:SS', 用于一次性事件，它指定事件仅在 给定的日期和时间执行一次
timestamp，当执行完成后，JOB 状态会变更为 FINISHED。
-
-- **EVERY**
-
- - **Interval**
-
- 表示定期重复操作，它指定了作业的执行频率，关键字后面要指定一个时间间隔，该时间间隔可以是周、天、小时、分钟、秒。例如：` 1 DAY`
表示每天执行一次，` 1 HOUR` 表示每小时执行一次，` 1 MINUTE` 表示每分钟执行一次，` 1 WEEK` 表示每周执行一次。
-
- - **STARTS timestamp（可选字段）**
-
- 格式：'YYYY-MM-DD HH:MM:SS',用于指定作业的开始时间，如果没有指定，则从当前时间的下一个时间点开始执行。开始时间必须大于当前时间。
-
- - **ENDS timestamp（可选字段）**
-
- 格式：'YYYY-MM-DD HH:MM:SS',
用于指定作业的结束时间，如果没有指定，则表示永久执行。该日期必须大于当前时间，如果指定了开始时间，即 `STARTS`，则结束时间必须大于开始时间。
-
-- **DO**
-
- 用于指定作业触发时需要执行的操作，目前仅支持 *INSERT 内表* 操作。后续我们会支持更多的操作。
-
- 1. 创建一个一次性的 Job，它会在 2020-01-01 00:00:00 时执行一次，执行的操作是将 db2.tbl2 中的数据导入到
db1.tbl1 中。
-
- ```SQL
- CREATE JOB my_job ON SCHEDULE AT '2020-01-01 00:00:00' DO INSERT INTO
db1.tbl1 SELECT * FROM db2.tbl2;
- ```
-
- 2. 创建一个周期性的 Job，它会在 2020-01-01 00:00:00 时开始执行，每天执行一次，执行的操作是将 db2.tbl2
中的数据导入到 db1.tbl1 中。
-
- ```SQL
- CREATE JOB my_job ON SCHEDULE EVERY 1 DAY STARTS '2020-01-01 00:00:00' DO
INSERT INTO db1.tbl1 SELECT * FROM db2.tbl2 WHERE create_time =
days_add(now(),-1);
- ```
-
- 3. 创建一个周期性的 Job，它会在 2020-01-01 00:00:00 时开始执行，每天执行一次，执行的操作是将 db2.tbl2
中的数据导入到 db1.tbl1 中，该 Job 在 2020-01-01 00:10:00 时结束。
-
- ```SQL
- CREATE JOB my_job ON SCHEDULE EVERY 1 DAY STARTS '2020-01-01 00:00:00'
ENDS '2020-01-01 00:10:00' DO INSERT INTO db1.tbl1 SELECT * FROM db2.tbl2
create_time = days_add(now(),-1);
- ```
-
-## INSERT JOB
-
-- 目前仅支持 _INSERT 内表_
-
-- 当下一个计划任务时间到期，即需要调度任务执行时，如果当前 JOB 仍有历史任务正在执行，则会跳过当前任务调度。因此控制一个合理的执行间隔非常重要。
-
-## CONFIG
-
-fe.conf
-
-- job_dispatch_timer_job_thread_num, 用于分发定时任务的线程数，默认值 2，如果含有大量周期执行任务，可以调大这个参数。
-
-- job_dispatch_timer_job_queue_size, 任务堆积时用于存放定时任务的队列大小，默认值 1024.
如果有大量任务同一时间触发，可以调大这个参数。否则会导致队列满，提交任务会进入阻塞状态，从而导致后续任务无法提交。
-
-- finished_job_cleanup_threshold_time_hour, 用于清理已完成的任务的时间阈值，单位为小时，默认值为 24 小时。
-
-- job_insert_task_consumer_thread_num = 10;用于执行 Insert 任务的线程数，值应该大于 0，否则默认为 5.
-
-## 最佳实践
-
-- 合理的进行 Job 的管理，避免大量的 Job 同时触发，导致任务堆积，从而影响系统的正常运行。
-
-- 任务的执行间隔应该设置在一个合理的范围，至少应该大于任务执行时间。
-
-## 更多帮助
-
-其他相关操作，查看 SQL 手册
[PAUSE-JOB](../../sql-manual/sql-reference/Data-Definition-Statements/Alter/PAUSE-JOB),[RESUME-JOB](../../sql-manual/sql-reference/Data-Definition-Statements/Alter/RESUME-JOB),[DROP-JOB](../../sql-manual/sql-reference/Data-Definition-Statements/Drop/DROP-JOB),
[TVF-JOB](../../sql-manual/sql-functions/table-functions/job),
-
-[TVF-TASKS](../../sql-manual/sql-functions/table-functions/tasks)。
\ No newline at end of file
diff --git a/versioned_docs/version-2.0/admin-manual/query-admin/job.md
b/versioned_docs/version-2.0/admin-manual/query-admin/job.md
deleted file mode 100644
index cfc87c1872e3..000000000000
--- a/versioned_docs/version-2.0/admin-manual/query-admin/job.md
+++ /dev/null
@@ -1,156 +0,0 @@
----
-{
- "title": "Job",
- "language": "en"
-}
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-# Job Scheduling
-
-In Doris, a job is a task that runs according to a pre-defined plan. It is
used to trigger pre-defined operations at specific times or intervals, helping
users automate certain tasks. In terms of functionality, it is similar to
scheduled tasks on an operating system (e.g., cron in Linux, Task Scheduler in
Windows).
-
-There are two types of jobs in Doris: `ONE_TIME` jobs and `RECURRING` jobs.
`ONE_TIME` jobs are triggered at a specified time and are primarily for
one-time tasks. The `RECURRING` jobs are triggered at specified intervals and
are used for tasks that need to be executed periodically. You can specify the
start and end time for `RECURRING` jobs via `STARTS\ENDS`. If no start time is
specified, the first execution time of the job will be set to one scheduling
period after the current time. I [...]
-
-There are four possible states for a job: `RUNNING`, `STOPPED`, `PAUSED`, and
`FINISHED`. The initial state is `RUNNING`. A `RUNNING` job generates tasks
based on the pre-defined scheduling period. When a job completes execution and
reaches the end time, it transitions to the `FINISHED` state.
-
-- A `RUNNING` job can be paused, meaning it will not generate tasks for the
time being.
-- A `PAUSED` job can be resumed through the RESUME operation, changing its
state to `RUNNING`.
-- A `STOPPED` job is triggered by the user. The running tasks will be canceled
and then the job will be deleted.
-- A `FINISHED` job remains in the system for 24 hours and is then deleted.
-
-A job only describes the task information, and the execution of the job
generates tasks. A task can be in one of the following states: `PENDING`,
`RUNNING`, `SUCCESS`, `FAILED`, or `CANCELED`.
-
-- `PENDING` means that the trigger time has been reached, but the task is
waiting for resources.
-- Once resources are allocated, the state of the task changes to `RUNNING`.
-- When the task completes successfully or fails, the state changes to
`SUCCESS` or `FAILED`, respectively.
-- `CANCELED` indicates that the task has been canceled.
-- Eventually, the tasks will persist with `SUCCESS` or `FAILED` states; other
states can be queried while the task is running but are not visible after a
restart.
-- Only the latest 100 task records are retained.
-
-## Privilege
-
-- Job scheduling can only be operated with admin privileges currently.
-
-## Syntax
-
-```SQL
-CREATE
- JOB
- job_name
- ON SCHEDULE schedule
- [COMMENT 'string']
- DO sql_body;
-
-schedule: {
- AT timestamp
- | EVERY interval
- [STARTS timestamp ]
- [ENDS timestamp ]
-}
-
-interval:
- quantity { WEEK | DAY | HOUR | MINUTE }
-```
-
-An effective job statement must include the following:
-
-- The keyword `CREATE JOB` followed by the job name, which uniquely identifies
the event within a database. The job name must be globally unique, and if a job
with the same name already exists, an error will occur. We reserve the "inner_"
prefix for internal system use, so users cannot create job names starting with
"inner_".
-- The `ON SCHEDULE` clause, which specifies the type of the job and its
trigger time and frequency.
-- The `DO` clause, which specifies the action to be executed when the job is
triggered, typically a SQL statement.
-
-## Example
-
-This is a simple example.
-
-```SQL
-CREATE JOB my_job ON SCHEDULE EVERY 1 MINUTE DO INSERT INTO db1.tbl1 SELECT *
FROM db2.tbl2;
-```
-
-This statement creates a job named "my_job" that executes every minute. The
action performed by the job is to import data from "db2.tbl2" into "db1.tbl1".
-
-The `SCHEDULE` statement is used to define the execution time, frequency, and
duration of a job. It can be used for either a one-time job or a recurring job.
-
-- **AT timestamp**
-
-Format: 'YYYY-MM-DD HH:MM:SS'
-
-This is used for one-time jobs. It specifies that the job should occur only
once at the given date and time. After execution, the job status changes to
FINISHED.
-
-- **EVERY**
- - **Interval**
-
-This represents a recurring operation and specifies the frequency of job
execution. The keyword should be followed by a time interval, which can be
specified in terms of weeks, days, hours, minutes, or seconds. For example, `1
DAY` means the job should be executed once every day, `1 HOUR` means once every
hour, `1 MINUTE` means once every minute, and `1 WEEK` means once every week.
-
-- **STARTS timestamp (optional)**
-
-Format: 'YYYY-MM-DD HH:MM:SS'
-
-It specifies the start time of the job. If not specified, the job starts
executing from the next occurrence based on the current time. The start time
must be later than the current time.
-
-- **ENDS timestamp (optional)**
-
-Format: 'YYYY-MM-DD HH:MM:SS' It specifies the end time of the job. If not
specified, the job should execute indefinitely. The end time must be later than
the current time. If a start time (`STARTS`) is specified, the end time must be
later than the start time.
-
-- **DO**
-
-It specifies the action to be performed when the job is triggered. Currently,
it only supports the INSERT INTO internal table operation. We plan to support
more operations in the future.
-
-1. Create a one-time job that executes on January 1, 2020, at 00:00:00. The
action is to import data from "db2.tbl2" into "db1.tbl1".
-
-```SQL
-CREATE JOB my_job ON SCHEDULE AT '2020-01-01 00:00:00' DO INSERT INTO db1.tbl1
SELECT * FROM db2.tbl2;
-```
-
-2. Create a recurring job that executes on January 1, 2020, at 00:00:00. It is
executed once a day. The action is to import data from "db2.tbl2" into
"db1.tbl1".
-
-```SQL
-CREATE JOB my_job ON SCHEDULE EVERY 1 DAY STARTS '2020-01-01 00:00:00' DO
INSERT INTO db1.tbl1 SELECT * FROM db2.tbl2 WHERE create_time =
days_add(now(),-1);
-```
-
-3. Create a recurring job that executes on January 1, 2020, at 00:00:00. It is
executed once a day. The action is to import data from "db2.tbl2" into
"db1.tbl1". It ends on January 1, 2020, at 00:10:00.
-
-```SQL
-CREATE JOB my_job ON SCHEDULE EVERY 1 DAY STARTS '2020-01-01 00:00:00' ENDS
'2020-01-01 00:10:00' DO INSERT INTO db1.tbl1 SELECT * FROM db2.tbl2
create_time = days_add(now(),-1);
-```
-
-## INSERT JOB
-
-- Currently, only INSERT INTO internal tables is supported.
-- When the next scheduled task time arrives and the current job still has
historical tasks running, the current task scheduling will be skipped.
Therefore, it is important to have a reasonable execution interval.
-
-## CONFIG
-
-fe.conf
-
-- `job_dispatch_timer_job_thread_num`: The number of threads for dispatching
scheduled tasks. The default value is 2. If there are a large number of
recurring tasks, this parameter can be increased.
-- `job_dispatch_timer_job_queue_size`: The queue size used to store scheduled
tasks when there is a backlog of tasks. The default value is 1024. If there are
a large number of tasks triggered at the same time, this parameter can be
increased. Otherwise, the queue may become full, causing submitted tasks to be
blocked and subsequent tasks unable to be submitted.
-- `finished_job_cleanup_threshold_time_hour`: The time threshold, measured in
hours, for cleaning up completed tasks. The default value is 24 hours.
-- `job_insert_task_consumer_thread_num`: The number of threads used for
executing INSERT tasks. The value should be greater than 0; otherwise, the
default value of 5 will be used.
-
-## Best Practice
-
-- Manage jobs properly to avoid a large number of jobs being triggered
simultaneously, thus avoiding task backlogs and system abnomalities.
-- Set the execution interval of tasks within a reasonable range and ensure
that it is at least greater than the task execution time.
-
-## More help
-
-For further information, refer to the SQL manual for
[PAUSE-JOB](https://doris.apache.org/docs/2.0/sql-manual/sql-reference/Data-Definition-Statements/Alter/PAUSE-JOB/),
[RESUME-JOB](https://doris.apache.org/docs/2.0/sql-manual/sql-reference/Data-Definition-Statements/Alter/RESUME-JOB/),
[DROP-JOB](https://doris.apache.org/docs/sql-manual/sql-reference/Data-Definition-Statements/Drop/DROP-JOB/),
[TVF-JOB](https://doris.apache.org/docs/sql-manual/sql-functions/table-functions/job/),
and [ [...]
diff --git a/versioned_sidebars/version-2.0-sidebars.json
b/versioned_sidebars/version-2.0-sidebars.json
index 320e6177be19..4c4824fce6d6 100644
--- a/versioned_sidebars/version-2.0-sidebars.json
+++ b/versioned_sidebars/version-2.0-sidebars.json
@@ -318,8 +318,7 @@
"label": "Query Admin",
"items": [
"admin-manual/query-admin/sql-interception",
- "admin-manual/query-admin/kill-query",
- "admin-manual/query-admin/job"
+ "admin-manual/query-admin/kill-query"
]
},
{
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org
For additional commands, e-mail: commits-h...@doris.apache.org
