You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by gi...@apache.org on 2023/05/15 03:33:26 UTC
[dolphinscheduler-website] branch asf-site updated: Automated deployment: 21b47d8b146a806d21f68ee851708561e4a8d468
This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new ddf7107576 Automated deployment: 21b47d8b146a806d21f68ee851708561e4a8d468
ddf7107576 is described below
commit ddf7107576ffe3bbcd0424ce8edfd7a18a0adbf0
Author: github-actions[bot] <gi...@users.noreply.github.com>
AuthorDate: Mon May 15 03:33:20 2023 +0000
Automated deployment: 21b47d8b146a806d21f68ee851708561e4a8d468
---
data/doc/zh-cn.json | 1261 ++++++++++++++++++--
data/faq/en-us.json | 228 ++--
data/faq/zh-cn.json | 224 ++--
fetch/deployment.json | 12 +-
fetch/doc/en-us/3.1.6.json | 1127 +++++++++++++++++
fetch/doc/zh-cn/3.1.6.json | 1067 +++++++++++++++++
fetch/download.json | 21 +-
data/faq/en-us.json => fetch/faq/en-us/3.1.6.json | 114 --
fetch/faq/version.json | 3 +-
data/faq/zh-cn.json => fetch/faq/zh-cn/3.1.6.json | 112 --
fetch/version.json | 3 +-
img/tasks/demo/dinky_task_id.png | Bin 170795 -> 221254 bytes
pages/doc/en-us/3.1.5/DSIP.json | 2 +-
pages/doc/en-us/3.1.5/about/features.json | 2 +-
pages/doc/en-us/3.1.5/about/glossary.json | 2 +-
pages/doc/en-us/3.1.5/about/hardware.json | 2 +-
pages/doc/en-us/3.1.5/about/introduction.json | 2 +-
pages/doc/en-us/3.1.5/architecture/cache.json | 2 +-
.../en-us/3.1.5/architecture/configuration.json | 2 +-
pages/doc/en-us/3.1.5/architecture/design.json | 2 +-
.../doc/en-us/3.1.5/architecture/load-balance.json | 2 +-
pages/doc/en-us/3.1.5/architecture/metadata.json | 2 +-
.../en-us/3.1.5/architecture/task-structure.json | 2 +-
.../en-us/3.1.5/contribute/backend/spi/alert.json | 2 +-
.../3.1.5/contribute/backend/spi/datasource.json | 2 +-
.../3.1.5/contribute/backend/spi/registry.json | 2 +-
.../en-us/3.1.5/contribute/backend/spi/task.json | 2 +-
.../contribute/development-environment-setup.json | 2 +-
.../3.1.5/contribute/frontend-development.json | 2 +-
.../3.1.5/guide/alert/alert_plugin_user_guide.json | 2 +-
pages/doc/en-us/3.1.5/guide/alert/dingtalk.json | 2 +-
pages/doc/en-us/3.1.5/guide/alert/email.json | 2 +-
.../3.1.5/guide/alert/enterprise-webexteams.json | 2 +-
.../en-us/3.1.5/guide/alert/enterprise-wechat.json | 2 +-
pages/doc/en-us/3.1.5/guide/alert/feishu.json | 2 +-
pages/doc/en-us/3.1.5/guide/alert/http.json | 2 +-
pages/doc/en-us/3.1.5/guide/alert/script.json | 2 +-
pages/doc/en-us/3.1.5/guide/alert/telegram.json | 2 +-
pages/doc/en-us/3.1.5/guide/api/healthcheck.json | 2 +-
pages/doc/en-us/3.1.5/guide/api/open-api.json | 2 +-
.../en-us/3.1.5/guide/api/pydolphinscheduler.json | 2 +-
pages/doc/en-us/3.1.5/guide/data-quality.json | 2 +-
pages/doc/en-us/3.1.5/guide/datasource/athena.json | 2 +-
.../en-us/3.1.5/guide/datasource/clickhouse.json | 2 +-
pages/doc/en-us/3.1.5/guide/datasource/db2.json | 2 +-
pages/doc/en-us/3.1.5/guide/datasource/hive.json | 2 +-
pages/doc/en-us/3.1.5/guide/datasource/mysql.json | 2 +-
pages/doc/en-us/3.1.5/guide/datasource/oracle.json | 2 +-
.../en-us/3.1.5/guide/datasource/postgresql.json | 2 +-
pages/doc/en-us/3.1.5/guide/datasource/presto.json | 2 +-
.../doc/en-us/3.1.5/guide/datasource/redshift.json | 2 +-
pages/doc/en-us/3.1.5/guide/datasource/spark.json | 2 +-
.../en-us/3.1.5/guide/datasource/sqlserver.json | 2 +-
.../doc/en-us/3.1.5/guide/expansion-reduction.json | 2 +-
pages/doc/en-us/3.1.5/guide/homepage.json | 2 +-
.../en-us/3.1.5/guide/installation/cluster.json | 2 +-
.../en-us/3.1.5/guide/installation/kubernetes.json | 2 +-
.../3.1.5/guide/installation/pseudo-cluster.json | 2 +-
.../en-us/3.1.5/guide/installation/standalone.json | 2 +-
.../en-us/3.1.5/guide/integration/rainbond.json | 2 +-
pages/doc/en-us/3.1.5/guide/metrics/metrics.json | 2 +-
pages/doc/en-us/3.1.5/guide/monitor.json | 2 +-
.../doc/en-us/3.1.5/guide/parameter/built-in.json | 2 +-
pages/doc/en-us/3.1.5/guide/parameter/context.json | 2 +-
pages/doc/en-us/3.1.5/guide/parameter/global.json | 2 +-
pages/doc/en-us/3.1.5/guide/parameter/local.json | 2 +-
.../doc/en-us/3.1.5/guide/parameter/priority.json | 2 +-
.../en-us/3.1.5/guide/project/project-list.json | 2 +-
.../en-us/3.1.5/guide/project/task-definition.json | 2 +-
.../en-us/3.1.5/guide/project/task-instance.json | 2 +-
.../3.1.5/guide/project/workflow-definition.json | 2 +-
.../3.1.5/guide/project/workflow-instance.json | 2 +-
.../en-us/3.1.5/guide/resource/configuration.json | 2 +-
.../en-us/3.1.5/guide/resource/file-manage.json | 2 +-
pages/doc/en-us/3.1.5/guide/resource/intro.json | 2 +-
.../doc/en-us/3.1.5/guide/resource/task-group.json | 2 +-
.../doc/en-us/3.1.5/guide/resource/udf-manage.json | 2 +-
pages/doc/en-us/3.1.5/guide/security.json | 2 +-
pages/doc/en-us/3.1.5/guide/start/docker.json | 2 +-
pages/doc/en-us/3.1.5/guide/start/quick-start.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/appendix.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/chunjun.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/conditions.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/datax.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/dependent.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/dinky.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/dvc.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/emr.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/flink.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/hive-cli.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/http.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/jupyter.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/kubernetes.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/map-reduce.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/mlflow.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/openmldb.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/pigeon.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/python.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/pytorch.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/sagemaker.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/seatunnel.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/shell.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/spark.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/sql.json | 2 +-
.../en-us/3.1.5/guide/task/stored-procedure.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/sub-process.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/switch.json | 2 +-
pages/doc/en-us/3.1.5/guide/task/zeppelin.json | 2 +-
.../en-us/3.1.5/guide/upgrade/incompatible.json | 2 +-
pages/doc/en-us/3.1.5/guide/upgrade/upgrade.json | 2 +-
pages/doc/en-us/{3.1.5 => 3.1.6}/DSIP.json | 2 +-
.../doc/en-us/{3.1.5 => 3.1.6}/about/features.json | 2 +-
.../doc/en-us/{3.1.5 => 3.1.6}/about/glossary.json | 2 +-
.../doc/en-us/{3.1.5 => 3.1.6}/about/hardware.json | 2 +-
.../en-us/{3.1.5 => 3.1.6}/about/introduction.json | 2 +-
.../en-us/{3.1.5 => 3.1.6}/architecture/cache.json | 2 +-
.../architecture/configuration.json | 2 +-
.../{3.1.5 => 3.1.6}/architecture/design.json | 4 +-
.../architecture/load-balance.json | 2 +-
.../{3.1.5 => 3.1.6}/architecture/metadata.json | 2 +-
.../architecture/task-structure.json | 2 +-
.../contribute/backend/spi/alert.json | 2 +-
.../contribute/backend/spi/datasource.json | 2 +-
.../contribute/backend/spi/registry.json | 2 +-
.../contribute/backend/spi/task.json | 2 +-
.../contribute/development-environment-setup.json | 4 +-
.../contribute/frontend-development.json | 2 +-
.../guide/alert/alert_plugin_user_guide.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/alert/dingtalk.json | 2 +-
.../en-us/{3.1.5 => 3.1.6}/guide/alert/email.json | 2 +-
.../guide/alert/enterprise-webexteams.json | 2 +-
.../guide/alert/enterprise-wechat.json | 2 +-
.../en-us/{3.1.5 => 3.1.6}/guide/alert/feishu.json | 2 +-
.../en-us/{3.1.5 => 3.1.6}/guide/alert/http.json | 2 +-
.../en-us/{3.1.5 => 3.1.6}/guide/alert/script.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/alert/telegram.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/api/healthcheck.json | 2 +-
.../en-us/{3.1.5 => 3.1.6}/guide/api/open-api.json | 2 +-
.../guide/api/pydolphinscheduler.json | 2 +-
.../en-us/{3.1.5 => 3.1.6}/guide/data-quality.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/datasource/athena.json | 4 +-
.../guide/datasource/clickhouse.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/datasource/db2.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/datasource/hive.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/datasource/mysql.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/datasource/oracle.json | 2 +-
.../guide/datasource/postgresql.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/datasource/presto.json | 2 +-
.../guide/datasource/redshift.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/datasource/spark.json | 2 +-
.../guide/datasource/sqlserver.json | 2 +-
.../guide/expansion-reduction.json | 4 +-
.../doc/en-us/{3.1.5 => 3.1.6}/guide/homepage.json | 2 +-
.../guide/installation/cluster.json | 4 +-
.../guide/installation/kubernetes.json | 4 +-
.../guide/installation/pseudo-cluster.json | 4 +-
.../guide/installation/standalone.json | 4 +-
.../guide/integration/rainbond.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/metrics/metrics.json | 2 +-
.../doc/en-us/{3.1.5 => 3.1.6}/guide/monitor.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/parameter/built-in.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/parameter/context.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/parameter/global.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/parameter/local.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/parameter/priority.json | 4 +-
.../guide/project/project-list.json | 2 +-
.../guide/project/task-definition.json | 4 +-
.../guide/project/task-instance.json | 2 +-
.../guide/project/workflow-definition.json | 4 +-
.../guide/project/workflow-instance.json | 4 +-
.../en-us/3.1.6/guide/resource/configuration.json | 35 +
.../guide/resource/file-manage.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/resource/intro.json | 2 +-
.../guide/resource/task-group.json | 2 +-
.../guide/resource/udf-manage.json | 2 +-
.../doc/en-us/{3.1.5 => 3.1.6}/guide/security.json | 2 +-
pages/doc/en-us/3.1.6/guide/start/docker.json | 96 ++
.../{3.1.5 => 3.1.6}/guide/start/quick-start.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/task/appendix.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/chunjun.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/conditions.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/datax.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/dependent.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/dinky.json | 4 +-
.../doc/en-us/{3.1.5 => 3.1.6}/guide/task/dvc.json | 4 +-
.../doc/en-us/{3.1.5 => 3.1.6}/guide/task/emr.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/flink.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/hive-cli.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/http.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/jupyter.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/kubernetes.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/map-reduce.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/mlflow.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/openmldb.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/pigeon.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/python.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/pytorch.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/sagemaker.json | 4 +-
pages/doc/en-us/3.1.6/guide/task/seatunnel.json | 97 ++
.../en-us/{3.1.5 => 3.1.6}/guide/task/shell.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/spark.json | 4 +-
.../doc/en-us/{3.1.5 => 3.1.6}/guide/task/sql.json | 4 +-
.../guide/task/stored-procedure.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/sub-process.json | 4 +-
.../en-us/{3.1.5 => 3.1.6}/guide/task/switch.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/zeppelin.json | 4 +-
.../guide/upgrade/incompatible.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/upgrade/upgrade.json | 4 +-
pages/doc/zh-cn/3.1.5/DSIP.json | 2 +-
pages/doc/zh-cn/3.1.5/about/features.json | 2 +-
pages/doc/zh-cn/3.1.5/about/glossary.json | 2 +-
pages/doc/zh-cn/3.1.5/about/hardware.json | 2 +-
pages/doc/zh-cn/3.1.5/about/introduction.json | 2 +-
pages/doc/zh-cn/3.1.5/architecture/cache.json | 2 +-
.../zh-cn/3.1.5/architecture/configuration.json | 2 +-
pages/doc/zh-cn/3.1.5/architecture/design.json | 2 +-
.../doc/zh-cn/3.1.5/architecture/load-balance.json | 2 +-
pages/doc/zh-cn/3.1.5/architecture/metadata.json | 2 +-
.../zh-cn/3.1.5/architecture/task-structure.json | 2 +-
.../zh-cn/3.1.5/contribute/backend/spi/alert.json | 2 +-
.../3.1.5/contribute/backend/spi/datasource.json | 2 +-
.../3.1.5/contribute/backend/spi/registry.json | 2 +-
.../zh-cn/3.1.5/contribute/backend/spi/task.json | 2 +-
.../contribute/development-environment-setup.json | 2 +-
.../3.1.5/contribute/frontend-development.json | 2 +-
.../3.1.5/guide/alert/alert_plugin_user_guide.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/alert/dingtalk.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/alert/email.json | 2 +-
.../3.1.5/guide/alert/enterprise-webexteams.json | 2 +-
.../zh-cn/3.1.5/guide/alert/enterprise-wechat.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/alert/feishu.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/alert/http.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/alert/script.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/alert/telegram.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/api/healthcheck.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/api/open-api.json | 2 +-
.../zh-cn/3.1.5/guide/api/pydolphinscheduler.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/data-quality.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/datasource/athena.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/datasource/hive.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/datasource/mysql.json | 2 +-
.../zh-cn/3.1.5/guide/datasource/postgresql.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/datasource/spark.json | 2 +-
.../doc/zh-cn/3.1.5/guide/expansion-reduction.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/homepage.json | 2 +-
.../zh-cn/3.1.5/guide/installation/cluster.json | 2 +-
.../zh-cn/3.1.5/guide/installation/kubernetes.json | 2 +-
.../3.1.5/guide/installation/pseudo-cluster.json | 2 +-
.../zh-cn/3.1.5/guide/installation/standalone.json | 2 +-
.../zh-cn/3.1.5/guide/integration/rainbond.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/metrics/metrics.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/monitor.json | 2 +-
.../doc/zh-cn/3.1.5/guide/parameter/built-in.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/parameter/context.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/parameter/global.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/parameter/local.json | 2 +-
.../doc/zh-cn/3.1.5/guide/parameter/priority.json | 2 +-
.../zh-cn/3.1.5/guide/project/project-list.json | 2 +-
.../zh-cn/3.1.5/guide/project/task-definition.json | 2 +-
.../zh-cn/3.1.5/guide/project/task-instance.json | 2 +-
.../3.1.5/guide/project/workflow-definition.json | 2 +-
.../3.1.5/guide/project/workflow-instance.json | 2 +-
.../zh-cn/3.1.5/guide/resource/configuration.json | 2 +-
.../zh-cn/3.1.5/guide/resource/file-manage.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/resource/intro.json | 2 +-
.../doc/zh-cn/3.1.5/guide/resource/task-group.json | 2 +-
.../doc/zh-cn/3.1.5/guide/resource/udf-manage.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/security.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/start/docker.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/start/quick-start.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/appendix.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/chunjun.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/conditions.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/datax.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/dependent.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/dinky.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/dvc.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/emr.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/flink.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/hive-cli.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/http.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/jupyter.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/kubernetes.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/map-reduce.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/mlflow.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/openmldb.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/pigeon.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/python.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/pytorch.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/sagemaker.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/seatunnel.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/shell.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/spark.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/sql.json | 2 +-
.../zh-cn/3.1.5/guide/task/stored-procedure.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/sub-process.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/switch.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/task/zeppelin.json | 2 +-
.../zh-cn/3.1.5/guide/upgrade/incompatible.json | 2 +-
pages/doc/zh-cn/3.1.5/guide/upgrade/upgrade.json | 2 +-
pages/doc/zh-cn/{3.1.5 => 3.1.6}/DSIP.json | 2 +-
.../doc/zh-cn/{3.1.5 => 3.1.6}/about/features.json | 2 +-
.../doc/zh-cn/{3.1.5 => 3.1.6}/about/glossary.json | 2 +-
.../doc/zh-cn/{3.1.5 => 3.1.6}/about/hardware.json | 2 +-
.../zh-cn/{3.1.5 => 3.1.6}/about/introduction.json | 2 +-
.../zh-cn/{3.1.5 => 3.1.6}/architecture/cache.json | 2 +-
.../architecture/configuration.json | 2 +-
.../{3.1.5 => 3.1.6}/architecture/design.json | 2 +-
.../architecture/load-balance.json | 2 +-
.../{3.1.5 => 3.1.6}/architecture/metadata.json | 2 +-
.../architecture/task-structure.json | 2 +-
.../contribute/backend/spi/alert.json | 2 +-
.../contribute/backend/spi/datasource.json | 2 +-
.../contribute/backend/spi/registry.json | 2 +-
.../contribute/backend/spi/task.json | 2 +-
.../contribute/development-environment-setup.json | 4 +-
.../contribute/frontend-development.json | 2 +-
.../guide/alert/alert_plugin_user_guide.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/alert/dingtalk.json | 2 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/alert/email.json | 2 +-
.../guide/alert/enterprise-webexteams.json | 2 +-
.../guide/alert/enterprise-wechat.json | 2 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/alert/feishu.json | 2 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/alert/http.json | 2 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/alert/script.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/alert/telegram.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/api/healthcheck.json | 2 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/api/open-api.json | 2 +-
.../guide/api/pydolphinscheduler.json | 2 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/data-quality.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/datasource/athena.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/datasource/hive.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/datasource/mysql.json | 4 +-
.../guide/datasource/postgresql.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/datasource/spark.json | 2 +-
.../guide/expansion-reduction.json | 4 +-
.../doc/zh-cn/{3.1.5 => 3.1.6}/guide/homepage.json | 2 +-
.../guide/installation/cluster.json | 4 +-
.../guide/installation/kubernetes.json | 4 +-
.../guide/installation/pseudo-cluster.json | 4 +-
.../zh-cn/3.1.6/guide/installation/standalone.json | 76 ++
.../guide/integration/rainbond.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/metrics/metrics.json | 2 +-
.../doc/zh-cn/{3.1.5 => 3.1.6}/guide/monitor.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/parameter/built-in.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/parameter/context.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/parameter/global.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/parameter/local.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/parameter/priority.json | 4 +-
.../guide/project/project-list.json | 2 +-
.../guide/project/task-definition.json | 4 +-
.../guide/project/task-instance.json | 2 +-
.../guide/project/workflow-definition.json | 4 +-
.../guide/project/workflow-instance.json | 4 +-
.../zh-cn/3.1.6/guide/resource/configuration.json | 45 +
.../guide/resource/file-manage.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/resource/intro.json | 2 +-
.../guide/resource/task-group.json | 2 +-
.../guide/resource/udf-manage.json | 2 +-
.../doc/zh-cn/{3.1.5 => 3.1.6}/guide/security.json | 2 +-
pages/doc/zh-cn/3.1.6/guide/start/docker.json | 96 ++
.../{3.1.5 => 3.1.6}/guide/start/quick-start.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/task/appendix.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/chunjun.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/conditions.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/datax.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/dependent.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/dinky.json | 4 +-
.../doc/zh-cn/{3.1.5 => 3.1.6}/guide/task/dvc.json | 4 +-
.../doc/zh-cn/{3.1.5 => 3.1.6}/guide/task/emr.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/flink.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/hive-cli.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/http.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/jupyter.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/kubernetes.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/map-reduce.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/mlflow.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/openmldb.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/pigeon.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/python.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/pytorch.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/sagemaker.json | 4 +-
pages/doc/zh-cn/3.1.6/guide/task/seatunnel.json | 97 ++
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/shell.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/spark.json | 4 +-
.../doc/zh-cn/{3.1.5 => 3.1.6}/guide/task/sql.json | 4 +-
.../guide/task/stored-procedure.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/sub-process.json | 4 +-
.../zh-cn/{3.1.5 => 3.1.6}/guide/task/switch.json | 4 +-
.../{3.1.5 => 3.1.6}/guide/task/zeppelin.json | 4 +-
.../guide/upgrade/incompatible.json | 2 +-
.../{3.1.5 => 3.1.6}/guide/upgrade/upgrade.json | 4 +-
python/2.0.5/.buildinfo | 2 +-
python/2.0.6/.buildinfo | 2 +-
python/2.0.7/.buildinfo | 2 +-
python/3.0.0/.buildinfo | 2 +-
python/3.0.1/.buildinfo | 2 +-
python/3.1.0/.buildinfo | 2 +-
python/4.0.0/.buildinfo | 2 +-
python/4.0.1/.buildinfo | 2 +-
python/4.0.2/.buildinfo | 2 +-
python/4.0.3/.buildinfo | 2 +-
python/main/.buildinfo | 2 +-
403 files changed, 4631 insertions(+), 1019 deletions(-)
diff --git a/data/doc/zh-cn.json b/data/doc/zh-cn.json
index 932ac99a5f..87c0819024 100644
--- a/data/doc/zh-cn.json
+++ b/data/doc/zh-cn.json
@@ -15813,7 +15813,7 @@
{
"content": "关于DolphinScheduler\nApache DolphinScheduler 是一个分布式易扩展的可视化DAG工作流任务调度开源系统。适用于企业级场景，提供了一个可视化操作任务、工作流和全生命周期数据处理过程的解决方案。\nApache DolphinScheduler 旨在解决复杂的大数据任务依赖关系，并为应用程序提供数据和各种 OPS 编排中的关系。 解决数据研发ETL依赖错综复杂，无法监控任务健康状态的问题。\nDolphinScheduler 以 DAG（Directed Acyclic Graph，DAG）流式方式组装任务，可以及时监控任务的执行状态，支持重试、指定节点恢复失败、暂停、恢复、终止任务等操作。\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/about/introduction",
"title": "关于DolphinScheduler",
"location": [
@@ -15824,7 +15824,7 @@
{
"content": "特性\n简单易用\n\n可视化 DAG: 用户友好的，通过拖拽定义工作流的，运行时控制工具\n模块化操作: 模块化有助于轻松定制和维护。\n\n丰富的使用场景\n\n支持多种任务类型: 支持Shell、MR、Spark、SQL等10余种任务类型，支持跨语言，易于扩展\n丰富的工作流操作: 工作流程可以定时、暂停、恢复和停止，便于维护和控制全局和本地参数。\n\nHigh Reliability\n\n高可靠性: 去中心化设计，确保稳定性。 原生 HA 任务队列支持，提供过载容错能力。 DolphinScheduler 能提供高度稳健的环境。\n\nHigh Scalability\n\n高扩展性: 支持多租户和在线资源管理。支持每天10万个数据任务的稳定运行。\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/about/features",
"title": "特性",
"location": [
@@ -15835,7 +15835,7 @@
{
"content": "软硬件环境建议配置\nDolphinScheduler 作为一款开源分布式工作流任务调度系统，可以很好地部署和运行在 Intel 架构服务器及主流虚拟化环境下，并支持主流的Linux操作系统环境\n1. Linux 操作系统版本要求\n\n\n\n操作系统\n版本\n\n\n\n\nRed Hat Enterprise Linux\n7.0 及以上\n\n\nCentOS\n7.0 及以上\n\n\nOracle Enterprise Linux\n7.0 及以上\n\n\nUbuntu LTS\n16.04 及以上\n\n\n\n\n注意：\n以上 Linux 操作系统可运行在物理服务器以及 VMware、KVM、XEN 主流虚拟化环境上\n\n2. 服务器建议配置\nDolphinScheduler 支持运行在 Intel x86-64 架构的 64 位通用硬件服务器平台。对生产环境的服务器硬件配置有以下建议：\n生产环境\n\n\n\nCPU\n内存\n硬盘类型\n网络\n实例数量\n\n\n\n\n4核+\n8 GB+\nSAS\ [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/about/hardware",
"title": "软硬件环境建议配置",
"location": [
@@ -15846,7 +15846,7 @@
{
"content": "名词解释\n在对 Apache DolphinScheduler 了解之前，我们先来认识一下调度系统常用的名词\n1.名词解释\nDAG： 全称 Directed Acyclic Graph，简称 DAG。工作流中的 Task 任务以有向无环图的形式组装起来，从入度为零的节点进行拓扑遍历，直到无后继节点为止。举例如下图：\n\n流程定义：通过拖拽任务节点并建立任务节点的关联所形成的可视化DAG\n流程实例：流程实例是流程定义的实例化，可以通过手动启动或定时调度生成。每运行一次流程定义，产生一个流程实例\n任务实例：任务实例是流程定义中任务节点的实例化，标识着某个具体的任务\n任务类型：目前支持有 SHELL、SQL、SUB_PROCESS(子流程)、PROCEDURE、MR、SPARK、PYTHON、DEPENDENT(依赖)，同时计划支持动态插件扩展，注意：其中 SUB_PROCESS类型的任务需要关联另外一个流程定义，被关联的流程定义是可
以单独启动执行的\n调度方式：系统支持基于 cron 表达式的定时调度和手动调度。命令类型支持：启 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/about/glossary",
"title": "名词解释",
"location": [
@@ -15857,7 +15857,7 @@
{
"content": "快速上手\n\n\n喜欢看视频的伙伴可以参见手把手教你如何《快速上手 Apache DolphinScheduler 教程》\n\n\n\n管理员用户登录\n\n地址：http://localhost:12345/dolphinscheduler/ui 用户名/密码：admin/dolphinscheduler123\n\n\n\n\n\n创建队列\n\n\n\n创建租户\n\n\n\n创建普通用户\n\n\n\n创建告警组实例\n\n\n\n创建告警组\n\n\n\n创建 Worker 分组\n\n\n\n\n创建环境\n\n\n\n创建 Token 令牌\n\n\n\n\n使用普通用户登录\n\n\n点击右上角用户名“退出”，重新使用普通用户登录。\n\n\n项目管理->创建项目->点击项目名称\n\n\n\n点击工作流定义->创建工作流定义->上线工作流定义\n\n\n\n运行工作流定义->点击工作流实例->点击工作流实例名称->双击任务节点->查看任务执行日志\n\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/start/quick-start",
"title": "快速上手",
"location": [
@@ -15868,7 +15868,7 @@
{
"content": "Docker 快速使用教程\n本教程使用三种不同的方式通过 Docker 完成 DolphinScheduler 的部署，如果你想要快速体验，推荐使用 standalone-server 镜像，\n如果你想要体验比较完成的服务，推荐使用 docker-compose 启动服务。如果你已经有自己的数据库或者 Zookeeper 服务\n你想要沿用这些基础服务，你可以参考沿用已有的 PostgreSQL 和 ZooKeeper 服务完成部署。\n前置条件\n\nDocker 1.13.1+\nDocker Compose 1.28.0+\n\n启动服务\n使用 standalone-server 镜像\n使用 standalone-server 镜像启动一个 DolphinScheduler standalone-server 容器应该是最快体验 DolphinScheduler 的方法。通过这个方式\n你可以最快速的体验到 DolphinScheduler 的大部分功能，了解主要和概念和内容。\n$ DOLPHINSCHEDULER_VER [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/start/docker",
"title": "Docker 快速使用教程",
"location": [
@@ -15879,7 +15879,7 @@
{
"content": "首页\nApache DolphinScheduler 首页可让您查看用户所有项目的任务状态统计、工作流状态统计和项目统计。 这是观察整个系统状态以及深入各个进程以检查任务和任务日志的每个状态的最佳方式。\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/homepage",
"title": "首页",
"location": [
@@ -15890,7 +15890,7 @@
{
"content": "项目管理\n创建项目\n点击"项目管理"进入项目管理页面，点击“创建项目”按钮，输入项目名称，项目描述，点击“提交”，创建新的项目。\n\n项目首页\n在项目管理页面点击项目名称链接，进入项目首页，如下图所示，项目首页包含该项目的任务状态统计、流程状态统计、工作流定义统计。这几个指标的说明如下\n\n任务状态统计：在指定时间范围内，统计任务实例中状态为提交成功、正在运行、准备暂停、暂停、准备停止、停止、失败、成功、需要容错、kill、等待线程的个数\n流程状态统计：在指定时间范围内，统计工作流实例中状态为提交成功、正在运行、准备暂停、暂停、准备停止、停止、失败、成功、需要容错、kill、等待线程的个数\n工作流定义统计：统计用户创建的工作流定义及管理员授予该用户的工作流定义\n\n
\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/project/project-list",
"title": "项目管理",
"location": [
@@ -15902,7 +15902,7 @@
{
"content": "工作流定义\n创建工作流定义\n\n\n点击项目管理->工作流->工作流定义，进入工作流定义页面，点击“创建工作流”按钮，进入工作流DAG编辑页面，如下图所示：\n\n\n\n工具栏中拖拽 到画板中，新增一个Shell任务,如下图所示：\n\n\n\n添加 Shell 任务的参数设置：\n\n填写“节点名称”，“描述”，“脚本”字段；\n“运行标志”勾选“正常”，若勾选“禁止执行”，运行工作流不会执行该任务；\n选择“任务优先级”：当 worker 线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；\n超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过超时时长，会发送告警邮件并且任务超时失败；\n资源（非必选）：资源文件是资源中心->文件管理页面创建或上传的�
��件，如文件名为 test.sh，脚本中调用资源命令为 sh test.sh。注意调用需要使用资源的全路径；\n自定义参数（非必填）；\n点击"确认添加"按钮，保存任务设置。\ [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/project/workflow-definition",
"title": "工作流定义",
"location": [
@@ -15914,7 +15914,7 @@
{
"content": "工作流实例\n查看工作流实例\n\n点击项目管理->工作流->工作流实例，进入工作流实例页面，如下图所示：\n\n\n\n点击工作流名称，进入DAG查看页面，查看任务执行状态，如下图所示。\n\n\n查看任务日志\n\n进入工作流实例页面，点击工作流名称，进入DAG查看页面，双击任务节点，如下图所示：\n\n\n\n点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考任务查看日志。\n\n\n查看任务历史记录\n\n点击项目管理->工作流->工作流实例，进入工作流实例页面，点击工作流名称，进入工作流 DAG 页面;\n双击任务节点，如下图所示，点击"查看历史"，跳转到任务实例页面，并展示该工作流实例运行的任务实例列表\n\n\n查看运行参数\n\n点击项目管理->工作流->工作流实例，进入工作流实例页面�
�点击工作流名称，进入工作流 DAG 页面;\n点击左上角图标，查看工作流实例的启动参数；点击图标，查看工作流实例的全局参数和局部参数，如 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/project/workflow-instance",
"title": "工作流实例",
"location": [
@@ -15926,7 +15926,7 @@
{
"content": "任务实例\n批量任务实例\n\n点击项目管理->工作流->任务实例，进入任务实例页面，如下图所示，点击工作流实例名称，可跳转到工作流实例DAG图查看任务状态。\n\n\n\n查看日志：点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。\n\n\n实时任务实例\n\n切换到实时任务实例页面，如下图所示：\n\n\n\nSavePoint：点击操作列中的SavePoint按钮，可以进行实时任务的SavePoint。\nStop：点击操作列中的Stop按钮，可以停止该实时任务。\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/project/task-instance",
"title": "任务实例",
"location": [
@@ -15938,7 +15938,7 @@
{
"content": "任务定义\n批量任务定义\n批量任务定义允许您在基于任务级别而不是在工作流中操作修改任务。再此之前，我们已经有了工作流级别的任务编辑器，你可以在工作流定义\n单击特定的工作流，然后编辑任务的定义。当您想编辑特定的任务定义但不记得它属于哪个工作流时，这是令人沮丧的。所以我们决定在 任务 菜单下添加 任务定义 视图。\n\n在该视图中，您可以通过单击 操作 列中的相关按钮来进行创建、查询、更新、删除任务定义。最令人兴奋的是您可以通过通配符进行全部任务查询，当您只\n记得任务名称但忘记它属于哪个工作流时是非常有用的。也支持通过任务名称结合使用 任务类型 或 工作流程名称 进行查询。\n实时任务定义\n实时任务定义在工作流定义中创建，在任务定义页面可以进行修改和执行。\n\n点击实时任务执行，
检查执行参数后点击确认，即可提交实时任务。\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/project/task-definition",
"title": "任务定义",
"location": [
@@ -15950,7 +15950,7 @@
{
"content": "DolphinScheduler任务参数附录\nDolphinScheduler任务插件有一些公共参数，我们将这些公共参数列在文档中供您查阅。每种任务都有如下的所有或者部分默认参数：\n默认任务参数\n\n\n\n任务参数\n描述\n\n\n\n\n任务名称\n任务的名称，同一个工作流定义中的节点名称不能重复。\n\n\n运行标志\n标识这个节点是否需要调度执行，如果不需要执行，可以打开禁止执行开关。\n\n\n描述\n当前节点的功能描述。\n\n\n任务优先级\nworker线程数不足时，根据优先级从高到低依次执行任务，优先级一样时根据先到先得原则执行。\n\n\nWorker分组\n设置分组后，任务会被分配给worker组的机器机执行。若选择Default，则会随机选择一个worker执行。\n\n\n任务组名称\n任务资源组，未配置则不生效。\n\n\n组内优先级\n一个任务组内此任务的优先级。\n\n\n环境名称\n配置任务执�
�的环境。\n\n\n失败重试次数\n任务失败重新提交的次数，可以在下拉菜单中选择或者手动填充。\n\n\ [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/appendix",
"title": "DolphinScheduler任务参数附录",
"location": [
@@ -15962,7 +15962,7 @@
{
"content": "Shell\n综述\nShell 任务类型，用于创建 Shell 类型的任务并执行一系列的 Shell 脚本。worker 执行该任务的时候，会生成一个临时 shell 脚本，并使用与租户同名的 linux 用户执行这个脚本。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入 DAG 编辑页面。\n工具栏中拖动 到画板中，即可完成创建。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n除上述默认参数，此任务没有其他参数\n\n任务样例\n简单打印一行文字\n该样例模拟了常见的简单任务，这些任务只需要简单的一两行命令就能运行起来。我们以打印一行日志为例，该任务仅会在日志文件中打印一行\n"This is a demo of shell task"\n\n使用自定义参数\n该样例模拟了自定义参数任务，为了更方便的复用已有的任务，�
��者面对动态的需求时，我们会使用变量保证脚本的复用性。本例中，我们先在自定义脚本\n [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/shell",
"title": "Shell",
"location": [
@@ -15974,7 +15974,7 @@
{
"content": "子流程节点\n综述\n子流程节点，就是把外部的某个工作流定义当做一个节点去执行。\n创建任务\n\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击”创建工作流”按钮，进入 DAG 编辑页面：\n\n\n拖动工具栏的 任务节点到画板中。\n\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n子节点\n是选择子流程的工作流定义，右上角进入该子节点可以跳转到所选子流程的工作流定义\n\n\n\n任务样例\n该样例模拟了常见的任务类型，这里我们使用子结点任务调用 Shell 打印出 ”hello world“。即将一个 shell 任务当作子结点来执行。\n创建 shell 任务\n创建一个 shell 任务，用于打印 “hello”。并为该工作流定义为 test_dag01。\n\n创建 sub_process 任务\n在使用 sub_process 的过程中，需要创建所需
的子结点任务，也就是我们第一步所创建的 s [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/sub-process",
"title": "子流程节点",
"location": [
@@ -15986,7 +15986,7 @@
{
"content": "Dependent 节点\n综述\nDependent 节点，就是依赖检查节点。比如 A 流程依赖昨天的 B 流程执行成功，依赖节点会去检查 B 流程在昨天是否有执行成功的实例。\n创建任务\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n此任务除上述链接中的默认参数外无其他参数。\n\n任务样例\nDependent 节点提供了逻辑判断功能，可以按照逻辑来检测所依赖节点的执行情况。\n例如，A 流程为周报任务，B、C 流程为天任务，A 任务需要 B、C 任务在上周的每一天都执行成功，如图示：\n\n例如，A 流程为周报任务，B、C 流程为天任务，A 任务需要 B 或 C 任务在上周的每一天都执行成功，如图示：\n\n�
��如，周报 A 同时还需要自身在上周二执行成功：\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/dependent",
"title": "Dependent 节点",
"location": [
@@ -15998,7 +15998,7 @@
{
"content": "存储过程节点\n\n根据选择的数据源，执行存储过程。\n\n\n拖动工具栏中的PROCEDURE任务节点到画板中，如下图所示：\n\n\n \n \n\n前提：在该数据库里面创建存储过程，如：\n\nCREATE PROCEDURE dolphinscheduler.test(in in1 INT, out out1 INT)\nbegin\n\tset out1=in1;\nEND\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n数据源\n存储过程的数据源类型支持MySQL、POSTGRESQL、ORACLE，选择对应的数据源\n\n\nSQL Statement\n调用存储过程，如 call test(${in1},${out1});\n\n\n自定义参数\n存储过程的自定义参数类型支持IN、OUT两种，数据类型支持VARCHAR、INTEGER、LONG、FLOAT、DOUBLE、DATE、TIME、TIMESTAMP、 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/stored-procedure",
"title": "存储过程节点",
"location": [
@@ -16010,7 +16010,7 @@
{
"content": "SQL\n综述\nSQL任务类型，用于连接数据库并执行相应SQL。\n创建数据源\n可参考 数据源配置 数据源中心。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入DAG编辑页面。\n工具栏中拖动 到画板中，选择需要连接的数据源，即可完成创建。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n数据源：选择对应的数据源\nsql类型：支持查询和非查询两种。\n查询：支持 DML select 类型的命令，是有结果集返回的，可以指定邮件通知为表格、附件或表格附件三种模板；\n非查询：支持 DDL全部命令 和 DML update、delete、insert 三种类型的命令；\n默认采用;\\n作为SQL分隔符,拆分成多段SQL语句执行。Hive的JDBC不支持一次执行多段SQL语句，请不要使用;\\n。\nsql参数：输入参数格式为key1=value
1;key2=value2…\nsql语句：SQL语句\nUDF函数：对于HI [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/sql",
"title": "SQL",
"location": [
@@ -16022,7 +16022,7 @@
{
"content": "SPARK节点\n综述\nSpark 任务类型用于执行 Spark 应用。对于 Spark 节点，worker 支持两个不同类型的 spark 命令提交任务：\n(1) spark submit 方式提交任务。更多详情查看 spark-submit。\n(2) spark sql 方式提交任务。更多详情查看 spark sql。\n创建任务\n\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击”创建工作流”按钮，进入 DAG 编辑页面：\n\n\n拖动工具栏的 任务节点到画板中。\n\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n程序类型：支持 Java、Scala、Python 和 SQL 四种语言。\nSpark 版本：支持 Spark1 和 Spark2。\n主函数的 Class：Spark 程序的入口 Main class 的全路径。\n主程序包：执行 Spark 程序的 jar 包（通过资源中心上传）。\nSQL脚本：Spark sql 运行的 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/spark",
"title": "SPARK节点",
"location": [
@@ -16034,7 +16034,7 @@
{
"content": "MapReduce(MR) 节点\n综述\nMapReduce(MR) 任务类型，用于执行 MapReduce 程序。对于 MapReduce 节点，worker 会通过使用 Hadoop 命令 hadoop jar 的方式提交任务。更多详情查看 Hadoop Command Manual。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入 DAG 编辑页面。\n拖动工具栏中的 任务节点到画板中，如下图所示：\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\nJAVA/SCALA 程序\n\n\n\n任务参数\n描述\n\n\n\n\n程序类型\n选择 JAVA/SCALA 语言\n\n\n主函数的 Class\n是 MapReduce 程序的入口 Main Class 的全路径\n\n\n主程序包\n执行 MapReduce 程序的 jar 包\n\n\n任务名称（选填）\nMapReduce 任务名称\n\n\n命令行参 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/map-reduce",
"title": "MapReduce(MR) 节点",
"location": [
@@ -16046,7 +16046,7 @@
{
"content": "Python 节点\n综述\nPython 任务类型，用于创建 Python 类型的任务并执行一系列的 Python 脚本。worker 执行该任务的时候，会生成一个临时python脚本，\n并使用与租户同名的 linux 用户执行这个脚本。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入DAG编辑页面。\n工具栏中拖动 到画板中，即可完成创建。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n脚本\n用户开发的PYTHON程序\n\n\n自定义参数\n是PYTHON局部的用户自定义参数，会替换脚本中以${变量}的内容\n\n\n\n任务样例\n简单打印一行文字\n该样例模拟了常见的简单任务，这些任务只需要简单的一两行命令就能运行起来。我们以打印一行日志为例，该任务仅会在日志文件中打印一行\n"This i
s a demo of python task" [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/python",
"title": "Python 节点",
"location": [
@@ -16058,7 +16058,7 @@
{
"content": "Flink节点\n综述\nFlink 任务类型，用于执行 Flink 程序。对于 Flink 节点：\n\n\n当程序类型为 Java、Scala 或 Python 时，worker 使用 Flink 命令提交任务 flink run。更多详情查看 flink cli 。\n\n\n当程序类型为 SQL 时，worker 使用sql-client.sh 提交任务。更多详情查看 flink sql client 。\n\n\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n程序类型\n支持 Java、Scala、 Python 和 SQL 四种语言\n\n\n主函数的 Class\nFlink 程序的入口 Main Class 的全路径\n\n\n主程序包\n执行 Flink 程序的 jar 包 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/flink",
"title": "Flink节点",
"location": [
@@ -16070,7 +16070,7 @@
{
"content": "HTTP 节点\n综述\n该节点用于执行 http 类型的任务，例如常见的 POST、GET 等请求类型，此外还支持 http 请求校验等功能。\n创建任务\n\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击”创建工作流”按钮，进入 DAG 编辑页面：\n\n\n拖动工具栏的 任务节点到画板中。\n\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n请求地址\nhttp 请求 URL\n\n\n请求类型\n支持 GET、POST、HEAD、PUT、DELETE\n\n\n请求参数\n支持 Parameter、Body、Headers\n\n\n校验条件\n支持默认响应码、自定义响应码、内容包含、内容不包含\n\n\n校验内容\n当校验条件选择自定义响应码、内容包含、内容不包含时，需填写校验内容\n\n\n自定义参数\n是 http 局部的用户自定义参数，会替换脚本中以 ${变量} 的内容\n\n\n\n任务 [.
..]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/http",
"title": "HTTP 节点",
"location": [
@@ -16082,7 +16082,7 @@
{
"content": "DATAX 节点\n综述\nDataX 任务类型，用于执行 DataX 程序。对于 DataX 节点，worker 会通过执行 ${DATAX_HOME}/bin/datax.py 来解析传入的 json 文件。\n创建任务\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\njson\nDataX 同步的 json 配置文件\n\n\n资源\n在使用自定义json中如果集群开启了kerberos认证后，datax读取或者写入hdfs、hbase等插件时需要使用相关的keytab，xml文件等，则可使用改选项。资源中心-文件管理上传或创建的文件\n\n\n自定义参数\nsql 任务类型，而存储过程是自定义参数顺序的给方法设置值自定义参数类型和数据类型同存储过程任务类型一样。区别在
于SQ [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/datax",
"title": "DATAX 节点",
"location": [
@@ -16094,7 +16094,7 @@
{
"content": "Pigeon\nPigeon任务类型是通过调用远程websocket服务，实现远程任务的触发，状态、日志的获取，是 DolphinScheduler 通用远程 websocket 服务调用任务\n创建任务\n拖动工具栏中的任务节点到画板中即能完成任务创建\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n目标任务名\n输入Pigeon任务的目标任务名称\n\n\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/pigeon",
"title": "Pigeon",
"location": [
@@ -16106,7 +16106,7 @@
{
"content": "Conditions 节点\nConditions 是一个条件节点，根据上游任务运行状态，判断应该运行哪个下游任务。截止目前 Conditions 支持多个上游任务，但只支持两个下游任务。当上游任务数超过一个时，可以通过且以及或操作符实现复杂上游依赖\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏中的任务节点到画板中。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n下游任务选择\n根据前置任务的状态来跳转到对应的分支：成功分支 - 当上游运行成功时，运行成功选择的分支；失败分支 - 当上游运行失败时，运行失败选择的分支\n\n\n上游条件选择\n可以为 Conditions 任务选择一个或多个上游任务：增加上游依赖 - 通过选择第一个�
��数选择对应的任务名称，通过第二个参数选择触发的 Conditions 任务的状态；上游任务关系选择 - 当有多个上游任务时，可 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/conditions",
"title": "Conditions 节点",
"location": [
@@ -16118,7 +16118,7 @@
{
"content": "Switch\nSwitch 是一个条件判断节点，依据全局变量的值和用户所编写的表达式判断结果执行对应分支。\n注意使用 javax.script.ScriptEngine.eval 执行表达式。\n创建任务\n点击项目管理 -> 项目名称 -> 工作流定义，点击"创建工作流"按钮，进入 DAG 编辑页面。\n拖动工具栏中的 任务节点到画板中即能完成任务创建。\n注意 switch 任务创建后，要先配置上下游，才能配置任务分支的参数。\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n条件\n可以为 switch 任务配置多个条件，当条件满足时，就会执行指定的分支，可以配置多个不同的条件来满足不同的业务，使用字符串判断时需要使用""\n\n\n分支流转\n默认的流转内容，当条件中的内容为全部不符合要求时，则运行分支�
�转中指定的分支\n\n\n\n任务样例\n这里使用一个 switch [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/switch",
"title": "Switch",
"location": [
@@ -16130,7 +16130,7 @@
{
"content": "Apache SeaTunnel\n综述\nSeaTunnel 任务类型，用于创建并执行 SeaTunnel 类型任务。worker 执行该任务的时候，会通过 start-seatunnel-spark.sh 或 start-seatunnel-flink.sh 命令解析 config 文件。\n点击 这里 获取更多关于 Apache SeaTunnel 的信息。\n创建任务\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务参数\n\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n引擎：支持 FLINK 和 SPARK\n\n\nFLINK\n\n\n运行模型：支持 run 和 run-application 两种模式\n\n\n选项参数：用于添加 Flink 引擎本身参数，例如 -m yarn-cluster -ynm seatunnel\n\n\nSPARK\n\n\n部署 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/seatunnel",
"title": "Apache SeaTunnel",
"location": [
@@ -16142,7 +16142,7 @@
{
"content": "Amazon EMR\n综述\nAmazon EMR 任务类型，用于在AWS上操作EMR集群并执行计算任务。\n后台使用 aws-java-sdk 将JSON参数转换为任务对象，提交到AWS，目前支持两种程序类型：\n\nRUN_JOB_FLOW 使用 API_RunJobFlow 提交 RunJobFlowRequest 对象\nADD_JOB_FLOW_STEPS 使用 API_AddJobFlowSteps 提交 AddJobFlowStepsRequest 对象\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n程序类型\n选择程序类型，如果是RUN_JOB_FLOW，则需要填写jobFlowDefineJson，如果是ADD_JOB_FLOW_STEPS，则需要填写stepsDefineJson\n\n\njobFlowDefineJson\nRunJobFlowRequest 对象对应的JSON，详细JSON定义参见 A [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/emr",
"title": "Amazon EMR",
"location": [
@@ -16154,7 +16154,7 @@
{
"content": "Apache Zeppelin\n综述\nZeppelin任务类型，用于创建并执行Zeppelin类型任务。worker 执行该任务的时候，会通过Zeppelin Cient API触发Zeppelin Notebook Paragraph。\n点击这里 获取更多关于Apache Zeppelin Notebook的信息。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入DAG编辑页面。\n工具栏中拖动 到画板中，即可完成创建。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\nZeppelin Note ID\nZeppelin Note对应的唯一ID\n\n\nZeppelin Paragraph ID\nZeppelin Paragraph对应的唯一ID。如果你想一次性调度整个note，这一栏不填即可\n\n\nZeppelin Rest Endpoint\n您的Zepp [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/zeppelin",
"title": "Apache Zeppelin",
"location": [
@@ -16166,7 +16166,7 @@
{
"content": "Jupyter\n综述\nJupyter任务类型，用于创建并执行Jupyter类型任务。worker 执行该任务的时候，会通过papermill执行jupyter note。\n点击这里 获取更多关于papermill的信息。\nConda虚拟环境配置\n\n在common.properties配置conda.path，将其指向您的conda.sh。这里的conda应该是您用来管理您的 papermill和jupyter所在python环境的相同conda。\n点击 这里 获取更多关于conda的信息.\nconda.path默认设置为/opt/anaconda3/etc/profile.d/conda.sh。 如果您不清楚您的conda环境在哪里，只需要在命令行执行conda info | grep -i 'base environment'即可获得。\n\n\n注意：Jupyter任务插件使用source命令激活conda环境，\n如果您的租户没有source命令使用权限，Jupyter任务插件将无法使用。\n\nPython依赖管理 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/jupyter",
"title": "Jupyter",
"location": [
@@ -16178,7 +16178,7 @@
{
"content": "Hive CLI\n综述\n使用Hive Cli任务插件创建Hive Cli类型的任务执行SQL脚本语句或者SQL任务文件。\n执行任务的worker会通过hive -e命令执行hive SQL脚本语句或者通过hive -f命令执行资源中心中的hive SQL文件。\nHive CLI任务 VS 连接Hive数据源的SQL任务\n在DolphinScheduler中，我们有Hive CLI任务插件和使用Hive数据源的SQL插件提供用户在不同场景下使用，您可以根据需要进行选择。\n\nHive CLI任务插件直接连接HDFS和Hive Metastore来执行hive类型的任务，所以需要能够访问到对应的服务。\n执行任务的worker节点需要有相应的Hive jar包以及Hive和HDFS的配置文件。\n但是在生产调度中，Hive CLI任务插件能够提供更可靠的稳定性。\n使用Hive数据源的SQL插件不需要您在worker节点上有相应的Hive jar包以及Hive和HDFS的配置文件，而且支持 Kerberos认证。\n但是在生产调度 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/hive-cli",
"title": "Hive CLI",
"location": [
@@ -16190,7 +16190,7 @@
{
"content": "Kubernetes\n综述\nkubernetes任务类型，用于在kubernetes上执行一个短时和批处理的任务。worker最终会通过使用kubernetes client提交任务。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入DAG编辑页面。\n工具栏中拖动 到画板中，选择需要连接的数据源，即可完成创建。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n命名空间\n选择kubernetes集群上存在的命名空间\n\n\n最小CPU\n任务在kubernetes上运行所需的最小CPU\n\n\n最小内存\n任务在kubernetes上运行所需的最小内存\n\n\n镜像\n镜像地址\n\n\n自定义参数\nkubernetes任务局部的用户自定义参数，自定义参数最终会通过环境变量形式存在于容器中，提供给kubernetes任务使用\n\n\n\n任务样例\n在 Dol [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/kubernetes",
"title": "Kubernetes",
"location": [
@@ -16202,7 +16202,7 @@
{
"content": "MLflow节点\n综述\nMLflow 是一个MLops领域一个优秀的开源项目， 用于管理机器学习的生命周期，包括实验、可再现性、部署和中心模型注册。\nMLflow 组件用于执行 MLflow 任务，目前包含Mlflow Projects，和MLflow Models。（Model Registry将在不就的将来支持）。\n\nMLflow Projects: 将代码打包，并可以运行到任务的平台上。\nMLflow Models: 在不同的服务环境中部署机器学习模型。\nModel Registry: 在一个中央存储库中存储、注释、发现和管理模型 (你也可以在你的MLflow project 里面自行注册模型)。\n\n目前 Mlflow 组件支持的和即将支持的内容如下中：\n\nMLflow Projects\n\nBasicAlgorithm: 基础算法，包含LogisticRegression， svm， lightgbm， xgboost\nAutoML: AutoML工具，包含autosklean， flaml\nCusto [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/mlflow",
"title": "MLflow节点",
"location": [
@@ -16214,7 +16214,7 @@
{
"content": "OpenMLDB 节点\n综述\nOpenMLDB 是一个优秀的开源机器学习数据库，提供生产级数据及特征开发全栈解决方案。\nOpenMLDB任务组件可以连接OpenMLDB集群执行任务。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务样例\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\nzookeeper地址\nOpenMLDB集群连接地址中的zookeeper地址, e.g. 127.0.0.1:2181\n\n\nzookeeper路径\nOpenMLDB集群连接地址中的zookeeper路径, e.g. /openmldb\n\n\n执行模式\n初始执行模式（离线/在线），你可以在sql语句中随时切换\n\n\nSQL语句\nSQL语句\n\n\n\n下面有几个例子：\n导入数据\n\n我们使用LOAD DATA语句导入数据到Open [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/openmldb",
"title": "OpenMLDB 节点",
"location": [
@@ -16226,7 +16226,7 @@
{
"content": "DVC节点\n综述\nDVC（Data Version Control） 是一个MLops领域一个优秀的开机器学习版本管理系统。\nDVC 组件用于在DS上使用DVC的数据版本管理功能，帮助用户简易地进行数据的版本管理。组件提供如下三个功能：\n\nInit DVC: 将git仓库初始化为DVC仓库，并绑定存储数据的地址用于存储实际的数据。\nUpload: 将特定数据添加或者更新到仓库中，并记录版本号。\nDownload: 从仓库中下载特定版本的数据。\n\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务样例\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\nDVC任务类型\n可以选择 Upload、Download、Init DVC\n\n\nDVC仓库\n任务执行时关联的仓库地址\n\n\n\nInit DVC\n将git仓�
�初始化为DV [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/dvc",
"title": "DVC节点",
"location": [
@@ -16238,7 +16238,7 @@
{
"content": "Dinky\nOverview\nDinky任务类型，用于创建并执行Dinky类型任务以支撑一站式的开发、调试、运维 FlinkSQL、Flink Jar、SQL。worker 执行该任务的时候，会通过Dinky API触发Dinky 的作业。\n点击这里 获取更多关于Dinky的信息。\nCreate Task\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入DAG编辑页面。\n工具栏中拖动 到画板中，即可完成创建。\n\nTask Parameter\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\nDinky 地址\nDinky 服务的 url。\n\n\nDinky 任务 ID\nDinky 作业对应的唯一ID。\n\n\n上线作业\n指定当前 Dinky 作业是否上线，如果是，则该被提交的作业只能处于已发布且当前无对应的 Flink Job 实例在运行才可提交成功。\n\n\n\nTask Ex [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/dinky",
"title": "Dinky",
"location": [
@@ -16250,7 +16250,7 @@
{
"content": "SageMaker 节点\n综述\nAmazon SageMaker 是一个云机器学习平台。 提供了完整的基础设施，工具和工作流来帮助用户可以创建、训练和发布机器学习模型。\nAmazon SageMaker Model Building Pipelines 是一个可以直接使用SageMaker各种集成的机器学习管道构建工具，用户可以使用使用 Amazon SageMaker Pipeline 来构建端到端的机器学习系统。\n对于使用大数据与人工智能的用户，SageMaker 任务组件帮助用户可以串联起大数据工作流与SagaMaker的使用场景。\nDolphinScheduler SageMaker 组件的功能:\n\n启动 SageMaker Pipeline Execution，并持续获取状态，直至Pipeline执行完成。\n\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务样例\n\n默认参数说明请参考DolphinSched [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/sagemaker",
"title": "SageMaker 节点",
"location": [
@@ -16262,7 +16262,7 @@
{
"content": "ChunJun节点\n综述\nChunJun 任务类型，用于执行 ChunJun 程序。对于 ChunJun 节点，worker 会通过执行 ${CHUNJUN_HOME}/bin/start-chunjun 来解析传入的 json 文件。\n创建任务\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n自定义模板\n自定义 ChunJun 节点的 json 配置文件内容，当前支持此种方式。\n\n\njson\nChunJun 同步的 json 配置文件。\n\n\n自定义参数\n用户自定义参数，会替换脚本中以 ${变量} 的内容。\n\n\n部署方式\n执行ChunJun任务的方式，比如local，standalone等。\n\n\n选项参数\n支持 -confProp " [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/chunjun",
"title": "ChunJun节点",
"location": [
@@ -16274,7 +16274,7 @@
{
"content": "Pytorch 节点（试验版）\n综述\nPytorch 是一个的主流Python机器学习库。\n为了用户能够在DolphinScheduler中更方便的运行Pytorch项目，实现了Pytorch任务组件。主要提供便捷的python环境管理以及支持运行python项目。\n与Python任务组件不同，该组件允许用户快速使用已有python环境或者创建新的python环境（使用virtualenv或者conda）；支持运行Python项目（本地项目或者Git项目）而非只是python脚本。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务样例\n组件图示如下：\n\nPytorch参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n运行参数\n\n\n\n任务参数\n描述\n\n\n\n\npython脚本\n需要运行的python脚本文件入口\n\n\n脚本启动参数\n运行时的输入�
�数\ [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/task/pytorch",
"title": "Pytorch 节点（试验版）",
"location": [
@@ -16286,7 +16286,7 @@
{
"content": "内置参数\n基础内置参数\n\n 变量名声明方式含义\n \n system.biz.date\n ${system.biz.date}\n 日常调度实例定时的定时时间前一天，格式为 yyyyMMdd\n \n \n system.biz.curdate\n ${system.biz.curdate}\n 日常调度实例定时的定时时间，格式为 yyyyMMdd\n \n \n system.datetime\n ${system.datetime}\n 日常调度实例定时的定时时间，格式为 yyyyMMddHHmmss\n \n\n衍生内置参数\n\n\n支持代码中自定义变量名，声明方式：${变量名}。可以是引用 "系统参数"\n\n\n我们定义这种基准变量为 $[...] 格式的，$[yyyyMMddHHmmss] 是可以任意分解组合的，比如：$[yyyy [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/parameter/built-in",
"title": "内置参数",
"location": [
@@ -16298,7 +16298,7 @@
{
"content": "全局参数\n作用域\n全局参数是指针对整个工作流的所有任务节点都有效的参数，在工作流定义页面配置。\n使用方式\n具体的使用方式可结合实际的生产情况而定，这里演示为使用 Shell 任务打印出前一天的日期。\n创建 Shell 任务\n创建一个 Shell 任务，并在脚本内容中输入 echo ${dt}。此时 dt 则为我们需要声明的全局参数。如下图所示：\n\n保存工作流，并设置全局参数\n全局参数配置方式如下：在工作流定义页面，点击“设置全局”右边的加号，填写对应的变量名称和对应的值，保存即可。如下图所示：\n\n\n注：这里定义的 dt 参数可以被其它任一节点的局部参数引用。\n\n任务实例查看执行结果\n进入任务实例页面，可以通过查看日志，验证任务的执行结果，判断参数是否有效。\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/parameter/global",
"title": "全局参数",
"location": [
@@ -16310,7 +16310,7 @@
{
"content": "本地参数\n作用域\n在任务定义页面配置的参数，默认作用域仅限该任务，如果配置了参数传递则可将该参数作用到下游任务中。\n使用方式\n本地参数配置方式如下：在任务定义页面，点击“自定义参数”右边的加号，填写对应的变量名称和对应的值，保存即可。\n\n如果要在单个任务中使用参数，请参阅通过自定义参数使用\n如果要在任务中使用配置参数并在下游任务中使用它们：\n\n如果你只是想要简单使用，且不使用自定义参数, 请参阅 通过 setValue 和自定义参数 export 本地参数\n如果想要使用自定义参数, 请参阅 通过 setValue 和自定义参数 export 本地参数\n如果想要使用 Bash 参数, 请参阅 通过 setValue 和 Bash 环境变量参数 export 本地参数\n\n\n\n任务样例\n通过自定义参数使用\n本样例展示了如何使用本地参数，打印输出当前日期。创建一�
� Shell 任务，并编写脚本内容为 echo ${dt}。点击配置栏中的自定义参数，配置如下图所示：\n\n参数说明：\n\ndt：参数名\nIN：I [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/parameter/local",
"title": "本地参数",
"location": [
@@ -16322,7 +16322,7 @@
{
"content": "参数的引用\nDolphinScheduler 提供参数间相互引用的能力，包括：本地参数引用全局参数、上下游参数传递。因为有引用的存在，就涉及当参数名相同时，参数的优先级问题，详见参数优先级\n本地任务引用全局参数\n本地任务引用全局参数的前提是，你已经定义了全局参数，使用方式和本地参数中的使用方式类似，但是参数的值需要配置成全局参数中的 key。\n上游任务传递给下游任务\nDolphinScheduler 允许在任务间进行参数传递，目前传递方向仅支持上游单向传递给下游。目前支持这个特性的任务类型有：\n\nShell\nSQL\nProcedure\nPython\n\n当定义上游节点时，如果有需要将该节点的结果传递给有依赖关系的下游节点，需要在【当前节点设置】的【自定义参数】设置一个方向是 OUT 的变量。目前我们主要针对 SQL 和 SHELL 节点做了可以向下传递参数的
功能。\n上游传递的参数可以在下游节点中被更新，更新方法与设置参数相同。\n如果定义了同名的传递参数，上游节点的参数将被覆盖。\n\n注：若节点之间没有依赖关系， [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/parameter/context",
"title": "参数的引用",
"location": [
@@ -16334,7 +16334,7 @@
{
"content": "参数优先级\nDolphinScheduler 中所涉及的参数值的定义可能来自三种类型：\n\n全局参数：在工作流保存页面定义时定义的变量\n上游任务传递的参数：上游任务传递过来的参数\n本地参数：节点的自有变量，用户在“自定义参数”定义的变量，并且用户可以在工作流定义时定义该部分变量的值\n\n因为参数的值存在多个来源，当参数名相同时，就需要会存在参数优先级的问题。DolphinScheduler 参数的优先级从高到低为：本地参数 > 上游任务传递的参数 > 全局参数\n在上游任务传递的参数中，由于上游可能存在多个任务向下游传递参数，当上游传递的参数名称相同时：\n\n下游节点会优先使用值为非空的参数\n如果存在多个值为非空的参数，则按照上游任务的完成时间排序，选择完成时间最早的上游任务对应的参数\n\n例子\n下面例子向你展示�
��何使用任务参数传递的优先级问题\n1：先以 shell 节点解释第一种情况\n\n节点 【useParam】可以使用到节点【createParam】中设置的变量。而节点 【useParam】与节点【 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/parameter/priority",
"title": "参数优先级",
"location": [
@@ -16346,7 +16346,7 @@
{
"content": "MySQL 数据源\n\n\n数据源：选择 MYSQL\n数据源名称：输入数据源的名称\n描述：输入数据源的描述\nIP 主机名：输入连接 MySQL 的 IP\n端口：输入连接 MySQL 的端口\n用户名：设置连接 MySQL 的用户名\n密码：设置连接 MySQL 的密码\n数据库名：输入连接 MySQL 的数据库名称\nJdbc 连接参数：用于 MySQL 连接的参数设置，以 JSON 形式填写\n\n是否原生支持\n否，使用前需请参考 数据源配置 中的 "数据源中心" 章节激活数据源。\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/datasource/mysql",
"title": "MySQL 数据源",
"location": [
@@ -16358,7 +16358,7 @@
{
"content": "POSTGRESQL 数据源\n\n\n数据源：选择 POSTGRESQL\n数据源名称：输入数据源的名称\n描述：输入数据源的描述\nIP 主机名：输入连接 POSTGRESQL 的 IP\n端口：输入连接 POSTGRESQL 的端口\n用户名：设置连接 POSTGRESQL 的用户名\n密码：设置连接 POSTGRESQL 的密码\n数据库名：输入连接 POSTGRESQL 的数据库名称\nJdbc 连接参数：用于 POSTGRESQL 连接的参数设置，以 JSON 形式填写\n\n是否原生支持\n是，数据源不需要任务附加操作即可使用。\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/datasource/postgresql",
"title": "POSTGRESQL 数据源",
"location": [
@@ -16370,7 +16370,7 @@
{
"content": "HIVE数据源\n使用HiveServer2\n\n\n数据源：选择 HIVE\n数据源名称：输入数据源的名称\n描述：输入数据源的描述\nIP 主机名：输入连接 HIVE 的 IP\n端口：输入连接 HIVE 的端口\n用户名：设置连接 HIVE 的用户名\n密码：设置连接 HIVE 的密码\n数据库名：输入连接 HIVE 的数据库名称\nJdbc 连接参数：用于 HIVE 连接的参数设置，以 JSON 形式填写\n\n\n注意：如果您希望在同一个会话中执行多个 HIVE SQL，您可以修改配置文件 common.properties 中的配置，设置 support.hive.oneSession = true。\n这对运行 HIVE SQL 前设置环境变量的场景会很有帮助。参数 support.hive.oneSession 默认值为 false，多条 SQL 将在不同的会话中运行。\n\n使用 HiveServer2 HA Zookeeper\n\n注意：如果没有开启 kerberos,请保证参数 hadoop.security.a [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/datasource/hive",
"title": "HIVE数据源",
"location": [
@@ -16382,7 +16382,7 @@
{
"content": "Spark数据源\n\n\n数据源：选择 Spark\n数据源名称：输入数据源的名称\n描述：输入数据源的描述\nIP/主机名：输入连接Spark的IP\n端口：输入连接Spark的端口\n用户名：设置连接Spark的用户名\n密码：设置连接Spark的密码\n数据库名：输入连接Spark的数据库名称\nJdbc连接参数：用于Spark连接的参数设置，以JSON形式填写\n\n注意：如果开启了kerberos，则需要填写 Principal\n\n \n \n是否原生支持\n是，数据源不需要任务附加操作即可使用。\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/datasource/spark",
"title": "Spark数据源",
"location": [
@@ -16394,7 +16394,7 @@
{
"content": "AWS Athena 数据源\n\n\n数据源：选择 ATHENA\n数据源名称：输入数据源的名称\n描述：输入数据源的描述\n用户名：设置连接 AWS 的 access key\n密码：设置连接 AWS 的 secret access key\nAwsRegion: 设置连接 AWS 的区域\n数据库名：输入连接 ATHENA 的数据库名称\nJdbc 连接参数：用于 ATHENA 连接的参数设置，以 JSON 形式填写\n\n是否原生支持\n\n否，使用前需请参考 数据源配置 中的 "数据源中心" 章节激活数据源。\nJDBC驱动配置参考文档 athena-connect-with-jdbc\n驱动下载链接 SimbaAthenaJDBC-2.0.31.1000/AthenaJDBC42.jar\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/datasource/athena",
"title": "AWS Athena 数据源",
"location": [
@@ -16406,7 +16406,7 @@
{
"content": "如何创建告警插件以及告警组\n在 2.0.0 版本中，用户需要创建告警实例，在创建告警实例时，需要选择告警策略，有三个选项，成功发、失败发，以及成功和失败都发。在执行完工作流或任务时，如果触发告警，调用告警实例发送方法会进行逻辑判断，将告警实例与任务状态进行匹配，匹配则执行该告警实例发送逻辑，不匹配则过滤。创建完告警实例后，需要同告警组进行关联，一个告警组可以使用多个告警实例。\n告警模块支持场景如下：\n\n使用步骤如下：\n首先需要进入到安全中心，选择告警组管理，然后点击左侧的告警实例管理，然后创建一个告警实例，然后选择对应的告警插件，填写相关告警参数。\n然后选择告警组管理，创建告警组，选择相应的告警实例即可。\n\n\n\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/alert/alert_plugin_user_guide",
"title": "如何创建告警插件以及告警组",
"location": [
@@ -16418,7 +16418,7 @@
{
"content": "Email\n如果需要使用Email进行告警，请在告警实例管理中创建告警实例，并选择Email插件。\n下面显示了 Email 配置示例：:\n\n\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/alert/email",
"title": "Email",
"location": [
@@ -16430,7 +16430,7 @@
{
"content": "Telegram\n如果您需要使用 Telegram 进行告警，请在告警实例管理模块创建告警实例，选择 Telegram 插件。\nTelegram 的配置样例如下:\n\n参数配置:\n\nWebHook:\n\n\n使用 Telegram 的机器人，发送消息的 WebHook。\n\nbotToken\n创建 Telegram 的机器人，获取的访问令牌。\nchatId\n订阅的 Telegram 频道\nparseMode\n消息解析类型, 支持: txt、markdown、markdownV2、html\nEnableProxy\n开启代理\nProxy\n代理地址\nPort\n代理端口\nUser\n代理鉴权用户\nPassword\n代理鉴权密码\n\n\n注意：用户配置的 WebHook 需要能够接收和使用与 DolphinScheduler 构造的 HTTP POST 请求 BODY 相同的结构，JSON 结构如下：\n{\n "text": "[{\\"projectId\ [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/alert/telegram",
"title": "Telegram",
"location": [
@@ -16442,7 +16442,7 @@
{
"content": "钉钉\n如果您需要使用到钉钉进行告警，请在告警实例管理里创建告警实例，选择 DingTalk 插件。钉钉的配置样例如下:\n\n参数配置\n\n\nWebhook\n\n格式如下：https://oapi.dingtalk.com/robot/send?access_token=XXXXXX\n\n\n\nKeyword\n\n安全设置的自定义关键词\n\n\n\nSecret\n\n安全设置的加签\n\n\n\n消息类型\n\n支持 text 和 markdown 两种类型\n\n\n\n自定义机器人发送消息时，可以通过手机号码指定“被@人列表”。在“被@人列表”里面的人员收到该消息时，会有@消息提醒。免打扰会话仍然通知提醒，首屏出现“有人@你”\n\n@Mobiles\n\n\n被@人的手机号\n\n@UserIds\n被@人的用户userid\n@All\n是否@所有人\n\n\n钉钉自定义机器人接入开发文档\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/alert/dingtalk",
"title": "钉钉",
"location": [
@@ -16454,7 +16454,7 @@
{
"content": "企业微信\n如果您需要使用到企业微信进行告警，请在告警实例管理里创建告警实例，选择 WeChat 插件。企业微信的配置样例如下：\n\n发送类型\n其中send.type分别对应向企业微信自定义应用发送和向企业微信API创建的群聊发送消息。\n应用\n应用指将告警结果通过企业微信的自定义应用进行通知，支持向特定用户发送消息和对所有人发送消息。目前还不支持部门和标签，欢迎提PR贡献代码。\n下图是应用告警配置的示例:\n\n下图是应用``MARKDOWN告警消息的示例:\n\n下图是应用``TEXT告警消息的示例:\n\n前置\n向企业微信应用发送消息之前需要在企业微信中创建自定义应用，请在应用页面 进行创建,获取应用的AgentId并将可见范围设为根。\n向指定用户发消息\n企业微信应用支持向特定用户发送消息和对所有人发送消息，分别为使用|分隔多个userId和�
��用@all向所有人发送信息。\n获取用户的userId请参考官方文档根据手机号获取userId。\n下图是获取userId接口的示例:\n\n参考文档\n应用：https://w [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/alert/enterprise-wechat",
"title": "企业微信",
"location": [
@@ -16466,7 +16466,7 @@
{
"content": "WebexTeams\n如果您需要使用到Webex Teams进行告警，请在告警实例管理里创建告警实例，选择 WebexTeams 插件。\n你可以选择机器人私聊通知或聊天室通知。\nWebexTeams的配置样例如下:\n\n参数配置\n\n\nbotAccessToken\n\n在创建机器人时，获得的访问令牌\n\n\n\nroomID\n\n接受消息的room ID(只支持一个ID)\n\n\n\ntoPersonId\n\n接受消息的用户ID(只支持一个ID)\n\n\n\ntoPersonEmail\n\n接受消息的用户邮箱(只支持一个邮箱)\n\n\n\natSomeoneInRoom\n\n如果消息目的地为room，被@人的用户邮箱，多个邮箱用英文逗号分隔\n\n\n\ndestination\n\n消息目的地，一条消息只支持一个目的地\n\n\n\n创建一个机器人\n访问官网My-Apps来创建一个机器人，点击Create a New APP 然后选择 Create a Bot，填入机器人信息后获取bot username [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/alert/enterprise-webexteams",
"title": "WebexTeams",
"location": [
@@ -16478,7 +16478,7 @@
{
"content": "Script脚本\n如果您需要使用到Shell脚本进行告警，请在告警实例管理里创建告警实例，选择Script插件。Script的配置样例如下:\n\n参数配置\n\n\n自定义参数\n\n用户自定义的参数将被传入脚本执行\n\n\n\n脚本路径\n\n脚本在服务器上的文件位置\n\n\n\n脚本类型\n\n支持Shell脚本\n\n\n\n注意： 请注意脚本的读写权限与执行租户的关系\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/alert/script",
"title": "Script脚本",
"location": [
@@ -16490,7 +16490,7 @@
{
"content": "HTTP告警\n如果您需要使用到Http（GET或POST）进行告警，请在告警实例管理里创建告警实例，选择Http插件。\n参数配置\n\n\nURL\n\n访问的Http连接URL,需要包含协议、Host、路径，如果是GET方法可以添加参数\n\n\n\n请求方式\n\n选择该请求为POST或GET方法\n\n\n\n请求头\n\nHttp请求的完整请求头，以JSON为格式\n\n\n\n请求体\n\nHttp请求的完整请求体，以JSON为格式，GET方法不需要写该参数\n\n\n\n内容字段\n\n放置本次告警告警信息的字段名称\n\n\n\n发送类型\n其中Request Type分别对应使用POST方法和GET方法进行Http告警。\nGET Http告警\nGET Http告警指将告警结果作为参数通过Http GET方法进行请求。\n下图是GET告警配置的示例:\n\nPOST Http告警\nPOST Http告警指将告警结果作为BODY参数通过HttpPOST方法进行请求。\n下图是POST告警配置的示例:\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/alert/http",
"title": "HTTP告警",
"location": [
@@ -16502,7 +16502,7 @@
{
"content": "飞书\n如果您需要使用到飞书进行告警，请在告警实例管理里创建告警实例，选择 Feishu 插件。飞书的配置样例如下:\n\n参数配置\n\n\nWebhook\n\n复制机器人的webhook地址,如下图所示：\n\n\n\n\n飞书：如何在群组中使用机器人？\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/alert/feishu",
"title": "飞书",
"location": [
@@ -16514,7 +16514,7 @@
{
"content": "资源中心简介\n资源中心通常用于上传文件、UDF 函数和任务组管理。 对于 standalone 环境，可以选择本地文件目录作为上传文件夹（此操作不需要Hadoop部署）。当然，你也可以\n选择上传到 Hadoop 或者 MinIO 集群。 在这种情况下，您需要有 Hadoop（2.6+）或 MinION 等相关环境。\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/resource/intro",
"title": "资源中心简介",
"location": [
@@ -16526,7 +16526,7 @@
{
"content": "资源中心配置详情\n\n资源中心通常用于上传文件、UDF 函数，以及任务组管理等操作。\n资源中心可以对接分布式的文件存储系统，如Hadoop（2.6+）或者MinIO集群，也可以对接远端的对象存储，如AWS S3或者阿里云 OSS等。\n资源中心也可以直接对接本地文件系统。在单机模式下，您无需依赖Hadoop或S3一类的外部存储系统，可以方便地对接本地文件系统进行体验。\n除此之外，对于集群模式下的部署，您可以通过使用S3FS-FUSE将S3挂载到本地，或者使用JINDO-FUSE将OSS挂载到本地等，再用资源中心对接本地文件系统方式来操作远端对象存储中的文件。\n\n对接本地文件系统\n配置 common.properties 文件\n如果您以 集群 模式或者 伪集群 模式部署DolphinScheduler，您需要对以下路径的文件进行配置：api-server/conf/common.properties 和 worker-server/conf/common.properties；\n若�
��以 单机 模式部署DolphinSched [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/resource/configuration",
"title": "资源中心配置详情",
"location": [
@@ -16538,7 +16538,7 @@
{
"content": "文件管理\n当在调度过程中需要使用到第三方的 jar 或者用户需要自定义脚本的情况，可以通过在该页面完成相关操作。可创建的文件类型包括：txt/log/sh/conf/py/java 等。并且可以对文件进行编辑、重命名、下载和删除等操作。\n\n注意：\n\n当您以admin身份等入并操作文件时，需要先给admin设置租户\n\n\n基础操作\n\n创建文件\n文件格式支持以下几种类型：txt、log、sh、conf、cfg、py、java、sql、xml、hql、properties\n\n上传文件\n上传文件：点击"上传文件"按钮进行上传，将文件拖拽到上传区域，文件名会自动以上传的文件名称补全\n\n文件查看\n对可查看的文件类型，点击文件名称，可查看文件详情\n\n下载文件\n点击文件列表的"下载"按钮下载文件或者在文件详情中点击右上角"下载"按钮下载文件\n文件重命名\n\n删除文件\n文件�
�表->点击"删除"按钮，删除指定文件\n重新上传文件\ [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/resource/file-manage",
"title": "文件管理",
"location": [
@@ -16550,7 +16550,7 @@
{
"content": "UDF 管理\n\n资源管理和文件管理功能类似，不同之处是资源管理是上传的 UDF 函数，文件管理上传的是用户程序，脚本及配置文件。\n主要包括以下操作：重命名、下载、删除等。\n\n\n上传 UDF 资源\n\n\n和上传文件相同。\n\n函数管理\n\n\n创建 UDF 函数\n\n点击“创建 UDF 函数”，输入 UDF 函数参数，选择udf资源，点击“提交”，创建 UDF 函数。\n目前只支持 HIVE 的临时 UDF 函数\n\n\n\n\nUDF 函数名称：输入 UDF 函数时的名称\n包名类名：输入 UDF 函数的全路径\nUDF 资源：设置创建的 UDF 对应的资源文件\n\n\n任务样例\n编写 UDF 函数\n用户可以根据实际生产需求，自定义想要的 UDF 函数。这里编写一个在任意字符串的末尾添加 "HelloWorld" 的函数。如下图所示：\n\n配置 UDF 函数\n配置 UDF 函数前，需要先通过资源管理上传所需的函数 jar 包。然后进�
�函数管理，配置相关信息即可。如下图所示：\n\n使用 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/resource/udf-manage",
"title": "UDF 管理",
"location": [
@@ -16562,7 +16562,7 @@
{
"content": "任务组管理\n任务组主要用于控制任务实例并发，旨在控制其他资源的压力（也可以控制 Hadoop 集群压力，不过集群会有队列管控）。您可在新建任务定义时，可配置对应的任务组，并配置任务在任务组内运行的优先级。\n任务组配置\n新建任务组\n\n用户点击【资源中心】-【任务组管理】-【任务组配置】-新建任务组\n\n您需要输入图片中信息，其中\n【任务组名称】：任务组在被使用时显示的名称\n【项目名称】：任务组作用的项目，该项为非必选项，如果不选择，则整个系统所有项目均可使用该任务组。\n【资源容量】：允许任务实例并发的最大数量\n查看任务组队列\n\n点击按钮查看任务组使用信息\n\n任务组的使用\n注：任务组的使用适用于由 worker 执行的任务，例如【switch】节点、【condition】节点、【sub_process】等由 master 负责执行�
�节点类型不受任务组控制。\n我们以 shell 节点为例：\n\n关于任务组的配置，您需要做的只需要配置红色框内的部分，其中：\n【任务组名称】：任务组配置页面显示的任务组名称，这里只 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/resource/task-group",
"title": "任务组管理",
"location": [
@@ -16574,7 +16574,7 @@
{
"content": "监控中心\n服务管理\n\n服务管理主要是对系统中的各个服务的健康状况和基本信息的监控和显示\n\nMaster\n\n主要是 master 的相关信息。\n\n\nWorker\n\n主要是 worker 的相关信息。\n\n\nDatabase\n\n主要是 DB 的健康状况\n\n\n统计管理\nStatistics\n\n\n待执行命令数：统计 t_ds_command 表的数据\n执行失败的命令数：统计 t_ds_error_command 表的数据\n待运行任务数：统计 Zookeeper 中 task_queue 的数据\n待杀死任务数：统计 Zookeeper 中 task_kill 的数据\n\n审计日志\n审计日志的记录提供了有关谁访问了系统，以及他或她在给定时间段内执行了哪些操作的信息，他对于维护安全都很有用。\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/monitor",
"title": "监控中心",
"location": [
@@ -16585,7 +16585,7 @@
{
"content": "安全中心（权限系统）\n\n安全中心只有管理员账户才有权限操作，分别有队列管理、租户管理、用户管理、告警组管理、worker分组管理、令牌管理等功能，在用户管理模块可以对资源、数据源、项目等授权\n管理员登录，默认用户名/密码：admin/dolphinscheduler123\n\n创建队列\n\n队列是在执行 spark、mapreduce 等程序，需要用到“队列”参数时使用的。\n管理员进入安全中心 -> 队列管理页面，点击“创建队列”按钮，创建队列。\n\n\n添加租户\n\n租户对应的是 Linux 的用户，用于 worker 提交作业所使用的用户。如果 linux 没有这个用户，则会导致任务运行失败。你可以通过修改 worker.properties 配置文件中参数 worker.tenant.auto.create=true 实现当 linux 用户不存在时自动创建该用户。worker.tenant.auto.create=true 参数会要求 worker 可以免密运行 sudo 命令\n租户编�
�：租户编码是 Lin [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/security",
"title": "安全中心（权限系统）",
"location": [
@@ -16596,7 +16596,7 @@
{
"content": "指标（Metrics）使用指南\nApache DolphinScheduler通过向外透出指标来提高系统的监控告警能力。 我们使用Micrometer作为指标采集和透出框架。\n目前，我们只支持Prometheus Exporter，但是多样化的Exporter将会持续贡献给用户。\n快速上手\n\n我们提供Apache DolphinScheduler standalone 模式下采集并透出指标的能力，提供用户轻松快速的体验。\n当您在standalone模式下触发任务后，您可通过链接 http://localhost:12345/dolphinscheduler/actuator/metrics 访问生成的metrics列表。\n当您在standalone模式下触发任务后，您可通过链接 http://localhost:12345/dolphinscheduler/actuator/prometheus 访问prometheus格式指标。\n为了给您提供一个一站式的Prometheus + Grafana体验, 我们已经为您准备好了 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/metrics/metrics",
"title": "指标（Metrics）使用指南",
"location": [
@@ -16608,7 +16608,7 @@
{
"content": "概述\n任务类型介绍\n数据质量任务是用于检查数据在集成、处理过程中的数据准确性。本版本的数据质量任务包括单表检查、单表自定义SQL检查、多表准确性以及两表值比对。数据质量任务的运行环境为Spark2.4.0，其他版本尚未进行过验证，用户可自行验证。\n\n数据质量任务的执行逻辑如下：\n\n\n用户在界面定义任务，用户输入值保存在TaskParam中\n运行任务时，Master会解析TaskParam，封装DataQualityTask所需要的参数下发至Worker。 Worker运行数据质量任务，数据质量任务在运行结束之后将统计结果写入到指定的存储引擎中，当前数据质量任务结果存储在dolphinscheduler的t_ds_dq_execute_result表中\nWorker发送任务结果给Master，Master收到TaskResponse之后会判断任务类型是否为DataQualityTask，如果是的话会根据taskInstanceId从t_ds_dq_execute_result中读取相应的结果，�
�后根据用户配置好的检查方式， [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/data-quality",
"title": "概述",
"location": [
@@ -16619,7 +16619,7 @@
{
"content": "不向前兼容的更新\n本文档记录了各版本之间不兼容的更新内容。在升级到相关版本前，请检查本文档。\ndev\n\nRemove the spark version of spark task (#11860).\n\n3.0.0\n\nCopy and import workflow without 'copy' suffix #10607\nUse semicolon as default sql segment separator #10869\n\n3.1.1\n\nChange the default unix shell executor from sh to bash (#12180).\n\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/upgrade/incompatible",
"title": "不向前兼容的更新",
"location": [
@@ -16631,7 +16631,7 @@
{
"content": "DolphinScheduler 升级\n准备工作\n检查不向前兼容的更改\n在升级之前，您应该检查 incompatible change，因为一些不兼容的更改可能会破坏您当前的功能。\n备份上一版本文件和数据库\n为了防止操作错误导致数据丢失，建议升级之前备份数据，备份方法请结合你数据库的情况来定\n下载新版本的安装包\n在下载页面下载最新版本的二进制安装包，并将二进制包放到与当前 dolphinscheduler 服务不一样的路径中，以下升级操作都需要在新版本的目录进行。\n升级步骤\n停止 dolphinscheduler 所有服务\n根据你部署方式停止 dolphinscheduler 的所有服务，如果你是通过 集群部署 来部署你的 dolphinscheduler 的话，可以通过 sh ./script/stop-all.sh 停止全部服务。\n数据库升级\n修改 ./bin/env/dolphinscheduler_env.sh 中的如下配置（{user}和{password}改成你数据库的用户名和密码），�
�后运行升级脚本。 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/upgrade/upgrade",
"title": "DolphinScheduler 升级",
"location": [
@@ -16643,7 +16643,7 @@
{
"content": "DolphinScheduler扩容/缩容 文档\n1. DolphinScheduler扩容文档\n本文扩容是针对现有的DolphinScheduler集群添加新的master或者worker节点的操作说明.\n注意： 一台物理机上不能存在多个master服务进程或者worker服务进程.\n 如果扩容master或者worker节点所在的物理机已经安装了调度的服务,请直接跳到 [1.4.修改配置]. 编辑 ** 所有 ** 节点上的配置文件 `conf/config/install_config.conf`. 新增masters或者workers参数,重启调度集群即可.\n\n1.1. 基础软件安装(必装项请自行安装)\n\n[必装] JDK (1.8+) : 必装，请安装好后在/etc/profile下配置 JAVA_HOME 及 PATH 变量\n[可选] 如果扩容的是worker类型的节点,需要考虑是否要安装外部客户端,比如Hadoop、Hive、Spark 的Client.\n\n注意：DolphinSchedul [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/expansion-reduction",
"title": "DolphinScheduler扩容/缩容 文档",
"location": [
@@ -16654,7 +16654,7 @@
{
"content": "Standalone极速体验版\nStandalone 仅适用于 DolphinScheduler 的快速体验.\n如果你是新手，想要体验 DolphinScheduler 的功能，推荐使用Standalone方式体检。如果你想体验更完整的功能，或者更大的任务量，推荐使用伪集群部署。如果你是在生产中使用，推荐使用集群部署或者kubernetes\n\n注意: Standalone仅建议20个以下工作流使用，因为其采用内存式的H2 Database, Zookeeper Testing Server，任务过多可能导致不稳定，并且如果重启或者停止standalone-server会导致内存中数据库里的数据清空。\n如果您要连接外部数据库，比如mysql或者postgresql，请看配置数据库\n\n前置准备工作\n\nJDK：下载JDK (1.8+)，安装并配置 JAVA_HOME 环境变量，并将其下的 bin 目录追加到 PATH 环境变量中。如果你的环境中已存在，可以跳过这步。\n二进制包：在下载页面下载 DolphinScheduler [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/installation/standalone",
"title": "Standalone极速体验版",
"location": [
@@ -16665,7 +16665,7 @@
{
"content": "伪集群部署\n伪集群部署目的是在单台机器部署 DolphinScheduler 服务，该模式下master、worker、api server 都在同一台机器上\n如果你是新手，想要体验 DolphinScheduler 的功能，推荐使用Standalone方式体检。如果你想体验更完整的功能，或者更大的任务量，推荐使用伪集群部署。如果你是在生产中使用，推荐使用集群部署或者kubernetes\n前置准备工作\n伪分布式部署 DolphinScheduler 需要有外部软件的支持\n\nJDK：下载JDK (1.8+)，安装并配置 JAVA_HOME 环境变量，并将其下的 bin 目录追加到 PATH 环境变量中。如果你的环境中已存在，可以跳过这步。\n二进制包：在下载页面下载 DolphinScheduler 二进制包\n数据库：PostgreSQL (8.2.15+) 或者 MySQL (5.7+)，两者任选其一即可，如 MySQL 则需要 JDBC Driver 8.0.16\n注册中心：ZooKeeper (3.4.6+)，下载地址 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/installation/pseudo-cluster",
"title": "伪集群部署",
"location": [
@@ -16676,7 +16676,7 @@
{
"content": "集群部署(Cluster)\n集群部署目的是在多台机器部署 DolphinScheduler 服务，用于运行大量任务情况。\n如果你是新手，想要体验 DolphinScheduler 的功能，推荐使用Standalone方式体检。如果你想体验更完整的功能，或者更大的任务量，推荐使用伪集群部署。如果你是在生产中使用，推荐使用集群部署或者kubernetes\n部署步骤\n集群部署(Cluster)使用的脚本和配置文件与伪集群部署中的配置一样，所以所需要的步骤也与伪集群部署大致一样。区别就是伪集群部署针对的是一台机器，而集群部署(Cluster)需要针对多台机器，且两者“修改相关配置”步骤区别较大\n前置准备工作 && 准备 DolphinScheduler 启动环境\n其中除了伪集群部署中的“前置准备工作”，“准备启动环境”除了“启动zookeeper”以及“初始化数据库”外，别的都需要在每台机器中进行配置\
n修改相关配置\n这个是与伪集群部署差异较大的一步，因为部署脚本会通过 scp 的方式将安装需要的资源传输到各个机器上 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/installation/cluster",
"title": "集群部署(Cluster)",
"location": [
@@ -16687,7 +16687,7 @@
{
"content": "快速试用 Kubernetes 部署\nKubernetes部署目的是在Kubernetes集群中部署 DolphinScheduler 服务，能调度大量任务，可用于在生产中部署。\n如果你是新手，想要体验 DolphinScheduler 的功能，推荐使用Standalone方式体检。如果你想体验更完整的功能，或者更大的任务量，推荐使用伪集群部署。如果你是在生产中使用，推荐使用集群部署或者kubernetes\n先决条件\n\nHelm 3.1.0+\nKubernetes 1.12+\nPV 供应(需要基础设施支持)\n\n安装 dolphinscheduler\n请下载源码包 apache-dolphinscheduler--src.tar.gz，下载地址: 下载\n发布一个名为 dolphinscheduler 的版本(release)，请执行以下命令：\n$ tar -zxvf apache-dolphinscheduler-<version>-src.tar.gz\n$ cd apache-dolphinsched [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/installation/kubernetes",
"title": "快速试用 Kubernetes 部署",
"location": [
@@ -16698,7 +16698,7 @@
{
"content": "基于 Rainbond 部署 DolphinScheduler 高可用集群\n本文描述通过 Rainbond 云原生应用管理平台 一键部署高可用的 DolphinScheduler 集群，这种方式适合给不太了解 Kubernetes、容器化等复杂技术的用户使用，降低了在 Kubernetes 中部署 DolphinScheduler 的门槛。\n前提条件\n\n可用的 Rainbond 云原生应用管理平台，请参阅文档 Rainbond 快速安装\n\nDolphinScheduler 集群一键部署\n\n对接并访问内置的开源应用商店，搜索关键词 dolphinscheduler 即可找到 DolphinScheduler 应用。\n\n\n\n点击 DolphinScheduler 右侧的 安装 进入安装页面，填写对应的信息，点击确定即可开始安装，自动跳转至应用视图。\n\n\n\n\n选择项\n说明\n\n\n\n\n团队名称\n用户自建的工作空间，以命名空间隔离\n\n\n集群名称\n选择 DolphinScheduler 被部署到哪 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/integration/rainbond",
"title": "基于 Rainbond 部署 DolphinScheduler 高可用集群",
"location": [
@@ -16710,7 +16710,7 @@
{
"content": "DolphinScheduler 元数据文档\n表Schema\n详见dolphinscheduler/dolphinscheduler-dao/src/main/resources/sql目录下的sql文件\nE-R图\n用户\t队列\t数据源\n\n\n一个租户下可以有多个用户；\nt_ds_user中的queue字段存储的是队列表中的queue_name信息，t_ds_tenant下存的是queue_id，在流程定义执行过程中，用户队列优先级最高，用户队列为空则采用租户队列；\nt_ds_datasource表中的user_id字段表示创建该数据源的用户，t_ds_relation_datasource_user中的user_id表示对数据源有权限的用户；\n\n项目\t资源\t告警\n\n\n一个用户可以有多个项目，用户项目授权通过t_ds_relation_project_user表完成project_id和user_id的关系绑定；\nt_ds_projcet表中的user_id表示创建该项目的用户，t_ds_relation [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/architecture/metadata",
"title": "DolphinScheduler 元数据文档",
"location": [
@@ -16721,7 +16721,7 @@
{
"content": "系统架构设计\n系统架构\n系统架构图\n\n \n \n 系统架构图\n \n\n启动流程活动图\n\n \n \n 启动流程活动图\n \n\n架构说明\n\n\nMasterServer\nMasterServer采用分布式无中心设计理念，MasterServer主要负责 DAG 任务切分、任务提交监控，并同时监听其它MasterServer和WorkerServer的健康状态。\nMasterServer服务启动时向Zookeeper注册临时节点，通过监听Zookeeper临时节点变化来进行容错处理。\nMasterServer基于netty提供监听服务。\n该服务内主要包含:\n\n\nDistributedQuartz分布式调度组件，主要负责定时任务的启停操作，当quartz调起任务后，Master内部会有线程池具体负责处理任务的后续操作；\n\n\nMasterSchedulerService是一个扫描线程，定时扫描数据库中的t_ds_command表，根据不同的命令类型进行不同的业务 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/architecture/design",
"title": "系统架构设计",
"location": [
@@ -16732,7 +16732,7 @@
{
"content": "\n前言\n本文档为dolphinscheduler配置文件说明文档。\n目录结构\nDolphinScheduler的目录结构如下：\n├── LICENSE\n│\n├── NOTICE\n│\n├── licenses licenses存放目录\n│\n├── bin DolphinScheduler命令和环境变量配置存放目录\n│ ├── dolphinscheduler-daemon.sh 启动/关闭DolphinScheduler服务脚本\n│ ├── env 环境变量配置存放目录\n│ │ ├── dolphinscheduler_env.sh 当使用`dolphinscheduler-daemon.sh`脚本起停服务时，运行此脚本加载环境变 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/architecture/configuration",
"title": "前言",
"location": [
@@ -16743,7 +16743,7 @@
{
"content": "任务总体存储结构\n在dolphinscheduler中创建的所有任务都保存在t_ds_process_definition 表中.\n该数据库表结构如下表所示:\n\n\n\n序号\n字段\n类型\n描述\n\n\n\n\n1\nid\nint(11)\n主键\n\n\n2\nname\nvarchar(255)\n流程定义名称\n\n\n3\nversion\nint(11)\n流程定义版本\n\n\n4\nrelease_state\ntinyint(4)\n流程定义的发布状态：0 未上线 , 1已上线\n\n\n5\nproject_id\nint(11)\n项目id\n\n\n6\nuser_id\nint(11)\n流程定义所属用户id\n\n\n7\nprocess_definition_json\nlongtext\n流程定义JSON\n\n\n8\ndescription\ntext\n流程定义描述\n\n\n9\nglobal_params\ntext\n全局参数\n\n\n10\nflag\ntinyint(4)\ [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/architecture/task-structure",
"title": "任务总体存储结构",
"location": [
@@ -16754,7 +16754,7 @@
{
"content": "负载均衡\n负载均衡即通过路由算法（通常是集群环境），合理的分摊服务器压力，达到服务器性能的最大优化。\nDolphinScheduler-Worker 负载均衡算法\nDolphinScheduler-Master 分配任务至 worker,默认提供了三种算法:\n加权随机（random）\n平滑轮询（roundrobin）\n线性负载（lowerweight）\n默认配置为线性加权负载。\n由于路由是在客户端做的，即 master 服务，因此你可以更改 master.properties 中的 master.host.selector 来配置你所想要的算法。\neg：master.host.selector=random（不区分大小写）\nWorker 负载均衡配置\n配置文件 worker.properties\n权重\n上述所有的负载算法都是基于权重来进行加权分配的，权重影响分流结果。你可以在 修改 worker.weight 的值来给不同的机器设置不同的权重。\n预热\n考虑到 JIT 优化，我们会让 worker 在启动后低功 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/architecture/load-balance",
"title": "负载均衡",
"location": [
@@ -16765,7 +16765,7 @@
{
"content": "缓存\n缓存目的\n由于在master-server调度过程中，会产生大量的数据库读取操作，如tenant，user，processDefinition等，一方面对DB产生很大的读压力，另一方面则会使整个核心调度流程变得缓慢；\n考虑到这部分业务数据是读多写少的场景，故引入了缓存模块，以减少DB读压力，加快核心调度流程；\n缓存设置\nspring:\n cache:\n # default enable cache, you can disable by `type: none`\n type: none\n cache-names:\n - tenant\n - user\n - processDefinition\n - processTaskRelation\n - taskDefinition\n caffeine:\n spec: maximumSize=100,expireAfterWrite=300s,recordStats\n\n缓存模 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/architecture/cache",
"title": "缓存",
"location": [
@@ -16776,7 +16776,7 @@
{
"content": "API 调用\n背景\n一般都是通过页面来创建项目、流程等，但是与第三方系统集成就需要通过调用 API 来管理项目、流程。\n操作步骤\n创建 token\n\n登录调度系统，点击 "安全中心"，再点击左侧的 "令牌管理"，点击 "令牌管理" 创建令牌。\n\n\n\n选择 "失效时间" (Token 有效期)，选择 "用户" (以指定的用户执行接口操作)，点击 "生成令牌" ，拷贝 Token 字符串，然后点击 "提交" 。\n\n\n使用案例\n查询项目列表信息\n\n打开 API 文档页面\n\n\n地址：http://{api server ip}:12345/dolphinscheduler/swagger-ui/index.html?language=zh_CN&lang=cn\n\n\n\n选一个测试的接口，本次测试选取的接口是：查询所有项目\n\n\nprojects/list [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/api/open-api",
"title": "API 调用",
"location": [
@@ -16787,7 +16787,7 @@
{
"content": "PyDolphinScheduler\nPyDolphinScheduler 是 Apache DolphinScheduler 的 Python API，它允许您通过 Python 代码定义您的工作流，也称为 workflow-as-codes。\n更多信息请参考PyDolphinScheduler\n",
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/api/pydolphinscheduler",
"title": "PyDolphinScheduler",
"location": [
@@ -16798,7 +16798,7 @@
{
"content": "健康检查\n背景\n运行状况检查旨在提供一种独特的方法来检查 Dolphinscheduler 服务的运行状况。它包括模块的运行状况，例如 DB、缓存、网络等等。\nEndpoint\nAPI-Server\ncurl --request GET 'http://localhost:12345/dolphinscheduler/actuator/health'\n\n{"status":"UP","components":{"db":{"status":"UP","details":{"database":"H2","validationQuery":"isValid()"}}}}\n\nMaster-Server\ncurl --request GET 'http://localhost:5 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/guide/api/healthcheck",
"title": "健康检查",
"location": [
@@ -16809,7 +16809,7 @@
{
"content": "DolphinScheduler Alert SPI 主要设计\nDolphinScheduler SPI 设计\nDolphinScheduler 正在处于微内核 + 插件化的架构更改之中，所有核心能力如任务、资源存储、注册中心等都将被设计为扩展点，我们希望通过 SPI 来提高 DolphinScheduler 本身的灵活性以及友好性（扩展性）。\n告警相关代码可以参考 dolphinscheduler-alert-api 模块。该模块定义了告警插件扩展的接口以及一些基础代码，当我们需要实现相关功能的插件化的时候，建议先阅读此块的代码，当然，更建议你阅读文档，这会减少很多时间，不过文档有一定的后滞性，当文档缺失的时候，建议以源码为准（如果有兴趣，我们也欢迎你来提交相关文档），此外，我们几乎不会对扩展接口做变更（不包括新增），除非重大架构调整，出现不兼容升级版本，因此，现有文档一般都能够满足。\n我们采用了原生�
� JAVA-SPI，当你需要扩展的时候，事实上你只需要关注扩展org.apache.dolphinscheduler.alert [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/contribute/backend/spi/alert",
"title": "DolphinScheduler Alert SPI 主要设计",
"location": [
@@ -16821,7 +16821,7 @@
{
"content": "DolphinScheduler Datasource SPI 主要设计\n如何使用数据源？\n数据源中心默认支持POSTGRESQL、HIVE/IMPALA、SPARK、CLICKHOUSE、SQLSERVER数据源。\n如果使用的是MySQL、ORACLE数据源则需要、把对应的驱动包放置lib目录下\n如何进行数据源插件开发？\norg.apache.dolphinscheduler.spi.datasource.DataSourceChannel\norg.apache.dolphinscheduler.spi.datasource.DataSourceChannelFactory\norg.apache.dolphinscheduler.plugin.datasource.api.client.CommonDataSourceClient\n\n第一步数据源插件实现以上接口和继承通用client即可，具体可以参考sqlserver、mysql等数据源插件实现，所有RDBMS插件的添加方式都是一样的。\n在数据源插件pom.xml添 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/contribute/backend/spi/datasource",
"title": "DolphinScheduler Datasource SPI 主要设计",
"location": [
@@ -16833,7 +16833,7 @@
{
"content": "DolphinScheduler Registry SPI 扩展\n如何使用？\n进行以下配置（以 zookeeper 为例）\n\n\n注册中心插件配置, 以Zookeeper 为例 (registry.properties)\ndolphinscheduler-service/src/main/resources/registry.properties\nregistry.plugin.name=zookeeper\nregistry.servers=127.0.0.1:2181\n\n\n\n具体配置信息请参考具体插件提供的参数信息，例如 zk：org/apache/dolphinscheduler/plugin/registry/zookeeper/ZookeeperConfiguration.java\n所有配置信息前缀需要 +registry，如 base.sleep.time.ms，在 registry 中应该这样配置：registry.base.sleep.time.ms=100\n如何扩展\ndolphinschedul [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/contribute/backend/spi/registry",
"title": "DolphinScheduler Registry SPI 扩展",
"location": [
@@ -16845,7 +16845,7 @@
{
"content": "DolphinScheduler Task SPI 扩展\n如何进行任务插件开发？\norg.apache.dolphinscheduler.spi.task.TaskChannel\n插件实现以上接口即可。主要包含创建任务（任务初始化，任务运行等方法）、任务取消，如果是 yarn 任务，则需要实现 org.apache.dolphinscheduler.plugin.task.api.AbstractYarnTask。\n我们在 dolphinscheduler-task-api 模块提供了所有任务对外访问的 API，而 dolphinscheduler-spi 模块则是 spi 通用代码库，定义了所有的插件模块，比如告警模块，注册中心模块等，你可以详细阅读查看。\n另外，TaskChannelFactory 继承自 PrioritySPI，这意味着你可以设置插件的优先级，当你有两个插件同名时，你可以通过重写 getIdentify 方法来自定义优先级。高优先级的插件会被加载，但是如果你有两个同名且优先级相同的插件，加载插件时服务器会抛 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/contribute/backend/spi/task",
"title": "DolphinScheduler Task SPI 扩展",
"location": [
@@ -16857,7 +16857,7 @@
{
"content": "DolphinScheduler 开发手册\n软件要求\n在搭建 DolphinScheduler 开发环境之前请确保你已经安装以下软件:\n\nGit\nJDK: v1.8.x (当前暂不支持 jdk 11)\nMaven: v3.5+\nNode: v16.13+ (dolphinScheduler 版本低于 3.0, 请安装 node v12.20+)\nPnpm: v6.x\n\n克隆代码库\n通过你 git 管理工具下载 git 代码，下面以 git-core 为例\nmkdir dolphinscheduler\ncd dolphinscheduler\ngit clone git@github.com:apache/dolphinscheduler.git\n\n编译源码\n支持的系统:\n\nMacOS\nLinux\n\n运行 mvn clean install -Prelease -Dmaven.test.skip=true\n代码风格\nDolphinScheduler使用Spotless检查并修复代码风格和格式问题 [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/contribute/development-environment-setup",
"title": "DolphinScheduler 开发手册",
"location": [
@@ -16868,7 +16868,7 @@
{
"content": "前端开发文档\n技术选型\nVue mvvm 框架\n\nEs6 ECMAScript 6.0\n\nAns-ui Analysys-ui\n\nD3 可视化库图表库\n\nJsplumb 连线插件库\n\nLodash 高性能的 JavaScript 实用工具库\n\n开发环境搭建\n\n\n\nNode安装\nNode包下载 (注意版本 v12.20.2) https://nodejs.org/download/release/v12.20.2/\n\n\n\n前端项目构建\n用命令行模式 cd 进入 dolphinscheduler-ui项目目录并执行 npm install 拉取项目依赖包\n\n如果 npm install 速度非常慢，你可以设置淘宝镜像\n\nnpm config set registry http://registry.npm.taobao.org/\n\n\n修改 dolphinscheduler-ui/.env 文件中的 API_BASE，用于跟后端交互：\n\n# 代理的接口地址（自行修改）\nAPI [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
"link": "/contribute/frontend-development",
"title": "前端开发文档",
"location": [
@@ -16879,7 +16879,1084 @@
{
"content": "DSIP\nDolphinScheduler Improvement Proposal (DSIP) 是对 Apache DolphinScheduler 代码库进行的重大改进。它不是为了小修小补存在的，\nDSIP 的目的是通知社区完成或即将完成的重大变更。\n怎样的修改应该被认定为 DSIP\n\n任何重大的新功能、重大改进、引入或删除组件\n任何公共接口的任何重大变化，例如 API接口、web ui 巨大变化\n\n当一个 PR 或者 Issue 是否应该被认定为 DSIP 存疑时，如果有 committer 认为他应该纳入 DAIP 的范畴，那它就应该是 DSIP。\n我们使用 GitHub Issue 和 Apache 邮件列表来记录和保存 DSIP，想要了解更多相关信息，您可以跳转到 当前的 DSIPs 以及 past DSIPs\n作为 DSIP，它应该包含如下部分：\n\n在 dev@dolphinscheduler.apache.org 中有一个以 [DISCUSS][DSIP 为开头的邮件。\n有一个打了 " [...]
"version": "3.1.5",
- "time": "2023-4-6",
+ "time": "2023-04-06",
+ "link": "/DSIP",
+ "title": "DSIP",
+ "location": [
+ "DSIP",
+ "DSIP"
+ ]
+ },
+ {
+ "content": "关于DolphinScheduler\nApache DolphinScheduler 是一个分布式易扩展的可视化DAG工作流任务调度开源系统。适用于企业级场景，提供了一个可视化操作任务、工作流和全生命周期数据处理过程的解决方案。\nApache DolphinScheduler 旨在解决复杂的大数据任务依赖关系，并为应用程序提供数据和各种 OPS 编排中的关系。 解决数据研发ETL依赖错综复杂，无法监控任务健康状态的问题。\nDolphinScheduler 以 DAG（Directed Acyclic Graph，DAG）流式方式组装任务，可以及时监控任务的执行状态，支持重试、指定节点恢复失败、暂停、恢复、终止任务等操作。\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/about/introduction",
+ "title": "关于DolphinScheduler",
+ "location": [
+ "关于Apache DolphinScheduler",
+ "简介"
+ ]
+ },
+ {
+ "content": "特性\n简单易用\n\n可视化 DAG: 用户友好的，通过拖拽定义工作流的，运行时控制工具\n模块化操作: 模块化有助于轻松定制和维护。\n\n丰富的使用场景\n\n支持多种任务类型: 支持Shell、MR、Spark、SQL等10余种任务类型，支持跨语言，易于扩展\n丰富的工作流操作: 工作流程可以定时、暂停、恢复和停止，便于维护和控制全局和本地参数。\n\nHigh Reliability\n\n高可靠性: 去中心化设计，确保稳定性。 原生 HA 任务队列支持，提供过载容错能力。 DolphinScheduler 能提供高度稳健的环境。\n\nHigh Scalability\n\n高扩展性: 支持多租户和在线资源管理。支持每天10万个数据任务的稳定运行。\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/about/features",
+ "title": "特性",
+ "location": [
+ "关于Apache DolphinScheduler",
+ "特性"
+ ]
+ },
+ {
+ "content": "软硬件环境建议配置\nDolphinScheduler 作为一款开源分布式工作流任务调度系统，可以很好地部署和运行在 Intel 架构服务器及主流虚拟化环境下，并支持主流的Linux操作系统环境\n1. Linux 操作系统版本要求\n\n\n\n操作系统\n版本\n\n\n\n\nRed Hat Enterprise Linux\n7.0 及以上\n\n\nCentOS\n7.0 及以上\n\n\nOracle Enterprise Linux\n7.0 及以上\n\n\nUbuntu LTS\n16.04 及以上\n\n\n\n\n注意：\n以上 Linux 操作系统可运行在物理服务器以及 VMware、KVM、XEN 主流虚拟化环境上\n\n2. 服务器建议配置\nDolphinScheduler 支持运行在 Intel x86-64 架构的 64 位通用硬件服务器平台。对生产环境的服务器硬件配置有以下建议：\n生产环境\n\n\n\nCPU\n内存\n硬盘类型\n网络\n实例数量\n\n\n\n\n4核+\n8 GB+\nSAS\ [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/about/hardware",
+ "title": "软硬件环境建议配置",
+ "location": [
+ "关于Apache DolphinScheduler",
+ "建议配置"
+ ]
+ },
+ {
+ "content": "名词解释\n在对 Apache DolphinScheduler 了解之前，我们先来认识一下调度系统常用的名词\n1.名词解释\nDAG： 全称 Directed Acyclic Graph，简称 DAG。工作流中的 Task 任务以有向无环图的形式组装起来，从入度为零的节点进行拓扑遍历，直到无后继节点为止。举例如下图：\n\n流程定义：通过拖拽任务节点并建立任务节点的关联所形成的可视化DAG\n流程实例：流程实例是流程定义的实例化，可以通过手动启动或定时调度生成。每运行一次流程定义，产生一个流程实例\n任务实例：任务实例是流程定义中任务节点的实例化，标识着某个具体的任务\n任务类型：目前支持有 SHELL、SQL、SUB_PROCESS(子流程)、PROCEDURE、MR、SPARK、PYTHON、DEPENDENT(依赖)，同时计划支持动态插件扩展，注意：其中 SUB_PROCESS类型的任务需要关联另外一个流程定义，被关联的流程定义是可
以单独启动执行的\n调度方式：系统支持基于 cron 表达式的定时调度和手动调度。命令类型支持：启 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/about/glossary",
+ "title": "名词解释",
+ "location": [
+ "关于Apache DolphinScheduler",
+ "名词解释"
+ ]
+ },
+ {
+ "content": "快速上手\n\n\n喜欢看视频的伙伴可以参见手把手教你如何《快速上手 Apache DolphinScheduler 教程》\n\n\n\n管理员用户登录\n\n地址：http://localhost:12345/dolphinscheduler/ui 用户名/密码：admin/dolphinscheduler123\n\n\n\n\n\n创建队列\n\n\n\n创建租户\n\n\n\n创建普通用户\n\n\n\n创建告警组实例\n\n\n\n创建告警组\n\n\n\n创建 Worker 分组\n\n\n\n\n创建环境\n\n\n\n创建 Token 令牌\n\n\n\n\n使用普通用户登录\n\n\n点击右上角用户名“退出”，重新使用普通用户登录。\n\n\n项目管理->创建项目->点击项目名称\n\n\n\n点击工作流定义->创建工作流定义->上线工作流定义\n\n\n\n运行工作流定义->点击工作流实例->点击工作流实例名称->双击任务节点->查看任务执行日志\n\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/start/quick-start",
+ "title": "快速上手",
+ "location": [
+ "快速上手",
+ "快速上手"
+ ]
+ },
+ {
+ "content": "Docker 快速使用教程\n本教程使用三种不同的方式通过 Docker 完成 DolphinScheduler 的部署\n\n如果你想要快速体验，推荐使用 standalone-server 镜像，\n如果你想要体验比较完成的服务，推荐使用 docker-compose 启动服务.\n如果你已经有自己的数据库或者 Zookeeper 服务你想要沿用这些基础服务，你可以参考沿用已有的 PostgreSQL 和 ZooKeeper 服务完成部署。\n\n前置条件\n需要安装 Docker 1.13.1 以上版本，以及 Docker Compose 1.28.0 以上版本。\n启动服务\n使用 standalone-server 镜像\n使用 standalone-server 镜像启动一个 DolphinScheduler standalone-server 容器应该是最快体验 DolphinScheduler 的方法。通过这个方式\n你可以最快速的体验到 DolphinScheduler 的大部分功能，了解主要和概念和内容。\n$ DOL [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/start/docker",
+ "title": "Docker 快速使用教程",
+ "location": [
+ "快速上手",
+ "Docker部署(Docker)"
+ ]
+ },
+ {
+ "content": "首页\nApache DolphinScheduler 首页可让您查看用户所有项目的任务状态统计、工作流状态统计和项目统计。 这是观察整个系统状态以及深入各个进程以检查任务和任务日志的每个状态的最佳方式。\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/homepage",
+ "title": "首页",
+ "location": [
+ "功能介绍",
+ "应用首页"
+ ]
+ },
+ {
+ "content": "项目管理\n创建项目\n点击"项目管理"进入项目管理页面，点击“创建项目”按钮，输入项目名称，项目描述，点击“提交”，创建新的项目。\n\n项目首页\n在项目管理页面点击项目名称链接，进入项目首页，如下图所示，项目首页包含该项目的任务状态统计、流程状态统计、工作流定义统计。这几个指标的说明如下\n\n任务状态统计：在指定时间范围内，统计任务实例中状态为提交成功、正在运行、准备暂停、暂停、准备停止、停止、失败、成功、需要容错、kill、等待线程的个数\n流程状态统计：在指定时间范围内，统计工作流实例中状态为提交成功、正在运行、准备暂停、暂停、准备停止、停止、失败、成功、需要容错、kill、等待线程的个数\n工作流定义统计：统计用户创建的工作流定义及管理员授予该用户的工作流定义\n\n
\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/project/project-list",
+ "title": "项目管理",
+ "location": [
+ "功能介绍",
+ "项目管理",
+ "项目列表"
+ ]
+ },
+ {
+ "content": "工作流定义\n创建工作流定义\n\n\n点击项目管理->工作流->工作流定义，进入工作流定义页面，点击“创建工作流”按钮，进入工作流DAG编辑页面，如下图所示：\n\n\n\n工具栏中拖拽 到画板中，新增一个Shell任务,如下图所示：\n\n\n\n添加 Shell 任务的参数设置：\n\n填写“节点名称”，“描述”，“脚本”字段；\n“运行标志”勾选“正常”，若勾选“禁止执行”，运行工作流不会执行该任务；\n选择“任务优先级”：当 worker 线程数不足时，级别高的任务在执行队列中会优先执行，相同优先级的任务按照先进先出的顺序执行；\n超时告警（非必选）：勾选超时告警、超时失败，填写“超时时长”，当任务执行时间超过超时时长，会发送告警邮件并且任务超时失败；\n资源（非必选）：资源文件是资源中心->文件管理页面创建或上传的�
��件，如文件名为 test.sh，脚本中调用资源命令为 sh test.sh。注意调用需要使用资源的全路径；\n自定义参数（非必填）；\n点击"确认添加"按钮，保存任务设置。\ [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/project/workflow-definition",
+ "title": "工作流定义",
+ "location": [
+ "功能介绍",
+ "项目管理",
+ "工作流定义"
+ ]
+ },
+ {
+ "content": "工作流实例\n查看工作流实例\n\n点击项目管理->工作流->工作流实例，进入工作流实例页面，如下图所示：\n\n\n\n点击工作流名称，进入DAG查看页面，查看任务执行状态，如下图所示。\n\n\n查看任务日志\n\n进入工作流实例页面，点击工作流名称，进入DAG查看页面，双击任务节点，如下图所示：\n\n\n\n点击"查看日志"，弹出日志弹框，如下图所示,任务实例页面也可查看任务日志，参考任务查看日志。\n\n\n查看任务历史记录\n\n点击项目管理->工作流->工作流实例，进入工作流实例页面，点击工作流名称，进入工作流 DAG 页面;\n双击任务节点，如下图所示，点击"查看历史"，跳转到任务实例页面，并展示该工作流实例运行的任务实例列表\n\n\n查看运行参数\n\n点击项目管理->工作流->工作流实例，进入工作流实例页面�
�点击工作流名称，进入工作流 DAG 页面;\n点击左上角图标，查看工作流实例的启动参数；点击图标，查看工作流实例的全局参数和局部参数，如 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/project/workflow-instance",
+ "title": "工作流实例",
+ "location": [
+ "功能介绍",
+ "项目管理",
+ "工作流实例"
+ ]
+ },
+ {
+ "content": "任务实例\n批量任务实例\n\n点击项目管理->工作流->任务实例，进入任务实例页面，如下图所示，点击工作流实例名称，可跳转到工作流实例DAG图查看任务状态。\n\n\n\n查看日志：点击操作列中的“查看日志”按钮，可以查看任务执行的日志情况。\n\n\n实时任务实例\n\n切换到实时任务实例页面，如下图所示：\n\n\n\nSavePoint：点击操作列中的SavePoint按钮，可以进行实时任务的SavePoint。\nStop：点击操作列中的Stop按钮，可以停止该实时任务。\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/project/task-instance",
+ "title": "任务实例",
+ "location": [
+ "功能介绍",
+ "项目管理",
+ "任务实例"
+ ]
+ },
+ {
+ "content": "任务定义\n批量任务定义\n批量任务定义允许您在基于任务级别而不是在工作流中操作修改任务。再此之前，我们已经有了工作流级别的任务编辑器，你可以在工作流定义\n单击特定的工作流，然后编辑任务的定义。当您想编辑特定的任务定义但不记得它属于哪个工作流时，这是令人沮丧的。所以我们决定在 任务 菜单下添加 任务定义 视图。\n\n在该视图中，您可以通过单击 操作 列中的相关按钮来进行创建、查询、更新、删除任务定义。最令人兴奋的是您可以通过通配符进行全部任务查询，当您只\n记得任务名称但忘记它属于哪个工作流时是非常有用的。也支持通过任务名称结合使用 任务类型 或 工作流程名称 进行查询。\n实时任务定义\n实时任务定义在工作流定义中创建，在任务定义页面可以进行修改和执行。\n\n点击实时任务执行，
检查执行参数后点击确认，即可提交实时任务。\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/project/task-definition",
+ "title": "任务定义",
+ "location": [
+ "功能介绍",
+ "项目管理",
+ "任务定义"
+ ]
+ },
+ {
+ "content": "DolphinScheduler任务参数附录\nDolphinScheduler任务插件有一些公共参数，我们将这些公共参数列在文档中供您查阅。每种任务都有如下的所有或者部分默认参数：\n默认任务参数\n\n\n\n任务参数\n描述\n\n\n\n\n任务名称\n任务的名称，同一个工作流定义中的节点名称不能重复。\n\n\n运行标志\n标识这个节点是否需要调度执行，如果不需要执行，可以打开禁止执行开关。\n\n\n描述\n当前节点的功能描述。\n\n\n任务优先级\nworker线程数不足时，根据优先级从高到低依次执行任务，优先级一样时根据先到先得原则执行。\n\n\nWorker分组\n设置分组后，任务会被分配给worker组的机器机执行。若选择Default，则会随机选择一个worker执行。\n\n\n任务组名称\n任务资源组，未配置则不生效。\n\n\n组内优先级\n一个任务组内此任务的优先级。\n\n\n环境名称\n配置任务执�
�的环境。\n\n\n失败重试次数\n任务失败重新提交的次数，可以在下拉菜单中选择或者手动填充。\n\n\ [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/appendix",
+ "title": "DolphinScheduler任务参数附录",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Appendix"
+ ]
+ },
+ {
+ "content": "Shell\n综述\nShell 任务类型，用于创建 Shell 类型的任务并执行一系列的 Shell 脚本。worker 执行该任务的时候，会生成一个临时 shell 脚本，并使用与租户同名的 linux 用户执行这个脚本。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入 DAG 编辑页面。\n工具栏中拖动 到画板中，即可完成创建。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n除上述默认参数，此任务没有其他参数\n\n任务样例\n简单打印一行文字\n该样例模拟了常见的简单任务，这些任务只需要简单的一两行命令就能运行起来。我们以打印一行日志为例，该任务仅会在日志文件中打印一行\n"This is a demo of shell task"\n\n使用自定义参数\n该样例模拟了自定义参数任务，为了更方便的复用已有的任务，�
��者面对动态的需求时，我们会使用变量保证脚本的复用性。本例中，我们先在自定义脚本\n [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/shell",
+ "title": "Shell",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Shell"
+ ]
+ },
+ {
+ "content": "子流程节点\n综述\n子流程节点，就是把外部的某个工作流定义当做一个节点去执行。\n创建任务\n\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击”创建工作流”按钮，进入 DAG 编辑页面：\n\n\n拖动工具栏的 任务节点到画板中。\n\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n子节点\n是选择子流程的工作流定义，右上角进入该子节点可以跳转到所选子流程的工作流定义\n\n\n\n任务样例\n该样例模拟了常见的任务类型，这里我们使用子结点任务调用 Shell 打印出 ”hello world“。即将一个 shell 任务当作子结点来执行。\n创建 shell 任务\n创建一个 shell 任务，用于打印 “hello”。并为该工作流定义为 test_dag01。\n\n创建 sub_process 任务\n在使用 sub_process 的过程中，需要创建所需
的子结点任务，也就是我们第一步所创建的 s [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/sub-process",
+ "title": "子流程节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "SubProcess"
+ ]
+ },
+ {
+ "content": "Dependent 节点\n综述\nDependent 节点，就是依赖检查节点。比如 A 流程依赖昨天的 B 流程执行成功，依赖节点会去检查 B 流程在昨天是否有执行成功的实例。\n创建任务\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n此任务除上述链接中的默认参数外无其他参数。\n\n任务样例\nDependent 节点提供了逻辑判断功能，可以按照逻辑来检测所依赖节点的执行情况。\n例如，A 流程为周报任务，B、C 流程为天任务，A 任务需要 B、C 任务在上周的每一天都执行成功，如图示：\n\n例如，A 流程为周报任务，B、C 流程为天任务，A 任务需要 B 或 C 任务在上周的每一天都执行成功，如图示：\n\n�
��如，周报 A 同时还需要自身在上周二执行成功：\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/dependent",
+ "title": "Dependent 节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Dependent"
+ ]
+ },
+ {
+ "content": "存储过程节点\n\n根据选择的数据源，执行存储过程。\n\n\n拖动工具栏中的PROCEDURE任务节点到画板中，如下图所示：\n\n\n \n \n\n前提：在该数据库里面创建存储过程，如：\n\nCREATE PROCEDURE dolphinscheduler.test(in in1 INT, out out1 INT)\nbegin\n\tset out1=in1;\nEND\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n数据源\n存储过程的数据源类型支持MySQL、POSTGRESQL、ORACLE，选择对应的数据源\n\n\nSQL Statement\n调用存储过程，如 call test(${in1},${out1});\n\n\n自定义参数\n存储过程的自定义参数类型支持IN、OUT两种，数据类型支持VARCHAR、INTEGER、LONG、FLOAT、DOUBLE、DATE、TIME、TIMESTAMP、 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/stored-procedure",
+ "title": "存储过程节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Stored Procedure"
+ ]
+ },
+ {
+ "content": "SQL\n综述\nSQL任务类型，用于连接数据库并执行相应SQL。\n创建数据源\n可参考 数据源配置 数据源中心。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入DAG编辑页面。\n工具栏中拖动 到画板中，选择需要连接的数据源，即可完成创建。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n数据源：选择对应的数据源\nsql类型：支持查询和非查询两种。\n查询：支持 DML select 类型的命令，是有结果集返回的，可以指定邮件通知为表格、附件或表格附件三种模板；\n非查询：支持 DDL全部命令 和 DML update、delete、insert 三种类型的命令；\n默认采用;\\n作为SQL分隔符,拆分成多段SQL语句执行。Hive的JDBC不支持一次执行多段SQL语句，请不要使用;\\n。\nsql参数：输入参数格式为key1=value
1;key2=value2…\nsql语句：SQL语句\nUDF函数：对于HI [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/sql",
+ "title": "SQL",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "SQL"
+ ]
+ },
+ {
+ "content": "SPARK节点\n综述\nSpark 任务类型用于执行 Spark 应用。对于 Spark 节点，worker 支持两个不同类型的 spark 命令提交任务：\n(1) spark submit 方式提交任务。更多详情查看 spark-submit。\n(2) spark sql 方式提交任务。更多详情查看 spark sql。\n创建任务\n\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击”创建工作流”按钮，进入 DAG 编辑页面：\n\n\n拖动工具栏的 任务节点到画板中。\n\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n程序类型：支持 Java、Scala、Python 和 SQL 四种语言。\nSpark 版本：支持 Spark1 和 Spark2。\n主函数的 Class：Spark 程序的入口 Main class 的全路径。\n主程序包：执行 Spark 程序的 jar 包（通过资源中心上传）。\nSQL脚本：Spark sql 运行的 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/spark",
+ "title": "SPARK节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Spark"
+ ]
+ },
+ {
+ "content": "MapReduce(MR) 节点\n综述\nMapReduce(MR) 任务类型，用于执行 MapReduce 程序。对于 MapReduce 节点，worker 会通过使用 Hadoop 命令 hadoop jar 的方式提交任务。更多详情查看 Hadoop Command Manual。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入 DAG 编辑页面。\n拖动工具栏中的 任务节点到画板中，如下图所示：\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\nJAVA/SCALA 程序\n\n\n\n任务参数\n描述\n\n\n\n\n程序类型\n选择 JAVA/SCALA 语言\n\n\n主函数的 Class\n是 MapReduce 程序的入口 Main Class 的全路径\n\n\n主程序包\n执行 MapReduce 程序的 jar 包\n\n\n任务名称（选填）\nMapReduce 任务名称\n\n\n命令行参 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/map-reduce",
+ "title": "MapReduce(MR) 节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "MapReduce"
+ ]
+ },
+ {
+ "content": "Python 节点\n综述\nPython 任务类型，用于创建 Python 类型的任务并执行一系列的 Python 脚本。worker 执行该任务的时候，会生成一个临时python脚本，\n并使用与租户同名的 linux 用户执行这个脚本。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入DAG编辑页面。\n工具栏中拖动 到画板中，即可完成创建。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n脚本\n用户开发的PYTHON程序\n\n\n自定义参数\n是PYTHON局部的用户自定义参数，会替换脚本中以${变量}的内容\n\n\n\n任务样例\n简单打印一行文字\n该样例模拟了常见的简单任务，这些任务只需要简单的一两行命令就能运行起来。我们以打印一行日志为例，该任务仅会在日志文件中打印一行\n"This i
s a demo of python task" [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/python",
+ "title": "Python 节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Python"
+ ]
+ },
+ {
+ "content": "Flink节点\n综述\nFlink 任务类型，用于执行 Flink 程序。对于 Flink 节点：\n\n\n当程序类型为 Java、Scala 或 Python 时，worker 使用 Flink 命令提交任务 flink run。更多详情查看 flink cli 。\n\n\n当程序类型为 SQL 时，worker 使用sql-client.sh 提交任务。更多详情查看 flink sql client 。\n\n\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n程序类型\n支持 Java、Scala、 Python 和 SQL 四种语言\n\n\n主函数的 Class\nFlink 程序的入口 Main Class 的全路径\n\n\n主程序包\n执行 Flink 程序的 jar 包 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/flink",
+ "title": "Flink节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Flink"
+ ]
+ },
+ {
+ "content": "HTTP 节点\n综述\n该节点用于执行 http 类型的任务，例如常见的 POST、GET 等请求类型，此外还支持 http 请求校验等功能。\n创建任务\n\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击”创建工作流”按钮，进入 DAG 编辑页面：\n\n\n拖动工具栏的 任务节点到画板中。\n\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n请求地址\nhttp 请求 URL\n\n\n请求类型\n支持 GET、POST、HEAD、PUT、DELETE\n\n\n请求参数\n支持 Parameter、Body、Headers\n\n\n校验条件\n支持默认响应码、自定义响应码、内容包含、内容不包含\n\n\n校验内容\n当校验条件选择自定义响应码、内容包含、内容不包含时，需填写校验内容\n\n\n自定义参数\n是 http 局部的用户自定义参数，会替换脚本中以 ${变量} 的内容\n\n\n\n任务 [.
..]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/http",
+ "title": "HTTP 节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "HTTP"
+ ]
+ },
+ {
+ "content": "DATAX 节点\n综述\nDataX 任务类型，用于执行 DataX 程序。对于 DataX 节点，worker 会通过执行 ${DATAX_HOME}/bin/datax.py 来解析传入的 json 文件。\n创建任务\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\njson\nDataX 同步的 json 配置文件\n\n\n资源\n在使用自定义json中如果集群开启了kerberos认证后，datax读取或者写入hdfs、hbase等插件时需要使用相关的keytab，xml文件等，则可使用改选项。资源中心-文件管理上传或创建的文件\n\n\n自定义参数\nsql 任务类型，而存储过程是自定义参数顺序的给方法设置值自定义参数类型和数据类型同存储过程任务类型一样。区别在
于SQ [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/datax",
+ "title": "DATAX 节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "DataX"
+ ]
+ },
+ {
+ "content": "Pigeon\nPigeon任务类型是通过调用远程websocket服务，实现远程任务的触发，状态、日志的获取，是 DolphinScheduler 通用远程 websocket 服务调用任务\n创建任务\n拖动工具栏中的任务节点到画板中即能完成任务创建\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n目标任务名\n输入Pigeon任务的目标任务名称\n\n\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/pigeon",
+ "title": "Pigeon",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Pigeon"
+ ]
+ },
+ {
+ "content": "Conditions 节点\nConditions 是一个条件节点，根据上游任务运行状态，判断应该运行哪个下游任务。截止目前 Conditions 支持多个上游任务，但只支持两个下游任务。当上游任务数超过一个时，可以通过且以及或操作符实现复杂上游依赖\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏中的任务节点到画板中。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n下游任务选择\n根据前置任务的状态来跳转到对应的分支：成功分支 - 当上游运行成功时，运行成功选择的分支；失败分支 - 当上游运行失败时，运行失败选择的分支\n\n\n上游条件选择\n可以为 Conditions 任务选择一个或多个上游任务：增加上游依赖 - 通过选择第一个�
��数选择对应的任务名称，通过第二个参数选择触发的 Conditions 任务的状态；上游任务关系选择 - 当有多个上游任务时，可 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/conditions",
+ "title": "Conditions 节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Conditions"
+ ]
+ },
+ {
+ "content": "Switch\nSwitch 是一个条件判断节点，依据全局变量的值和用户所编写的表达式判断结果执行对应分支。\n注意使用 javax.script.ScriptEngine.eval 执行表达式。\n创建任务\n点击项目管理 -> 项目名称 -> 工作流定义，点击"创建工作流"按钮，进入 DAG 编辑页面。\n拖动工具栏中的 任务节点到画板中即能完成任务创建。\n注意 switch 任务创建后，要先配置上下游，才能配置任务分支的参数。\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n条件\n可以为 switch 任务配置多个条件，当条件满足时，就会执行指定的分支，可以配置多个不同的条件来满足不同的业务，使用字符串判断时需要使用""\n\n\n分支流转\n默认的流转内容，当条件中的内容为全部不符合要求时，则运行分支�
�转中指定的分支\n\n\n\n任务样例\n这里使用一个 switch [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/switch",
+ "title": "Switch",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Switch"
+ ]
+ },
+ {
+ "content": "Apache SeaTunnel\n综述\nSeaTunnel 任务类型，用于创建并执行 SeaTunnel 类型任务。worker 执行该任务的时候，会通过 start-seatunnel-spark.sh 、 start-seatunnel-flink.sh 和 seatunnel.sh 命令解析 config 文件。\n点击 这里 获取更多关于 Apache SeaTunnel 的信息。\n创建任务\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务参数\n\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n引擎：支持 FLINK 、 SPARK 和 SEATUNNEL_ENGINE\n\n\nFLINK\n\n\n运行模型：支持 run 和 run-application 两种模式\n\n\n选项参数：用于添加 Flink 引擎本身参数，例如 -m yarn-cluster [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/seatunnel",
+ "title": "Apache SeaTunnel",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "SeaTunnel"
+ ]
+ },
+ {
+ "content": "Amazon EMR\n综述\nAmazon EMR 任务类型，用于在AWS上操作EMR集群并执行计算任务。\n后台使用 aws-java-sdk 将JSON参数转换为任务对象，提交到AWS，目前支持两种程序类型：\n\nRUN_JOB_FLOW 使用 API_RunJobFlow 提交 RunJobFlowRequest 对象\nADD_JOB_FLOW_STEPS 使用 API_AddJobFlowSteps 提交 AddJobFlowStepsRequest 对象\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n程序类型\n选择程序类型，如果是RUN_JOB_FLOW，则需要填写jobFlowDefineJson，如果是ADD_JOB_FLOW_STEPS，则需要填写stepsDefineJson\n\n\njobFlowDefineJson\nRunJobFlowRequest 对象对应的JSON，详细JSON定义参见 A [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/emr",
+ "title": "Amazon EMR",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Amazon EMR"
+ ]
+ },
+ {
+ "content": "Apache Zeppelin\n综述\nZeppelin任务类型，用于创建并执行Zeppelin类型任务。worker 执行该任务的时候，会通过Zeppelin Cient API触发Zeppelin Notebook Paragraph。\n点击这里 获取更多关于Apache Zeppelin Notebook的信息。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入DAG编辑页面。\n工具栏中拖动 到画板中，即可完成创建。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\nZeppelin Note ID\nZeppelin Note对应的唯一ID\n\n\nZeppelin Paragraph ID\nZeppelin Paragraph对应的唯一ID。如果你想一次性调度整个note，这一栏不填即可\n\n\nZeppelin Rest Endpoint\n您的Zepp [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/zeppelin",
+ "title": "Apache Zeppelin",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Apache Zeppelin"
+ ]
+ },
+ {
+ "content": "Jupyter\n综述\nJupyter任务类型，用于创建并执行Jupyter类型任务。worker 执行该任务的时候，会通过papermill执行jupyter note。\n点击这里 获取更多关于papermill的信息。\nConda虚拟环境配置\n\n在common.properties配置conda.path，将其指向您的conda.sh。这里的conda应该是您用来管理您的 papermill和jupyter所在python环境的相同conda。\n点击 这里 获取更多关于conda的信息.\nconda.path默认设置为/opt/anaconda3/etc/profile.d/conda.sh。 如果您不清楚您的conda环境在哪里，只需要在命令行执行conda info | grep -i 'base environment'即可获得。\n\n\n注意：Jupyter任务插件使用source命令激活conda环境，\n如果您的租户没有source命令使用权限，Jupyter任务插件将无法使用。\n\nPython依赖管理 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/jupyter",
+ "title": "Jupyter",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Jupyter"
+ ]
+ },
+ {
+ "content": "Hive CLI\n综述\n使用Hive Cli任务插件创建Hive Cli类型的任务执行SQL脚本语句或者SQL任务文件。\n执行任务的worker会通过hive -e命令执行hive SQL脚本语句或者通过hive -f命令执行资源中心中的hive SQL文件。\nHive CLI任务 VS 连接Hive数据源的SQL任务\n在DolphinScheduler中，我们有Hive CLI任务插件和使用Hive数据源的SQL插件提供用户在不同场景下使用，您可以根据需要进行选择。\n\nHive CLI任务插件直接连接HDFS和Hive Metastore来执行hive类型的任务，所以需要能够访问到对应的服务。\n执行任务的worker节点需要有相应的Hive jar包以及Hive和HDFS的配置文件。\n但是在生产调度中，Hive CLI任务插件能够提供更可靠的稳定性。\n使用Hive数据源的SQL插件不需要您在worker节点上有相应的Hive jar包以及Hive和HDFS的配置文件，而且支持 Kerberos认证。\n但是在生产调度 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/hive-cli",
+ "title": "Hive CLI",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Hive CLI"
+ ]
+ },
+ {
+ "content": "Kubernetes\n综述\nkubernetes任务类型，用于在kubernetes上执行一个短时和批处理的任务。worker最终会通过使用kubernetes client提交任务。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入DAG编辑页面。\n工具栏中拖动 到画板中，选择需要连接的数据源，即可完成创建。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n命名空间\n选择kubernetes集群上存在的命名空间\n\n\n最小CPU\n任务在kubernetes上运行所需的最小CPU\n\n\n最小内存\n任务在kubernetes上运行所需的最小内存\n\n\n镜像\n镜像地址\n\n\n自定义参数\nkubernetes任务局部的用户自定义参数，自定义参数最终会通过环境变量形式存在于容器中，提供给kubernetes任务使用\n\n\n\n任务样例\n在 Dol [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/kubernetes",
+ "title": "Kubernetes",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Kubernetes"
+ ]
+ },
+ {
+ "content": "MLflow节点\n综述\nMLflow 是一个MLops领域一个优秀的开源项目， 用于管理机器学习的生命周期，包括实验、可再现性、部署和中心模型注册。\nMLflow 组件用于执行 MLflow 任务，目前包含Mlflow Projects，和MLflow Models。（Model Registry将在不就的将来支持）。\n\nMLflow Projects: 将代码打包，并可以运行到任务的平台上。\nMLflow Models: 在不同的服务环境中部署机器学习模型。\nModel Registry: 在一个中央存储库中存储、注释、发现和管理模型 (你也可以在你的MLflow project 里面自行注册模型)。\n\n目前 Mlflow 组件支持的和即将支持的内容如下中：\n\nMLflow Projects\n\nBasicAlgorithm: 基础算法，包含LogisticRegression， svm， lightgbm， xgboost\nAutoML: AutoML工具，包含autosklean， flaml\nCusto [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/mlflow",
+ "title": "MLflow节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "MLflow"
+ ]
+ },
+ {
+ "content": "OpenMLDB 节点\n综述\nOpenMLDB 是一个优秀的开源机器学习数据库，提供生产级数据及特征开发全栈解决方案。\nOpenMLDB任务组件可以连接OpenMLDB集群执行任务。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务样例\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\nzookeeper地址\nOpenMLDB集群连接地址中的zookeeper地址, e.g. 127.0.0.1:2181\n\n\nzookeeper路径\nOpenMLDB集群连接地址中的zookeeper路径, e.g. /openmldb\n\n\n执行模式\n初始执行模式（离线/在线），你可以在sql语句中随时切换\n\n\nSQL语句\nSQL语句\n\n\n\n下面有几个例子：\n导入数据\n\n我们使用LOAD DATA语句导入数据到Open [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/openmldb",
+ "title": "OpenMLDB 节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Openmldb"
+ ]
+ },
+ {
+ "content": "DVC节点\n综述\nDVC（Data Version Control） 是一个MLops领域一个优秀的开机器学习版本管理系统。\nDVC 组件用于在DS上使用DVC的数据版本管理功能，帮助用户简易地进行数据的版本管理。组件提供如下三个功能：\n\nInit DVC: 将git仓库初始化为DVC仓库，并绑定存储数据的地址用于存储实际的数据。\nUpload: 将特定数据添加或者更新到仓库中，并记录版本号。\nDownload: 从仓库中下载特定版本的数据。\n\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务样例\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\nDVC任务类型\n可以选择 Upload、Download、Init DVC\n\n\nDVC仓库\n任务执行时关联的仓库地址\n\n\n\nInit DVC\n将git仓�
�初始化为DV [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/dvc",
+ "title": "DVC节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "DVC"
+ ]
+ },
+ {
+ "content": "Dinky\nOverview\nDinky任务类型，用于创建并执行Dinky类型任务以支撑一站式的开发、调试、运维 FlinkSQL、Flink Jar、SQL。worker 执行该任务的时候，会通过Dinky API触发Dinky 的作业。\n点击这里 获取更多关于Dinky的信息。\nCreate Task\n\n点击项目管理-项目名称-工作流定义，点击"创建工作流"按钮，进入DAG编辑页面。\n工具栏中拖动 到画板中，即可完成创建。\n\nTask Parameter\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\nDinky 地址\nDinky 服务的 url。\n\n\nDinky 任务 ID\nDinky 作业对应的唯一ID。\n\n\n上线作业\n指定当前 Dinky 作业是否上线，如果是，则该被提交的作业只能处于已发布且当前无对应的 Flink Job 实例在运行才可提交成功。\n\n\n\nTask Ex [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/dinky",
+ "title": "Dinky",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Dinky"
+ ]
+ },
+ {
+ "content": "SageMaker 节点\n综述\nAmazon SageMaker 是一个云机器学习平台。 提供了完整的基础设施，工具和工作流来帮助用户可以创建、训练和发布机器学习模型。\nAmazon SageMaker Model Building Pipelines 是一个可以直接使用SageMaker各种集成的机器学习管道构建工具，用户可以使用使用 Amazon SageMaker Pipeline 来构建端到端的机器学习系统。\n对于使用大数据与人工智能的用户，SageMaker 任务组件帮助用户可以串联起大数据工作流与SagaMaker的使用场景。\nDolphinScheduler SageMaker 组件的功能:\n\n启动 SageMaker Pipeline Execution，并持续获取状态，直至Pipeline执行完成。\n\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务样例\n\n默认参数说明请参考DolphinSched [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/sagemaker",
+ "title": "SageMaker 节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "SageMaker"
+ ]
+ },
+ {
+ "content": "ChunJun节点\n综述\nChunJun 任务类型，用于执行 ChunJun 程序。对于 ChunJun 节点，worker 会通过执行 ${CHUNJUN_HOME}/bin/start-chunjun 来解析传入的 json 文件。\n创建任务\n\n点击项目管理 -> 项目名称 -> 工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n\n\n\n任务参数\n描述\n\n\n\n\n自定义模板\n自定义 ChunJun 节点的 json 配置文件内容，当前支持此种方式。\n\n\njson\nChunJun 同步的 json 配置文件。\n\n\n自定义参数\n用户自定义参数，会替换脚本中以 ${变量} 的内容。\n\n\n部署方式\n执行ChunJun任务的方式，比如local，standalone等。\n\n\n选项参数\n支持 -confProp " [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/chunjun",
+ "title": "ChunJun节点",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "ChunJun"
+ ]
+ },
+ {
+ "content": "Pytorch 节点（试验版）\n综述\nPytorch 是一个的主流Python机器学习库。\n为了用户能够在DolphinScheduler中更方便的运行Pytorch项目，实现了Pytorch任务组件。主要提供便捷的python环境管理以及支持运行python项目。\n与Python任务组件不同，该组件允许用户快速使用已有python环境或者创建新的python环境（使用virtualenv或者conda）；支持运行Python项目（本地项目或者Git项目）而非只是python脚本。\n创建任务\n\n点击项目管理-项目名称-工作流定义，点击“创建工作流”按钮，进入 DAG 编辑页面；\n拖动工具栏的 任务节点到画板中。\n\n任务样例\n组件图示如下：\n\nPytorch参数\n\n默认参数说明请参考DolphinScheduler任务参数附录默认任务参数一栏。\n\n运行参数\n\n\n\n任务参数\n描述\n\n\n\n\npython脚本\n需要运行的python脚本文件入口\n\n\n脚本启动参数\n运行时的输入�
�数\ [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/task/pytorch",
+ "title": "Pytorch 节点（试验版）",
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Pytorch"
+ ]
+ },
+ {
+ "content": "内置参数\n基础内置参数\n\n 变量名声明方式含义\n \n system.biz.date\n ${system.biz.date}\n 日常调度实例定时的定时时间前一天，格式为 yyyyMMdd\n \n \n system.biz.curdate\n ${system.biz.curdate}\n 日常调度实例定时的定时时间，格式为 yyyyMMdd\n \n \n system.datetime\n ${system.datetime}\n 日常调度实例定时的定时时间，格式为 yyyyMMddHHmmss\n \n\n衍生内置参数\n\n\n支持代码中自定义变量名，声明方式：${变量名}。可以是引用 "系统参数"\n\n\n我们定义这种基准变量为 $[...] 格式的，$[yyyyMMddHHmmss] 是可以任意分解组合的，比如：$[yyyy [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/parameter/built-in",
+ "title": "内置参数",
+ "location": [
+ "功能介绍",
+ "参数",
+ "内置参数"
+ ]
+ },
+ {
+ "content": "全局参数\n作用域\n全局参数是指针对整个工作流的所有任务节点都有效的参数，在工作流定义页面配置。\n使用方式\n具体的使用方式可结合实际的生产情况而定，这里演示为使用 Shell 任务打印出前一天的日期。\n创建 Shell 任务\n创建一个 Shell 任务，并在脚本内容中输入 echo ${dt}。此时 dt 则为我们需要声明的全局参数。如下图所示：\n\n保存工作流，并设置全局参数\n全局参数配置方式如下：在工作流定义页面，点击“设置全局”右边的加号，填写对应的变量名称和对应的值，保存即可。如下图所示：\n\n\n注：这里定义的 dt 参数可以被其它任一节点的局部参数引用。\n\n任务实例查看执行结果\n进入任务实例页面，可以通过查看日志，验证任务的执行结果，判断参数是否有效。\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/parameter/global",
+ "title": "全局参数",
+ "location": [
+ "功能介绍",
+ "参数",
+ "全局参数"
+ ]
+ },
+ {
+ "content": "本地参数\n作用域\n在任务定义页面配置的参数，默认作用域仅限该任务，如果配置了参数传递则可将该参数作用到下游任务中。\n使用方式\n本地参数配置方式如下：在任务定义页面，点击“自定义参数”右边的加号，填写对应的变量名称和对应的值，保存即可。\n\n如果要在单个任务中使用参数，请参阅通过自定义参数使用\n如果要在任务中使用配置参数并在下游任务中使用它们：\n\n如果你只是想要简单使用，且不使用自定义参数, 请参阅 通过 setValue 和自定义参数 export 本地参数\n如果想要使用自定义参数, 请参阅 通过 setValue 和自定义参数 export 本地参数\n如果想要使用 Bash 参数, 请参阅 通过 setValue 和 Bash 环境变量参数 export 本地参数\n\n\n\n任务样例\n通过自定义参数使用\n本样例展示了如何使用本地参数，打印输出当前日期。创建一�
� Shell 任务，并编写脚本内容为 echo ${dt}。点击配置栏中的自定义参数，配置如下图所示：\n\n参数说明：\n\ndt：参数名\nIN：I [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/parameter/local",
+ "title": "本地参数",
+ "location": [
+ "功能介绍",
+ "参数",
+ "本地参数"
+ ]
+ },
+ {
+ "content": "参数的引用\nDolphinScheduler 提供参数间相互引用的能力，包括：本地参数引用全局参数、上下游参数传递。因为有引用的存在，就涉及当参数名相同时，参数的优先级问题，详见参数优先级\n本地任务引用全局参数\n本地任务引用全局参数的前提是，你已经定义了全局参数，使用方式和本地参数中的使用方式类似，但是参数的值需要配置成全局参数中的 key。\n上游任务传递给下游任务\nDolphinScheduler 允许在任务间进行参数传递，目前传递方向仅支持上游单向传递给下游。目前支持这个特性的任务类型有：\n\nShell\nSQL\nProcedure\nPython\n\n当定义上游节点时，如果有需要将该节点的结果传递给有依赖关系的下游节点，需要在【当前节点设置】的【自定义参数】设置一个方向是 OUT 的变量。目前我们主要针对 SQL 和 SHELL 节点做了可以向下传递参数的
功能。\n上游传递的参数可以在下游节点中被更新，更新方法与设置参数相同。\n如果定义了同名的传递参数，上游节点的参数将被覆盖。\n\n注：若节点之间没有依赖关系， [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/parameter/context",
+ "title": "参数的引用",
+ "location": [
+ "功能介绍",
+ "参数",
+ "参数传递"
+ ]
+ },
+ {
+ "content": "参数优先级\nDolphinScheduler 中所涉及的参数值的定义可能来自三种类型：\n\n全局参数：在工作流保存页面定义时定义的变量\n上游任务传递的参数：上游任务传递过来的参数\n本地参数：节点的自有变量，用户在“自定义参数”定义的变量，并且用户可以在工作流定义时定义该部分变量的值\n\n因为参数的值存在多个来源，当参数名相同时，就需要会存在参数优先级的问题。DolphinScheduler 参数的优先级从高到低为：本地参数 > 上游任务传递的参数 > 全局参数\n在上游任务传递的参数中，由于上游可能存在多个任务向下游传递参数，当上游传递的参数名称相同时：\n\n下游节点会优先使用值为非空的参数\n如果存在多个值为非空的参数，则按照上游任务的完成时间排序，选择完成时间最早的上游任务对应的参数\n\n例子\n下面例子向你展示�
��何使用任务参数传递的优先级问题\n1：先以 shell 节点解释第一种情况\n\n节点 【useParam】可以使用到节点【createParam】中设置的变量。而节点 【useParam】与节点【 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/parameter/priority",
+ "title": "参数优先级",
+ "location": [
+ "功能介绍",
+ "参数",
+ "参数优先级"
+ ]
+ },
+ {
+ "content": "MySQL 数据源\n\n\n数据源：选择 MYSQL\n数据源名称：输入数据源的名称\n描述：输入数据源的描述\nIP 主机名：输入连接 MySQL 的 IP\n端口：输入连接 MySQL 的端口\n用户名：设置连接 MySQL 的用户名\n密码：设置连接 MySQL 的密码\n数据库名：输入连接 MySQL 的数据库名称\nJdbc 连接参数：用于 MySQL 连接的参数设置，以 JSON 形式填写\n\n是否原生支持\n否，使用前需请参考 数据源配置 中的 "数据源中心" 章节激活数据源。\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/datasource/mysql",
+ "title": "MySQL 数据源",
+ "location": [
+ "功能介绍",
+ "数据源中心",
+ "MySQL"
+ ]
+ },
+ {
+ "content": "POSTGRESQL 数据源\n\n\n数据源：选择 POSTGRESQL\n数据源名称：输入数据源的名称\n描述：输入数据源的描述\nIP 主机名：输入连接 POSTGRESQL 的 IP\n端口：输入连接 POSTGRESQL 的端口\n用户名：设置连接 POSTGRESQL 的用户名\n密码：设置连接 POSTGRESQL 的密码\n数据库名：输入连接 POSTGRESQL 的数据库名称\nJdbc 连接参数：用于 POSTGRESQL 连接的参数设置，以 JSON 形式填写\n\n是否原生支持\n是，数据源不需要任务附加操作即可使用。\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/datasource/postgresql",
+ "title": "POSTGRESQL 数据源",
+ "location": [
+ "功能介绍",
+ "数据源中心",
+ "PostgreSQL"
+ ]
+ },
+ {
+ "content": "HIVE数据源\n使用HiveServer2\n\n\n数据源：选择 HIVE\n数据源名称：输入数据源的名称\n描述：输入数据源的描述\nIP 主机名：输入连接 HIVE 的 IP\n端口：输入连接 HIVE 的端口\n用户名：设置连接 HIVE 的用户名\n密码：设置连接 HIVE 的密码\n数据库名：输入连接 HIVE 的数据库名称\nJdbc 连接参数：用于 HIVE 连接的参数设置，以 JSON 形式填写\n\n\n注意：如果您希望在同一个会话中执行多个 HIVE SQL，您可以修改配置文件 common.properties 中的配置，设置 support.hive.oneSession = true。\n这对运行 HIVE SQL 前设置环境变量的场景会很有帮助。参数 support.hive.oneSession 默认值为 false，多条 SQL 将在不同的会话中运行。\n\n使用 HiveServer2 HA Zookeeper\n\n注意：如果没有开启 kerberos,请保证参数 hadoop.security.a [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/datasource/hive",
+ "title": "HIVE数据源",
+ "location": [
+ "功能介绍",
+ "数据源中心",
+ "HIVE"
+ ]
+ },
+ {
+ "content": "Spark数据源\n\n\n数据源：选择 Spark\n数据源名称：输入数据源的名称\n描述：输入数据源的描述\nIP/主机名：输入连接Spark的IP\n端口：输入连接Spark的端口\n用户名：设置连接Spark的用户名\n密码：设置连接Spark的密码\n数据库名：输入连接Spark的数据库名称\nJdbc连接参数：用于Spark连接的参数设置，以JSON形式填写\n\n注意：如果开启了kerberos，则需要填写 Principal\n\n \n \n是否原生支持\n是，数据源不需要任务附加操作即可使用。\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/datasource/spark",
+ "title": "Spark数据源",
+ "location": [
+ "功能介绍",
+ "数据源中心",
+ "Spark"
+ ]
+ },
+ {
+ "content": "AWS Athena 数据源\n\n\n数据源：选择 ATHENA\n数据源名称：输入数据源的名称\n描述：输入数据源的描述\n用户名：设置连接 AWS 的 access key\n密码：设置连接 AWS 的 secret access key\nAwsRegion: 设置连接 AWS 的区域\n数据库名：输入连接 ATHENA 的数据库名称\nJdbc 连接参数：用于 ATHENA 连接的参数设置，以 JSON 形式填写\n\n是否原生支持\n\n否，使用前需请参考 数据源配置 中的 "数据源中心" 章节激活数据源。\nJDBC驱动配置参考文档 athena-connect-with-jdbc\n驱动下载链接 SimbaAthenaJDBC-2.0.31.1000/AthenaJDBC42.jar\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/datasource/athena",
+ "title": "AWS Athena 数据源",
+ "location": [
+ "功能介绍",
+ "数据源中心",
+ "Amazon Athena"
+ ]
+ },
+ {
+ "content": "如何创建告警插件以及告警组\n在 2.0.0 版本中，用户需要创建告警实例，在创建告警实例时，需要选择告警策略，有三个选项，成功发、失败发，以及成功和失败都发。在执行完工作流或任务时，如果触发告警，调用告警实例发送方法会进行逻辑判断，将告警实例与任务状态进行匹配，匹配则执行该告警实例发送逻辑，不匹配则过滤。创建完告警实例后，需要同告警组进行关联，一个告警组可以使用多个告警实例。\n告警模块支持场景如下：\n\n使用步骤如下：\n首先需要进入到安全中心，选择告警组管理，然后点击左侧的告警实例管理，然后创建一个告警实例，然后选择对应的告警插件，填写相关告警参数。\n然后选择告警组管理，创建告警组，选择相应的告警实例即可。\n\n\n\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/alert/alert_plugin_user_guide",
+ "title": "如何创建告警插件以及告警组",
+ "location": [
+ "功能介绍",
+ "告警",
+ "告警组件向导"
+ ]
+ },
+ {
+ "content": "Email\n如果需要使用Email进行告警，请在告警实例管理中创建告警实例，并选择Email插件。\n下面显示了 Email 配置示例：:\n\n\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/alert/email",
+ "title": "Email",
+ "location": [
+ "功能介绍",
+ "告警",
+ "Email"
+ ]
+ },
+ {
+ "content": "Telegram\n如果您需要使用 Telegram 进行告警，请在告警实例管理模块创建告警实例，选择 Telegram 插件。\nTelegram 的配置样例如下:\n\n参数配置:\n\nWebHook:\n\n\n使用 Telegram 的机器人，发送消息的 WebHook。\n\nbotToken\n创建 Telegram 的机器人，获取的访问令牌。\nchatId\n订阅的 Telegram 频道\nparseMode\n消息解析类型, 支持: txt、markdown、markdownV2、html\nEnableProxy\n开启代理\nProxy\n代理地址\nPort\n代理端口\nUser\n代理鉴权用户\nPassword\n代理鉴权密码\n\n\n注意：用户配置的 WebHook 需要能够接收和使用与 DolphinScheduler 构造的 HTTP POST 请求 BODY 相同的结构，JSON 结构如下：\n{\n "text": "[{\\"projectId\ [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/alert/telegram",
+ "title": "Telegram",
+ "location": [
+ "功能介绍",
+ "告警",
+ "Telegram"
+ ]
+ },
+ {
+ "content": "钉钉\n如果您需要使用到钉钉进行告警，请在告警实例管理里创建告警实例，选择 DingTalk 插件。钉钉的配置样例如下:\n\n参数配置\n\n\nWebhook\n\n格式如下：https://oapi.dingtalk.com/robot/send?access_token=XXXXXX\n\n\n\nKeyword\n\n安全设置的自定义关键词\n\n\n\nSecret\n\n安全设置的加签\n\n\n\n消息类型\n\n支持 text 和 markdown 两种类型\n\n\n\n自定义机器人发送消息时，可以通过手机号码指定“被@人列表”。在“被@人列表”里面的人员收到该消息时，会有@消息提醒。免打扰会话仍然通知提醒，首屏出现“有人@你”\n\n@Mobiles\n\n\n被@人的手机号\n\n@UserIds\n被@人的用户userid\n@All\n是否@所有人\n\n\n钉钉自定义机器人接入开发文档\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/alert/dingtalk",
+ "title": "钉钉",
+ "location": [
+ "功能介绍",
+ "告警",
+ "钉钉告警"
+ ]
+ },
+ {
+ "content": "企业微信\n如果您需要使用到企业微信进行告警，请在告警实例管理里创建告警实例，选择 WeChat 插件。企业微信的配置样例如下：\n\n发送类型\n其中send.type分别对应向企业微信自定义应用发送和向企业微信API创建的群聊发送消息。\n应用\n应用指将告警结果通过企业微信的自定义应用进行通知，支持向特定用户发送消息和对所有人发送消息。目前还不支持部门和标签，欢迎提PR贡献代码。\n下图是应用告警配置的示例:\n\n下图是应用``MARKDOWN告警消息的示例:\n\n下图是应用``TEXT告警消息的示例:\n\n前置\n向企业微信应用发送消息之前需要在企业微信中创建自定义应用，请在应用页面 进行创建,获取应用的AgentId并将可见范围设为根。\n向指定用户发消息\n企业微信应用支持向特定用户发送消息和对所有人发送消息，分别为使用|分隔多个userId和�
��用@all向所有人发送信息。\n获取用户的userId请参考官方文档根据手机号获取userId。\n下图是获取userId接口的示例:\n\n参考文档\n应用：https://w [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/alert/enterprise-wechat",
+ "title": "企业微信",
+ "location": [
+ "功能介绍",
+ "告警",
+ "企业微信"
+ ]
+ },
+ {
+ "content": "WebexTeams\n如果您需要使用到Webex Teams进行告警，请在告警实例管理里创建告警实例，选择 WebexTeams 插件。\n你可以选择机器人私聊通知或聊天室通知。\nWebexTeams的配置样例如下:\n\n参数配置\n\n\nbotAccessToken\n\n在创建机器人时，获得的访问令牌\n\n\n\nroomID\n\n接受消息的room ID(只支持一个ID)\n\n\n\ntoPersonId\n\n接受消息的用户ID(只支持一个ID)\n\n\n\ntoPersonEmail\n\n接受消息的用户邮箱(只支持一个邮箱)\n\n\n\natSomeoneInRoom\n\n如果消息目的地为room，被@人的用户邮箱，多个邮箱用英文逗号分隔\n\n\n\ndestination\n\n消息目的地，一条消息只支持一个目的地\n\n\n\n创建一个机器人\n访问官网My-Apps来创建一个机器人，点击Create a New APP 然后选择 Create a Bot，填入机器人信息后获取bot username [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/alert/enterprise-webexteams",
+ "title": "WebexTeams",
+ "location": [
+ "功能介绍",
+ "告警",
+ "Webexteams"
+ ]
+ },
+ {
+ "content": "Script脚本\n如果您需要使用到Shell脚本进行告警，请在告警实例管理里创建告警实例，选择Script插件。Script的配置样例如下:\n\n参数配置\n\n\n自定义参数\n\n用户自定义的参数将被传入脚本执行\n\n\n\n脚本路径\n\n脚本在服务器上的文件位置\n\n\n\n脚本类型\n\n支持Shell脚本\n\n\n\n注意： 请注意脚本的读写权限与执行租户的关系\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/alert/script",
+ "title": "Script脚本",
+ "location": [
+ "功能介绍",
+ "告警",
+ "脚本告警"
+ ]
+ },
+ {
+ "content": "HTTP告警\n如果您需要使用到Http（GET或POST）进行告警，请在告警实例管理里创建告警实例，选择Http插件。\n参数配置\n\n\nURL\n\n访问的Http连接URL,需要包含协议、Host、路径，如果是GET方法可以添加参数\n\n\n\n请求方式\n\n选择该请求为POST或GET方法\n\n\n\n请求头\n\nHttp请求的完整请求头，以JSON为格式\n\n\n\n请求体\n\nHttp请求的完整请求体，以JSON为格式，GET方法不需要写该参数\n\n\n\n内容字段\n\n放置本次告警告警信息的字段名称\n\n\n\n发送类型\n其中Request Type分别对应使用POST方法和GET方法进行Http告警。\nGET Http告警\nGET Http告警指将告警结果作为参数通过Http GET方法进行请求。\n下图是GET告警配置的示例:\n\nPOST Http告警\nPOST Http告警指将告警结果作为BODY参数通过HttpPOST方法进行请求。\n下图是POST告警配置的示例:\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/alert/http",
+ "title": "HTTP告警",
+ "location": [
+ "功能介绍",
+ "告警",
+ "Http告警"
+ ]
+ },
+ {
+ "content": "飞书\n如果您需要使用到飞书进行告警，请在告警实例管理里创建告警实例，选择 Feishu 插件。飞书的配置样例如下:\n\n参数配置\n\n\nWebhook\n\n复制机器人的webhook地址,如下图所示：\n\n\n\n\n飞书：如何在群组中使用机器人？\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/alert/feishu",
+ "title": "飞书",
+ "location": [
+ "功能介绍",
+ "告警",
+ "飞书告警"
+ ]
+ },
+ {
+ "content": "资源中心简介\n资源中心通常用于上传文件、UDF 函数和任务组管理。 对于 standalone 环境，可以选择本地文件目录作为上传文件夹（此操作不需要Hadoop部署）。当然，你也可以\n选择上传到 Hadoop 或者 MinIO 集群。 在这种情况下，您需要有 Hadoop（2.6+）或 MinION 等相关环境。\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/resource/intro",
+ "title": "资源中心简介",
+ "location": [
+ "功能介绍",
+ "资源中心",
+ "简介"
+ ]
+ },
+ {
+ "content": "资源中心配置详情\n\n资源中心通常用于上传文件、UDF 函数，以及任务组管理等操作。\n资源中心可以对接分布式的文件存储系统，如Hadoop（2.6+）或者MinIO集群，也可以对接远端的对象存储，如AWS S3或者阿里云 OSS等。\n资源中心也可以直接对接本地文件系统。在单机模式下，您无需依赖Hadoop或S3一类的外部存储系统，可以方便地对接本地文件系统进行体验。\n除此之外，对于集群模式下的部署，您可以通过使用S3FS-FUSE将S3挂载到本地，或者使用JINDO-FUSE将OSS挂载到本地等，再用资源中心对接本地文件系统方式来操作远端对象存储中的文件。\n\n对接本地文件系统\n配置 common.properties 文件\n\n如果您以 集群 模式或者 伪集群 模式部署DolphinScheduler，您需要对以下路径的文件进行配置：api-server/conf/common.properties 和 worker-server/conf/common.properties；\n�
�您以 单机 模式部署DolphinSch [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/resource/configuration",
+ "title": "资源中心配置详情",
+ "location": [
+ "功能介绍",
+ "资源中心",
+ "配置详情"
+ ]
+ },
+ {
+ "content": "文件管理\n当在调度过程中需要使用到第三方的 jar 或者用户需要自定义脚本的情况，可以通过在该页面完成相关操作。可创建的文件类型包括：txt/log/sh/conf/py/java 等。并且可以对文件进行编辑、重命名、下载和删除等操作。\n\n注意：\n\n当您以admin身份等入并操作文件时，需要先给admin设置租户\n\n\n基础操作\n\n创建文件\n文件格式支持以下几种类型：txt、log、sh、conf、cfg、py、java、sql、xml、hql、properties\n\n上传文件\n上传文件：点击"上传文件"按钮进行上传，将文件拖拽到上传区域，文件名会自动以上传的文件名称补全\n\n文件查看\n对可查看的文件类型，点击文件名称，可查看文件详情\n\n下载文件\n点击文件列表的"下载"按钮下载文件或者在文件详情中点击右上角"下载"按钮下载文件\n文件重命名\n\n删除文件\n文件�
�表->点击"删除"按钮，删除指定文件\n重新上传文件\ [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/resource/file-manage",
+ "title": "文件管理",
+ "location": [
+ "功能介绍",
+ "资源中心",
+ "文件管理"
+ ]
+ },
+ {
+ "content": "UDF 管理\n\n资源管理和文件管理功能类似，不同之处是资源管理是上传的 UDF 函数，文件管理上传的是用户程序，脚本及配置文件。\n主要包括以下操作：重命名、下载、删除等。\n\n\n上传 UDF 资源\n\n\n和上传文件相同。\n\n函数管理\n\n\n创建 UDF 函数\n\n点击“创建 UDF 函数”，输入 UDF 函数参数，选择udf资源，点击“提交”，创建 UDF 函数。\n目前只支持 HIVE 的临时 UDF 函数\n\n\n\n\nUDF 函数名称：输入 UDF 函数时的名称\n包名类名：输入 UDF 函数的全路径\nUDF 资源：设置创建的 UDF 对应的资源文件\n\n\n任务样例\n编写 UDF 函数\n用户可以根据实际生产需求，自定义想要的 UDF 函数。这里编写一个在任意字符串的末尾添加 "HelloWorld" 的函数。如下图所示：\n\n配置 UDF 函数\n配置 UDF 函数前，需要先通过资源管理上传所需的函数 jar 包。然后进�
�函数管理，配置相关信息即可。如下图所示：\n\n使用 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/resource/udf-manage",
+ "title": "UDF 管理",
+ "location": [
+ "功能介绍",
+ "资源中心",
+ "UDF 管理"
+ ]
+ },
+ {
+ "content": "任务组管理\n任务组主要用于控制任务实例并发，旨在控制其他资源的压力（也可以控制 Hadoop 集群压力，不过集群会有队列管控）。您可在新建任务定义时，可配置对应的任务组，并配置任务在任务组内运行的优先级。\n任务组配置\n新建任务组\n\n用户点击【资源中心】-【任务组管理】-【任务组配置】-新建任务组\n\n您需要输入图片中信息，其中\n【任务组名称】：任务组在被使用时显示的名称\n【项目名称】：任务组作用的项目，该项为非必选项，如果不选择，则整个系统所有项目均可使用该任务组。\n【资源容量】：允许任务实例并发的最大数量\n查看任务组队列\n\n点击按钮查看任务组使用信息\n\n任务组的使用\n注：任务组的使用适用于由 worker 执行的任务，例如【switch】节点、【condition】节点、【sub_process】等由 master 负责执行�
�节点类型不受任务组控制。\n我们以 shell 节点为例：\n\n关于任务组的配置，您需要做的只需要配置红色框内的部分，其中：\n【任务组名称】：任务组配置页面显示的任务组名称，这里只 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/resource/task-group",
+ "title": "任务组管理",
+ "location": [
+ "功能介绍",
+ "资源中心",
+ "任务组管理"
+ ]
+ },
+ {
+ "content": "监控中心\n服务管理\n\n服务管理主要是对系统中的各个服务的健康状况和基本信息的监控和显示\n\nMaster\n\n主要是 master 的相关信息。\n\n\nWorker\n\n主要是 worker 的相关信息。\n\n\nDatabase\n\n主要是 DB 的健康状况\n\n\n统计管理\nStatistics\n\n\n待执行命令数：统计 t_ds_command 表的数据\n执行失败的命令数：统计 t_ds_error_command 表的数据\n待运行任务数：统计 Zookeeper 中 task_queue 的数据\n待杀死任务数：统计 Zookeeper 中 task_kill 的数据\n\n审计日志\n审计日志的记录提供了有关谁访问了系统，以及他或她在给定时间段内执行了哪些操作的信息，他对于维护安全都很有用。\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/monitor",
+ "title": "监控中心",
+ "location": [
+ "功能介绍",
+ "监控中心"
+ ]
+ },
+ {
+ "content": "安全中心（权限系统）\n\n安全中心只有管理员账户才有权限操作，分别有队列管理、租户管理、用户管理、告警组管理、worker分组管理、令牌管理等功能，在用户管理模块可以对资源、数据源、项目等授权\n管理员登录，默认用户名/密码：admin/dolphinscheduler123\n\n创建队列\n\n队列是在执行 spark、mapreduce 等程序，需要用到“队列”参数时使用的。\n管理员进入安全中心 -> 队列管理页面，点击“创建队列”按钮，创建队列。\n\n\n添加租户\n\n租户对应的是 Linux 的用户，用于 worker 提交作业所使用的用户。如果 linux 没有这个用户，则会导致任务运行失败。你可以通过修改 worker.properties 配置文件中参数 worker.tenant.auto.create=true 实现当 linux 用户不存在时自动创建该用户。worker.tenant.auto.create=true 参数会要求 worker 可以免密运行 sudo 命令\n租户编�
�：租户编码是 Lin [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/security",
+ "title": "安全中心（权限系统）",
+ "location": [
+ "功能介绍",
+ "安全中心"
+ ]
+ },
+ {
+ "content": "指标（Metrics）使用指南\nApache DolphinScheduler通过向外透出指标来提高系统的监控告警能力。 我们使用Micrometer作为指标采集和透出框架。\n目前，我们只支持Prometheus Exporter，但是多样化的Exporter将会持续贡献给用户。\n快速上手\n\n我们提供Apache DolphinScheduler standalone 模式下采集并透出指标的能力，提供用户轻松快速的体验。\n当您在standalone模式下触发任务后，您可通过链接 http://localhost:12345/dolphinscheduler/actuator/metrics 访问生成的metrics列表。\n当您在standalone模式下触发任务后，您可通过链接 http://localhost:12345/dolphinscheduler/actuator/prometheus 访问prometheus格式指标。\n为了给您提供一个一站式的Prometheus + Grafana体验, 我们已经为您准备好了 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/metrics/metrics",
+ "title": "指标（Metrics）使用指南",
+ "location": [
+ "功能介绍",
+ "指标相关",
+ "指标"
+ ]
+ },
+ {
+ "content": "概述\n任务类型介绍\n数据质量任务是用于检查数据在集成、处理过程中的数据准确性。本版本的数据质量任务包括单表检查、单表自定义SQL检查、多表准确性以及两表值比对。数据质量任务的运行环境为Spark2.4.0，其他版本尚未进行过验证，用户可自行验证。\n\n数据质量任务的执行逻辑如下：\n\n\n用户在界面定义任务，用户输入值保存在TaskParam中\n运行任务时，Master会解析TaskParam，封装DataQualityTask所需要的参数下发至Worker。 Worker运行数据质量任务，数据质量任务在运行结束之后将统计结果写入到指定的存储引擎中，当前数据质量任务结果存储在dolphinscheduler的t_ds_dq_execute_result表中\nWorker发送任务结果给Master，Master收到TaskResponse之后会判断任务类型是否为DataQualityTask，如果是的话会根据taskInstanceId从t_ds_dq_execute_result中读取相应的结果，�
�后根据用户配置好的检查方式， [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/data-quality",
+ "title": "概述",
+ "location": [
+ "功能介绍",
+ "数据质量"
+ ]
+ },
+ {
+ "content": "不向前兼容的更新\n本文档记录了各版本之间不兼容的更新内容。在升级到相关版本前，请检查本文档。\ndev\n\nRemove the spark version of spark task (#11860).\n\n3.0.0\n\nCopy and import workflow without 'copy' suffix #10607\nUse semicolon as default sql segment separator #10869\n\n3.1.1\n\nChange the default unix shell executor from sh to bash (#12180).\n\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/upgrade/incompatible",
+ "title": "不向前兼容的更新",
+ "location": [
+ "功能介绍",
+ "升级",
+ "不向前兼容的更新"
+ ]
+ },
+ {
+ "content": "DolphinScheduler 升级\n准备工作\n检查不向前兼容的更改\n在升级之前，您应该检查 incompatible change，因为一些不兼容的更改可能会破坏您当前的功能。\n备份上一版本文件和数据库\n为了防止操作错误导致数据丢失，建议升级之前备份数据，备份方法请结合你数据库的情况来定\n下载新版本的安装包\n在下载页面下载最新版本的二进制安装包，并将二进制包放到与当前 dolphinscheduler 服务不一样的路径中，以下升级操作都需要在新版本的目录进行。\n升级步骤\n停止 dolphinscheduler 所有服务\n根据你部署方式停止 dolphinscheduler 的所有服务，如果你是通过 集群部署 来部署你的 dolphinscheduler 的话，可以通过 sh ./script/stop-all.sh 停止全部服务。\n数据库升级\n修改 ./bin/env/dolphinscheduler_env.sh 中的如下配置（{user}和{password}改成你数据库的用户名和密码），�
�后运行升级脚本。 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/upgrade/upgrade",
+ "title": "DolphinScheduler 升级",
+ "location": [
+ "功能介绍",
+ "升级",
+ "升级步骤"
+ ]
+ },
+ {
+ "content": "DolphinScheduler扩容/缩容 文档\n1. DolphinScheduler扩容文档\n本文扩容是针对现有的DolphinScheduler集群添加新的master或者worker节点的操作说明.\n注意： 一台物理机上不能存在多个master服务进程或者worker服务进程.\n 如果扩容master或者worker节点所在的物理机已经安装了调度的服务,请直接跳到 [1.4.修改配置]. 编辑 ** 所有 ** 节点上的配置文件 `conf/config/install_config.conf`. 新增masters或者workers参数,重启调度集群即可.\n\n1.1. 基础软件安装(必装项请自行安装)\n\n[必装] JDK (1.8+) : 必装，请安装好后在/etc/profile下配置 JAVA_HOME 及 PATH 变量\n[可选] 如果扩容的是worker类型的节点,需要考虑是否要安装外部客户端,比如Hadoop、Hive、Spark 的Client.\n\n注意：DolphinSchedul [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/expansion-reduction",
+ "title": "DolphinScheduler扩容/缩容 文档",
+ "location": [
+ "功能介绍",
+ "扩/缩容"
+ ]
+ },
+ {
+ "content": "Standalone极速体验版\nStandalone 仅适用于 DolphinScheduler 的快速体验.\n如果你是新手，想要体验 DolphinScheduler 的功能，推荐使用Standalone方式体检。如果你想体验更完整的功能，或者更大的任务量，推荐使用伪集群部署。如果你是在生产中使用，推荐使用集群部署或者kubernetes\n\n注意: Standalone 仅建议 20 个以下工作流使用，因为其采用内存式的 H2 Database, Zookeeper Testing Server，任务过多可能导致不稳定，并且如果重启或者停止 standalone-server 会导致内存中数据库里的数据清空。\nStandalone 支持元数据持久化，但是需要使用外部数据库，如 mysql 或者 postgresql，请看配置数据库\n\n前置准备工作\n\nJDK：下载JDK (1.8+)，安装并配置 JAVA_HOME 环境变量，并将其下的 bin 目录追加到 PATH 环境变量中。如果你的环境中已存在，可以跳过这步。\n二 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/installation/standalone",
+ "title": "Standalone极速体验版",
+ "location": [
+ "部署指南",
+ "单机部署(Standalone)"
+ ]
+ },
+ {
+ "content": "伪集群部署\n伪集群部署目的是在单台机器部署 DolphinScheduler 服务，该模式下master、worker、api server 都在同一台机器上\n如果你是新手，想要体验 DolphinScheduler 的功能，推荐使用Standalone方式体检。如果你想体验更完整的功能，或者更大的任务量，推荐使用伪集群部署。如果你是在生产中使用，推荐使用集群部署或者kubernetes\n前置准备工作\n伪分布式部署 DolphinScheduler 需要有外部软件的支持\n\nJDK：下载JDK (1.8+)，安装并配置 JAVA_HOME 环境变量，并将其下的 bin 目录追加到 PATH 环境变量中。如果你的环境中已存在，可以跳过这步。\n二进制包：在下载页面下载 DolphinScheduler 二进制包\n数据库：PostgreSQL (8.2.15+) 或者 MySQL (5.7+)，两者任选其一即可，如 MySQL 则需要 JDBC Driver 8.0.16\n注册中心：ZooKeeper (3.4.6+)，下载地址 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/installation/pseudo-cluster",
+ "title": "伪集群部署",
+ "location": [
+ "部署指南",
+ "伪集群部署(Pseudo-Cluster)"
+ ]
+ },
+ {
+ "content": "集群部署(Cluster)\n集群部署目的是在多台机器部署 DolphinScheduler 服务，用于运行大量任务情况。\n如果你是新手，想要体验 DolphinScheduler 的功能，推荐使用Standalone方式体检。如果你想体验更完整的功能，或者更大的任务量，推荐使用伪集群部署。如果你是在生产中使用，推荐使用集群部署或者kubernetes\n部署步骤\n集群部署(Cluster)使用的脚本和配置文件与伪集群部署中的配置一样，所以所需要的步骤也与伪集群部署大致一样。区别就是伪集群部署针对的是一台机器，而集群部署(Cluster)需要针对多台机器，且两者“修改相关配置”步骤区别较大\n前置准备工作 && 准备 DolphinScheduler 启动环境\n其中除了伪集群部署中的“前置准备工作”，“准备启动环境”除了“启动zookeeper”以及“初始化数据库”外，别的都需要在每台机器中进行配置\
n修改相关配置\n这个是与伪集群部署差异较大的一步，因为部署脚本会通过 scp 的方式将安装需要的资源传输到各个机器上 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/installation/cluster",
+ "title": "集群部署(Cluster)",
+ "location": [
+ "部署指南",
+ "集群部署(Cluster)"
+ ]
+ },
+ {
+ "content": "快速试用 Kubernetes 部署\nKubernetes部署目的是在Kubernetes集群中部署 DolphinScheduler 服务，能调度大量任务，可用于在生产中部署。\n如果你是新手，想要体验 DolphinScheduler 的功能，推荐使用Standalone方式体检。如果你想体验更完整的功能，或者更大的任务量，推荐使用伪集群部署。如果你是在生产中使用，推荐使用集群部署或者kubernetes\n先决条件\n\nHelm 3.1.0+\nKubernetes 1.12+\nPV 供应(需要基础设施支持)\n\n安装 dolphinscheduler\n请下载源码包 apache-dolphinscheduler--src.tar.gz，下载地址: 下载\n发布一个名为 dolphinscheduler 的版本(release)，请执行以下命令：\n$ tar -zxvf apache-dolphinscheduler-<version>-src.tar.gz\n$ cd apache-dolphinsched [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/installation/kubernetes",
+ "title": "快速试用 Kubernetes 部署",
+ "location": [
+ "部署指南",
+ "Kubernetes部署(Kubernetes)"
+ ]
+ },
+ {
+ "content": "基于 Rainbond 部署 DolphinScheduler 高可用集群\n本文描述通过 Rainbond 云原生应用管理平台 一键部署高可用的 DolphinScheduler 集群，这种方式适合给不太了解 Kubernetes、容器化等复杂技术的用户使用，降低了在 Kubernetes 中部署 DolphinScheduler 的门槛。\n前提条件\n\n可用的 Rainbond 云原生应用管理平台，请参阅文档 Rainbond 快速安装\n\nDolphinScheduler 集群一键部署\n\n对接并访问内置的开源应用商店，搜索关键词 dolphinscheduler 即可找到 DolphinScheduler 应用。\n\n\n\n点击 DolphinScheduler 右侧的 安装 进入安装页面，填写对应的信息，点击确定即可开始安装，自动跳转至应用视图。\n\n\n\n\n选择项\n说明\n\n\n\n\n团队名称\n用户自建的工作空间，以命名空间隔离\n\n\n集群名称\n选择 DolphinScheduler 被部署到哪 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/integration/rainbond",
+ "title": "基于 Rainbond 部署 DolphinScheduler 高可用集群",
+ "location": [
+ "部署指南",
+ "集成",
+ "基于Rainbond部署(Cluster)"
+ ]
+ },
+ {
+ "content": "DolphinScheduler 元数据文档\n表Schema\n详见dolphinscheduler/dolphinscheduler-dao/src/main/resources/sql目录下的sql文件\nE-R图\n用户\t队列\t数据源\n\n\n一个租户下可以有多个用户；\nt_ds_user中的queue字段存储的是队列表中的queue_name信息，t_ds_tenant下存的是queue_id，在流程定义执行过程中，用户队列优先级最高，用户队列为空则采用租户队列；\nt_ds_datasource表中的user_id字段表示创建该数据源的用户，t_ds_relation_datasource_user中的user_id表示对数据源有权限的用户；\n\n项目\t资源\t告警\n\n\n一个用户可以有多个项目，用户项目授权通过t_ds_relation_project_user表完成project_id和user_id的关系绑定；\nt_ds_projcet表中的user_id表示创建该项目的用户，t_ds_relation [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/architecture/metadata",
+ "title": "DolphinScheduler 元数据文档",
+ "location": [
+ "架构设计",
+ "元数据文档"
+ ]
+ },
+ {
+ "content": "系统架构设计\n系统架构\n系统架构图\n\n \n \n 系统架构图\n \n\n启动流程活动图\n\n \n \n 启动流程活动图\n \n\n架构说明\n\n\nMasterServer\nMasterServer采用分布式无中心设计理念，MasterServer主要负责 DAG 任务切分、任务提交监控，并同时监听其它MasterServer和WorkerServer的健康状态。\nMasterServer服务启动时向Zookeeper注册临时节点，通过监听Zookeeper临时节点变化来进行容错处理。\nMasterServer基于netty提供监听服务。\n该服务内主要包含:\n\n\nDistributedQuartz分布式调度组件，主要负责定时任务的启停操作，当quartz调起任务后，Master内部会有线程池具体负责处理任务的后续操作；\n\n\nMasterSchedulerService是一个扫描线程，定时扫描数据库中的t_ds_command表，根据不同的命令类型进行不同的业务 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/architecture/design",
+ "title": "系统架构设计",
+ "location": [
+ "架构设计",
+ "架构设计"
+ ]
+ },
+ {
+ "content": "\n前言\n本文档为dolphinscheduler配置文件说明文档。\n目录结构\nDolphinScheduler的目录结构如下：\n├── LICENSE\n│\n├── NOTICE\n│\n├── licenses licenses存放目录\n│\n├── bin DolphinScheduler命令和环境变量配置存放目录\n│ ├── dolphinscheduler-daemon.sh 启动/关闭DolphinScheduler服务脚本\n│ ├── env 环境变量配置存放目录\n│ │ ├── dolphinscheduler_env.sh 当使用`dolphinscheduler-daemon.sh`脚本起停服务时，运行此脚本加载环境变 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/architecture/configuration",
+ "title": "前言",
+ "location": [
+ "架构设计",
+ "配置文件"
+ ]
+ },
+ {
+ "content": "任务总体存储结构\n在dolphinscheduler中创建的所有任务都保存在t_ds_process_definition 表中.\n该数据库表结构如下表所示:\n\n\n\n序号\n字段\n类型\n描述\n\n\n\n\n1\nid\nint(11)\n主键\n\n\n2\nname\nvarchar(255)\n流程定义名称\n\n\n3\nversion\nint(11)\n流程定义版本\n\n\n4\nrelease_state\ntinyint(4)\n流程定义的发布状态：0 未上线 , 1已上线\n\n\n5\nproject_id\nint(11)\n项目id\n\n\n6\nuser_id\nint(11)\n流程定义所属用户id\n\n\n7\nprocess_definition_json\nlongtext\n流程定义JSON\n\n\n8\ndescription\ntext\n流程定义描述\n\n\n9\nglobal_params\ntext\n全局参数\n\n\n10\nflag\ntinyint(4)\ [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/architecture/task-structure",
+ "title": "任务总体存储结构",
+ "location": [
+ "架构设计",
+ "任务结构"
+ ]
+ },
+ {
+ "content": "负载均衡\n负载均衡即通过路由算法（通常是集群环境），合理的分摊服务器压力，达到服务器性能的最大优化。\nDolphinScheduler-Worker 负载均衡算法\nDolphinScheduler-Master 分配任务至 worker,默认提供了三种算法:\n加权随机（random）\n平滑轮询（roundrobin）\n线性负载（lowerweight）\n默认配置为线性加权负载。\n由于路由是在客户端做的，即 master 服务，因此你可以更改 master.properties 中的 master.host.selector 来配置你所想要的算法。\neg：master.host.selector=random（不区分大小写）\nWorker 负载均衡配置\n配置文件 worker.properties\n权重\n上述所有的负载算法都是基于权重来进行加权分配的，权重影响分流结果。你可以在 修改 worker.weight 的值来给不同的机器设置不同的权重。\n预热\n考虑到 JIT 优化，我们会让 worker 在启动后低功 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/architecture/load-balance",
+ "title": "负载均衡",
+ "location": [
+ "架构设计",
+ "负载均衡"
+ ]
+ },
+ {
+ "content": "缓存\n缓存目的\n由于在master-server调度过程中，会产生大量的数据库读取操作，如tenant，user，processDefinition等，一方面对DB产生很大的读压力，另一方面则会使整个核心调度流程变得缓慢；\n考虑到这部分业务数据是读多写少的场景，故引入了缓存模块，以减少DB读压力，加快核心调度流程；\n缓存设置\nspring:\n cache:\n # default enable cache, you can disable by `type: none`\n type: none\n cache-names:\n - tenant\n - user\n - processDefinition\n - processTaskRelation\n - taskDefinition\n caffeine:\n spec: maximumSize=100,expireAfterWrite=300s,recordStats\n\n缓存模 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/architecture/cache",
+ "title": "缓存",
+ "location": [
+ "架构设计",
+ "缓存"
+ ]
+ },
+ {
+ "content": "API 调用\n背景\n一般都是通过页面来创建项目、流程等，但是与第三方系统集成就需要通过调用 API 来管理项目、流程。\n操作步骤\n创建 token\n\n登录调度系统，点击 "安全中心"，再点击左侧的 "令牌管理"，点击 "令牌管理" 创建令牌。\n\n\n\n选择 "失效时间" (Token 有效期)，选择 "用户" (以指定的用户执行接口操作)，点击 "生成令牌" ，拷贝 Token 字符串，然后点击 "提交" 。\n\n\n使用案例\n查询项目列表信息\n\n打开 API 文档页面\n\n\n地址：http://{api server ip}:12345/dolphinscheduler/swagger-ui/index.html?language=zh_CN&lang=cn\n\n\n\n选一个测试的接口，本次测试选取的接口是：查询所有项目\n\n\nprojects/list [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/api/open-api",
+ "title": "API 调用",
+ "location": [
+ "API",
+ "API调用"
+ ]
+ },
+ {
+ "content": "PyDolphinScheduler\nPyDolphinScheduler 是 Apache DolphinScheduler 的 Python API，它允许您通过 Python 代码定义您的工作流，也称为 workflow-as-codes。\n更多信息请参考PyDolphinScheduler\n",
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/api/pydolphinscheduler",
+ "title": "PyDolphinScheduler",
+ "location": [
+ "API",
+ "PyDolphinScheduler"
+ ]
+ },
+ {
+ "content": "健康检查\n背景\n运行状况检查旨在提供一种独特的方法来检查 Dolphinscheduler 服务的运行状况。它包括模块的运行状况，例如 DB、缓存、网络等等。\nEndpoint\nAPI-Server\ncurl --request GET 'http://localhost:12345/dolphinscheduler/actuator/health'\n\n{"status":"UP","components":{"db":{"status":"UP","details":{"database":"H2","validationQuery":"isValid()"}}}}\n\nMaster-Server\ncurl --request GET 'http://localhost:5 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/guide/api/healthcheck",
+ "title": "健康检查",
+ "location": [
+ "API",
+ "健康检查"
+ ]
+ },
+ {
+ "content": "DolphinScheduler Alert SPI 主要设计\nDolphinScheduler SPI 设计\nDolphinScheduler 正在处于微内核 + 插件化的架构更改之中，所有核心能力如任务、资源存储、注册中心等都将被设计为扩展点，我们希望通过 SPI 来提高 DolphinScheduler 本身的灵活性以及友好性（扩展性）。\n告警相关代码可以参考 dolphinscheduler-alert-api 模块。该模块定义了告警插件扩展的接口以及一些基础代码，当我们需要实现相关功能的插件化的时候，建议先阅读此块的代码，当然，更建议你阅读文档，这会减少很多时间，不过文档有一定的后滞性，当文档缺失的时候，建议以源码为准（如果有兴趣，我们也欢迎你来提交相关文档），此外，我们几乎不会对扩展接口做变更（不包括新增），除非重大架构调整，出现不兼容升级版本，因此，现有文档一般都能够满足。\n我们采用了原生�
� JAVA-SPI，当你需要扩展的时候，事实上你只需要关注扩展org.apache.dolphinscheduler.alert [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/contribute/backend/spi/alert",
+ "title": "DolphinScheduler Alert SPI 主要设计",
+ "location": [
+ "贡献指南",
+ "SPI",
+ "Alert SPI"
+ ]
+ },
+ {
+ "content": "DolphinScheduler Datasource SPI 主要设计\n如何使用数据源？\n数据源中心默认支持POSTGRESQL、HIVE/IMPALA、SPARK、CLICKHOUSE、SQLSERVER数据源。\n如果使用的是MySQL、ORACLE数据源则需要、把对应的驱动包放置lib目录下\n如何进行数据源插件开发？\norg.apache.dolphinscheduler.spi.datasource.DataSourceChannel\norg.apache.dolphinscheduler.spi.datasource.DataSourceChannelFactory\norg.apache.dolphinscheduler.plugin.datasource.api.client.CommonDataSourceClient\n\n第一步数据源插件实现以上接口和继承通用client即可，具体可以参考sqlserver、mysql等数据源插件实现，所有RDBMS插件的添加方式都是一样的。\n在数据源插件pom.xml添 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/contribute/backend/spi/datasource",
+ "title": "DolphinScheduler Datasource SPI 主要设计",
+ "location": [
+ "贡献指南",
+ "SPI",
+ "Datasource SPI"
+ ]
+ },
+ {
+ "content": "DolphinScheduler Registry SPI 扩展\n如何使用？\n进行以下配置（以 zookeeper 为例）\n\n\n注册中心插件配置, 以Zookeeper 为例 (registry.properties)\ndolphinscheduler-service/src/main/resources/registry.properties\nregistry.plugin.name=zookeeper\nregistry.servers=127.0.0.1:2181\n\n\n\n具体配置信息请参考具体插件提供的参数信息，例如 zk：org/apache/dolphinscheduler/plugin/registry/zookeeper/ZookeeperConfiguration.java\n所有配置信息前缀需要 +registry，如 base.sleep.time.ms，在 registry 中应该这样配置：registry.base.sleep.time.ms=100\n如何扩展\ndolphinschedul [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/contribute/backend/spi/registry",
+ "title": "DolphinScheduler Registry SPI 扩展",
+ "location": [
+ "贡献指南",
+ "SPI",
+ "Registry SPI"
+ ]
+ },
+ {
+ "content": "DolphinScheduler Task SPI 扩展\n如何进行任务插件开发？\norg.apache.dolphinscheduler.spi.task.TaskChannel\n插件实现以上接口即可。主要包含创建任务（任务初始化，任务运行等方法）、任务取消，如果是 yarn 任务，则需要实现 org.apache.dolphinscheduler.plugin.task.api.AbstractYarnTask。\n我们在 dolphinscheduler-task-api 模块提供了所有任务对外访问的 API，而 dolphinscheduler-spi 模块则是 spi 通用代码库，定义了所有的插件模块，比如告警模块，注册中心模块等，你可以详细阅读查看。\n另外，TaskChannelFactory 继承自 PrioritySPI，这意味着你可以设置插件的优先级，当你有两个插件同名时，你可以通过重写 getIdentify 方法来自定义优先级。高优先级的插件会被加载，但是如果你有两个同名且优先级相同的插件，加载插件时服务器会抛 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/contribute/backend/spi/task",
+ "title": "DolphinScheduler Task SPI 扩展",
+ "location": [
+ "贡献指南",
+ "SPI",
+ "Task SPI"
+ ]
+ },
+ {
+ "content": "DolphinScheduler 开发手册\n软件要求\n在搭建 DolphinScheduler 开发环境之前请确保你已经安装以下软件:\n\nGit\nJDK: v1.8.x (当前暂不支持 jdk 11)\nMaven: v3.5+\nNode: v16.13+ (dolphinScheduler 版本低于 3.0, 请安装 node v12.20+)\nPnpm: v6.x\n\n克隆代码库\n通过你 git 管理工具下载 git 代码，下面以 git-core 为例\nmkdir dolphinscheduler\ncd dolphinscheduler\ngit clone git@github.com:apache/dolphinscheduler.git\n\n编译源码\n支持的系统:\n\nMacOS\nLinux\n\n运行 mvn clean install -Prelease -Dmaven.test.skip=true\n代码风格\nDolphinScheduler使用Spotless检查并修复代码风格和格式问题 [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/contribute/development-environment-setup",
+ "title": "DolphinScheduler 开发手册",
+ "location": [
+ "贡献指南",
+ "环境搭建"
+ ]
+ },
+ {
+ "content": "前端开发文档\n技术选型\nVue mvvm 框架\n\nEs6 ECMAScript 6.0\n\nAns-ui Analysys-ui\n\nD3 可视化库图表库\n\nJsplumb 连线插件库\n\nLodash 高性能的 JavaScript 实用工具库\n\n开发环境搭建\n\n\n\nNode安装\nNode包下载 (注意版本 v12.20.2) https://nodejs.org/download/release/v12.20.2/\n\n\n\n前端项目构建\n用命令行模式 cd 进入 dolphinscheduler-ui项目目录并执行 npm install 拉取项目依赖包\n\n如果 npm install 速度非常慢，你可以设置淘宝镜像\n\nnpm config set registry http://registry.npm.taobao.org/\n\n\n修改 dolphinscheduler-ui/.env 文件中的 API_BASE，用于跟后端交互：\n\n# 代理的接口地址（自行修改）\nAPI [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
+ "link": "/contribute/frontend-development",
+ "title": "前端开发文档",
+ "location": [
+ "贡献指南",
+ "前端开发"
+ ]
+ },
+ {
+ "content": "DSIP\nDolphinScheduler Improvement Proposal (DSIP) 是对 Apache DolphinScheduler 代码库进行的重大改进。它不是为了小修小补存在的，\nDSIP 的目的是通知社区完成或即将完成的重大变更。\n怎样的修改应该被认定为 DSIP\n\n任何重大的新功能、重大改进、引入或删除组件\n任何公共接口的任何重大变化，例如 API接口、web ui 巨大变化\n\n当一个 PR 或者 Issue 是否应该被认定为 DSIP 存疑时，如果有 committer 认为他应该纳入 DAIP 的范畴，那它就应该是 DSIP。\n我们使用 GitHub Issue 和 Apache 邮件列表来记录和保存 DSIP，想要了解更多相关信息，您可以跳转到 当前的 DSIPs 以及 past DSIPs\n作为 DSIP，它应该包含如下部分：\n\n在 dev@dolphinscheduler.apache.org 中有一个以 [DISCUSS][DSIP 为开头的邮件。\n有一个打了 " [...]
+ "version": "3.1.6",
+ "time": "2023-05-15",
"link": "/DSIP",
"title": "DSIP",
"location": [
diff --git a/data/faq/en-us.json b/data/faq/en-us.json
index f3e8df33a6..3312eba820 100644
--- a/data/faq/en-us.json
+++ b/data/faq/en-us.json
@@ -1,343 +1,343 @@
[
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: What's the name of this project?</h2>",
"a": "\n<p>A: DolphinScheduler</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: DolphinScheduler service introduction and recommended running memory</h2>",
"a": "\n<p>A: DolphinScheduler consists of 5 services, MasterServer, WorkerServer, ApiServer, AlertServer, LoggerServer and UI.</p>\n<table>\n<thead>\n<tr>\n<th>Service</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>MasterServer</td>\n<td>Mainly responsible for DAG segmentation and task status monitoring</td>\n</tr>\n<tr>\n<td>WorkerServer/LoggerServer</td>\n<td>Mainly responsible for the submission, execution and update of task status. LoggerServer is used for Rest [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: Which mailboxes does the system support?</h2>",
"a": "\n<p>A: Support most mailboxes, qq, 163, 126, 139, outlook, aliyun, etc. are supported. Support TLS and SSL protocols, these can be configured in the ui of dolphinscheduler:\n<a href=\"../en/guide/alert/email.md\">How to setup email alarm</a>.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: What are the common system variable time parameters and how do I use them?</h2>",
"a": "\n<p>A: Please refer to 'System parameter' in the system-manual</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: pip install kazoo This installation gives an error. Is it necessary to install?</h2>",
"a": "\n<p>A: This is the python connection Zookeeper needs to use, it is used to delete the master/worker temporary node info in the Zookeeper. so you can ignore error if it's your first install. after version 1.3.0, kazoo is not been needed, we use program to replace what kazoo done</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: How to specify the machine running task</h2>",
"a": "\n<p>A: version 1.2 and berfore, Use <strong>the administrator</strong> to create a Worker group, <strong>specify the Worker group</strong> when the <strong>process definition starts</strong>, or <strong>specify the Worker group on the task node</strong>. If not specified, use Default, <strong>Default is to select one of all the workers in the cluster to use for task submission and execution.</strong>\nversion 1.3, you can set worker group for the worker</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: Priority of the task</h2>",
"a": "\n<p>A: We also support <strong>the priority of processes and tasks</strong>. Priority We have five levels of <strong>HIGHEST, HIGH, MEDIUM, LOW and LOWEST</strong>. <strong>You can set the priority between different process instances, or you can set the priority of different task instances in the same process instance.</strong> For details, please refer to the task priority design in the architecture-design.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: dolphinscheduler-grpc gives an error</h2>",
"a": "\n<p>A: Execute in the root directory: mvn -U clean package assembly:assembly -Dmaven.test.skip=true , then refresh the entire project.\nversion 1.3 not use grpc, we use netty directly</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: Does DolphinScheduler support running on windows?</h2>",
"a": "\n<p>A: In theory, <strong>only the Worker needs to run on Linux</strong>. Other services can run normally on Windows. But it is still recommended to deploy on Linux.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: UI compiles node-sass prompt in linux: Error: EACCESS: permission denied, mkdir xxxx</h2>",
"a": "\n<p>A: Install <strong>npm install node-sass --unsafe-perm</strong> separately, then <strong>npm install</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: UI cannot log in normally.</h2>",
"a": "\n<p>A: 1, if it is node startup, check whether the .env API_BASE configuration under dolphinscheduler-ui is the Api Server service address.</p>\n<p> 2, If it is nginx booted and installed via <strong>install-dolphinscheduler-ui.sh</strong>, check if the proxy_pass \t\t\tconfiguration in <strong>/etc/nginx/conf.d/dolphinscheduler.conf</strong> is the Api Server service address</p>\n<p> 3, if the above configuration is correct, then please check if the Api S [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: After the process definition is manually started or scheduled, no process instance is generated.</h2>",
"a": "\n<p>A: 1, first <strong>check whether the MasterServer service exists through jps</strong>, or directly check whether there is a master service in zk from the service monitoring.</p>\n<p> 2,If there is a master service, check <strong>the command status statistics</strong> or whether new records are added in <strong>t_ds_error_command</strong>. If it is added, <strong>please check the message field.</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : The task status is always in the successful submission status.</h2>",
"a": "\n<p>A: 1, <strong>first check whether the WorkerServer service exists through jps</strong>, or directly check whether there is a worker service in zk from the service monitoring.</p>\n<p> 2,If the <strong>WorkerServer</strong> service is normal, you need to <strong>check whether the MasterServer puts the task task in the zk queue. You need to check whether the task is blocked in the MasterServer log and the zk queue.</strong></p>\n<p> 3, if there is no problem [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: Is there a Docker image and a Dockerfile?</h2>",
"a": "\n<p>A: Provide Docker image and Dockerfile.</p>\n<p>Docker image address: https://hub.docker.com/r/escheduler/escheduler_images</p>\n<p>Dockerfile address: https://github.com/qiaozhanwei/escheduler_dockerfile/tree/master/docker_escheduler</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Need to pay attention to the problem in install.sh</h2>",
"a": "\n<p>A: 1, if the replacement variable contains special characters, <strong>use the \\ transfer character to transfer</strong></p>\n<p> 2, installPath="/data1_1T/dolphinscheduler", <strong>this directory can not be the same as the install.sh directory currently installed with one click.</strong></p>\n<p> 3, deployUser = "dolphinscheduler", <strong>the deployment user must have sudo privileges</strong>, because the worker is executed by sudo - [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Process definition and process instance offline exception</h2>",
"a": "\n<p>A : For <strong>versions prior to 1.0.4</strong>, modify the code under the escheduler-api cn.escheduler.api.quartz package.</p>\n<pre><code>public boolean deleteJob(String jobName, String jobGroupName) {\n lock.writeLock().lock();\n try {\n JobKey jobKey = new JobKey(jobName,jobGroupName);\n if(scheduler.checkExists(jobKey)){\n logger.info("try to delete job, job name: {}, job group name: {},", jobName, jobGroupName);\n return sched [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: Can the tenant created before the HDFS startup use the resource center normally?</h2>",
"a": "\n<p>A: No. Because the tenant created by HDFS is not started, the tenant directory will not be registered in HDFS. So the last resource will report an error.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: In the multi-master and multi-worker state, the service is lost, how to be fault-tolerant</h2>",
"a": "\n<p>A: <strong>Note:</strong> <strong>Master monitors Master and Worker services.</strong></p>\n<p> 1，If the Master service is lost, other Masters will take over the process of the hanged Master and continue to monitor the Worker task status.</p>\n<p> 2，If the Worker service is lost, the Master will monitor that the Worker service is gone. If there is a Yarn task, the Kill Yarn task will be retried.</p>\n<p>Please see the fault-tolerant design in the architecture for d [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Fault tolerance for a machine distributed by Master and Worker</h2>",
"a": "\n<p>A: The 1.0.3 version only implements the fault tolerance of the Master startup process, and does not take the Worker Fault Tolerance. That is to say, if the Worker hangs, no Master exists. There will be problems with this process. We will add Master and Worker startup fault tolerance in version <strong>1.1.0</strong> to fix this problem. If you want to manually modify this problem, you need to <strong>modify the running task for the running worker task that is running the [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Timing is easy to set to execute every second</h2>",
"a": "\n<p>A : Note when setting the timing. If the first digit (* * * * * ? *) is set to *, it means execution every second. <strong>We will add a list of recently scheduled times in version 1.1.0.</strong> You can see the last 5 running times online at http://cron.qqe2.com/</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: Is there a valid time range for timing?</h2>",
"a": "\n<p>A: Yes, <strong>if the timing start and end time is the same time, then this timing will be invalid timing. If the end time of the start and end time is smaller than the current time, it is very likely that the timing will be automatically deleted.</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : There are several implementations of task dependencies</h2>",
"a": "\n<p>A:\t1, the task dependency between <strong>DAG</strong>, is <strong>from the zero degree</strong> of the DAG segmentation</p>\n<p>\t\t2, there are <strong>task dependent nodes</strong>, you can achieve cross-process tasks or process dependencies, please refer to the (DEPENDENT) node design in the system-manual.</p>\n<p>\tNote: <strong>Cross-project processes or task dependencies are not supported</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: There are several ways to start the process definition.</h2>",
"a": "\n<p>A: 1, in <strong>the process definition list</strong>, click the <strong>Start</strong> button.</p>\n<p> 2, <strong>the process definition list adds a timer</strong>, scheduling start process definition.</p>\n<p> 3, process definition <strong>view or edit</strong> the DAG page, any <strong>task node right click</strong> Start process definition.</p>\n<p> 4, you can define DAG editing for the process, set the running flag of some tasks to <strong>proh [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Python task setting Python version</h2>",
"a": "\n<p>A:\t1，<strong>for the version after 1.0.3</strong> only need to modify PYTHON_HOME in <code>bin/env/dolphinscheduler_env.sh</code></p>\n<pre><code>export PYTHON_HOME=/bin/python\n</code></pre>\n<p>Note: This is <strong>PYTHON_HOME</strong> , which is the absolute path of the python command, not the simple PYTHON_HOME. Also note that when exporting the PATH, you need to directly</p>\n<pre><code>export PATH=$HADOOP_HOME/bin:$SPARK_HOME1/bin:$SPARK_HOME2/bin:$PYTHON_HOME:$JAV [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Worker Task will generate a child process through sudo -u tenant sh xxx.command, will kill when kill</h2>",
"a": "\n<p>A： We will add the kill task in 1.0.4 and kill all the various child processes generated by the task.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q ： How to use the queue in DolphinScheduler, what does the user queue and tenant queue mean?</h2>",
"a": "\n<p>A ： The queue in the DolphinScheduler can be configured on the user or the tenant. <strong>The priority of the queue specified by the user is higher than the priority of the tenant queue.</strong> For example, to specify a queue for an MR task, the queue is specified by mapreduce.job.queuename.</p>\n<p>Note: When using the above method to specify the queue, the MR uses the following methods:</p>\n<pre><code> Configuration conf = new Configuration();\nGenericOptionsParser [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Master or Worker reports the following alarm</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://analysys.github.io/easyscheduler_docs/images/master_worker_lack_res.png\" width=\"60%\" />\n </p>\n<p>A ： Change the value of master.properties <strong>master.reserved.memory</strong> under conf to a smaller value, say 0.1 or the value of worker.properties <strong>worker.reserved.memory</strong> is a smaller value, say 0.1</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q: The hive version is 1.1.0+cdh5.15.0, and the SQL hive task connection is reported incorrectly.</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://analysys.github.io/easyscheduler_docs/images/cdh_hive_error.png\" width=\"60%\" />\n </p>\n<p>A ： Will hive pom</p>\n<pre><code><dependency>\n <groupId>org.apache.hive</groupId>\n <artifactId>hive-jdbc</artifactId>\n <version>2.3.9</version>\n</dependency>\n</code></pre>\n<p>change into</p>\n<pre><code><dependency>\n <groupId>org.apache.hive</groupId>\n [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : how to add a worker server</h2>",
"a": "\n<p>A: 1, Create deployment user and hosts mapping, please refer 1.3 part of <a href=\"https://dolphinscheduler.apache.org/en-us/docs/laster/user_doc/installation/cluster.html\">cluster deployment</a></p>\n<p>\t\t2, Configure hosts mapping and ssh access and modify directory permissions. please refer 1.4 part of <a href=\"https://dolphinscheduler.apache.org/en-us/docs/laster/user_doc/installation/cluster.html\">cluster deployment</a></p>\n<p>\t\t3, Copy the deployment direct [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : When DolphinScheduler release a new version, and the change between current version and latest, and how to upgrade, and version number specification</h2>",
"a": "\n<p>A: 1, The release process of Apache Project happens in the mailing list. You can subscribe DolphinScheduler's mailing list and then when the release is in process, you'll receive release emails. Please follow this <a href=\"https://github.com/apache/dolphinscheduler#get-help\">introduction</a> to subscribe DolphinScheduler's mailing list.</p>\n<p>2, When new version published, there would be release note which describe the change log, and there also have upgrade document f [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Subsequent tasks can execute even front task failed</h2>",
"a": "\n<p>A: When start the workflow, you can set the task failure strategy: continue or failure.\n<img src=\"https://user-images.githubusercontent.com/15833811/80368215-ee378080-88be-11ea-9074-01a33d012b23.png\" alt=\"set task failure strategy\"></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Workflow template DAG, workflow instance, work task and what is the relationship among them? A DAG supports a maximum concurrency of 100, does it mean that 100 workflow instances are generated and run concurrently? A task node in a DAG also has a concurrent number configuration. Does it mean that tasks can run concurrently with multiple threads? Is the maximum number 100?</h2>",
"a": "\n<p>A:</p>\n<p>1.2.1 version</p>\n<pre><code>master.properties\nControl the max parallel number of master node workflows\nmaster.exec.threads=100\n\nControl the max number of parallel tasks in each workflow\nmaster.exec.task.number=20\n\nworker.properties\nControl the max parallel number of worker node tasks\nworker.exec.threads=100\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Worker group manage page no buttons displayed</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/39816903/81903776-d8cb9180-95f4-11ea-98cb-94ca1e6a1db5.png\" width=\"60%\" />\n</p>\nA: For version 1.3.0, we want to support k8s, while the ip always will be changed, so can't config on the UI, worker can config group name in the worker.properties.\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Why not add mysql jdbc connector to docker image</h2>",
"a": "\n<p>A: The license of mysql jdbc connector is not compatible with apache v2 license, so it can't be included by docker image.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Allways fail when a task instance submit multiple yarn application</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/16174111/81312485-476e9380-90b9-11ea-9aad-ed009db899b1.png\" width=\"60%\" />\n </p>\nA： This bug have fix in dev and in Requirement/TODO list.\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Master server and worker server stop abnormally after run for a few days</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/18378986/81293969-c3101680-90a0-11ea-87e5-ac9f0dd53f5e.png\" width=\"60%\" />\n </p>\nA: Session timeout is too short, only 0.3 seconds. Change the config item in zookeeper.properties:\n<pre><code>zookeeper.session.timeout=60000\nzookeeper.connection.timeout=30000\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Started using the docker-compose default configuration and display zookeeper errors</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/42579056/80374318-13c98780-88c9-11ea-8d5f-53448b957f02.png\" width=\"60%\" />\n </p>\nA: This problem is solved in dev-1.3.0. This [pr](https://github.com/apache/dolphinscheduler/pull/2595) has solved this bug, brief change log:\n<pre><code>1. add zookeeper environment variable ZOO_4LW_COMMANDS_WHITELIST in docker-compose.yml file.\n2. change the data type of minLatency, avgLatency and maxLatency fr [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Interface show some task would be running all the time when db delayed and log show task instance is null</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/51871547/80302626-b1478d00-87dd-11ea-97d4-08aa2244a6d0.jpg\" width=\"60%\" />\n </p>\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/51871547/80302626-b1478d00-87dd-11ea-97d4-08aa2244a6d0.jpg\" width=\"60%\" />\n </p>\n<p>A: This <a href=\"https://github.com/apache/dolphinscheduler/issues/1477\">bug</a> describe the problem detail and it has been been solved in version [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Zookeeper masters znode list ip address is 127.0.0.1, instead of wanted ip eth0 or eth1, and may can't see task log</h2>",
"a": "\n<p>A: bug fix:</p>\n<pre><code>1, confirm hostname\n$hostname\nhadoop1\n2, hostname -i\n127.0.0.1 10.3.57.15\n3, edit /etc/hosts,delete hadoop1 from 127.0.0.1 record\n$cat /etc/hosts\n127.0.0.1 localhost\n10.3.57.15 ds1 hadoop1\n4, hostname -i\n10.3.57.15\n</code></pre>\n<p>Hostname cmd return server hostname, hostname -i return all matched ips configured in /etc/hosts. So after I delete the hostname matched with 127.0.0.1, and only remain internal ip resolution, instead of r [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : The scheduling system set a second frequency task, causing the system to crash</h2>",
"a": "\n<p>A: The scheduling system not support second frequency task.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Compile front-end code(dolphinscheduler-ui) show error cannot download "https://github.com/sass/node-sass/releases/download/v4.13.1/darwin-x64-72_binding.node"</h2>",
"a": "\n<p>A: 1, cd dolphinscheduler-ui and delete node_modules directory</p>\n<pre><code>sudo rm -rf node_modules\n</code></pre>\n<p>\t2, install node-sass through npm.taobao.org</p>\n<pre><code>sudo npm uninstall node-sass\nsudo npm i node-sass --sass_binary_site=https://npm.taobao.org/mirrors/node-sass/\n</code></pre>\n<p>3, if the 2nd step failure, please, <a href=\"https://dolphinscheduler.apache.org/en-us/development/frontend-development.html\">referer url</a></p>\n<pre><code> [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : How to config when use mysql as database instead of postgres</h2>",
"a": "\n<p>A: 1, Edit project root dir maven config file, remove scope test property so that mysql driver can be loaded.</p>\n<pre><code><dependency>\n\t<groupId>mysql</groupId>\n\t<artifactId>mysql-connector-java</artifactId>\n\t<version>${mysql.connector.version}</version>\n\t<scope>test<scope>\n</dependency>\n</code></pre>\n<p>\t2, Edit application-dao.properties and quzrtz.properties config file to use mysql driver.\nDe [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : How does a shell task run</h2>",
"a": "\n<p>A: 1, Where is the executed server? Specify one worker to run the task, you can create worker group in Security Center, then the task can be send to the particular worker. If a worker group have multiple servers, which server actually execute is determined by scheduling and has randomness.</p>\n<p>\t2, If it is a shell file of a path on the server, how to point to the path? The server shell file, involving permissions issues, it is not recommended to do so. It is recommen [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : What’s the best deploy mode you suggest in production env</h2>",
"a": "\n<p>A: 1, I suggest you use 3 nodes for stability if you don't have too many tasks to run. And deploy Master/Worker server on different nodes is better. If you only have one node, you of course only can deploy them together! By the way, how many machines you need is determined by your business. The DolphinScheduler system itself does not use too many resources. Test more, and you'll find the right way to use a few machines.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : DEPENDENT Task Node</h2>",
"a": "\n<p>A: 1, DEPENDENT task node actually does not have script, it used for config data cycle dependent logic, and then add task node after that to realize task cycle dependent.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : How to change the boot port of the master</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/8263441/62352160-0f3e9100-b53a-11e9-95ba-3ae3dde49c72.png\" width=\"60%\" />\n </p>\nA: 1, modify application_master.properties, for example: server.port=12345.\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Scheduled tasks cannot be online</h2>",
"a": "\n<p>A: 1, We can successly create scheduled task and add one record into t_scheduler_schedules table, but when I click online, front page no reaction and will lock table t_scheduler_schedules, and tested set field release_state value to 1 in table t_scheduler_schedules, and task display online state. For DS version above 1.2 table name is t_ds_schedules, other version table name is t_scheduler_schedules.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : What is the address of swagger ui</h2>",
"a": "\n<p>A: 1, For version 3.1.0+ is http://apiServerIp:apiServerPort/dolphinscheduler/swagger-ui/index.html,\nfor version 1.2+ is http://apiServerIp:apiServerPort/dolphinscheduler/doc.html others is http://apiServerIp:apiServerPort/escheduler/doc.html.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Front-end installation package is missing files</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/41460919/61437083-d960b080-a96e-11e9-87f1-297ba3aca5e3.png\" width=\"60%\" />\n </p>\n <p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/41460919/61437218-1b89f200-a96f-11e9-8e48-3fac47eb2389.png\" width=\"60%\" />\n </p>\n<p>A: 1, User changed the config api server config file and item\n<img src=\"https://user-images.githubusercontent.com/41460919/61678323-1b09a680-ad3 [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Upload a relatively large file blocked</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/21357069/58231400-805b0e80-7d69-11e9-8107-7f37b06a95df.png\" width=\"60%\" />\n </p>\nA: 1, Edit ngnix config file, edit upload max size client_max_body_size 1024m.\n<p>\t2, the version of Google Chrome is old, and the latest version of the browser has been updated.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Create a spark data source, click "Test Connection", the system will fall back to the login page</h2>",
"a": "\n<p>A: 1, edit nginx config file /etc/nginx/conf.d/escheduler.conf</p>\n<pre><code>proxy_connect_timeout 300s;\nproxy_read_timeout 300s;\nproxy_send_timeout 300s;\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : Workflow Dependency</h2>",
"a": "\n<p>A: 1, It is currently judged according to natural days, at the end of last month: the judgment time is the workflow A start_time/scheduler_time between '2019-05-31 00:00:00' and '2019-05-31 23:59:59'. Last month: It is judged that there is an A instance completed every day from the 1st to the end of the month. Last week: There are completed A instances 7 days last week. The first two days: Judging yesterday and the day before yesterday, there must be a completed A instance [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q : DS Backend Inteface Document</h2>",
"a": "\n<p>A: 1, http://106.75.43.194:8888/dolphinscheduler/swagger-ui/index.html?language=en.</p>\n<h2>During the operation of dolphinscheduler, the ip address is obtained incorrectly</h2>\n<p>When the master service and worker service are registered with zookeeper, relevant information will be created in the form of ip:port</p>\n<p>If the ip address is obtained incorrectly, please check the network information. For example, in the Linux system, use the <code>ifconfig</code> command [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Deploy for multiple YARN clusters</h2>",
"a": "\n<p>A：By deploying different worker in different yarn clusters，the steps are as follows(eg: AWS EMR):</p>\n<ol>\n<li>\n<p>Deploying the worker server on the master node of the EMR cluster</p>\n</li>\n<li>\n<p>Changing <code>yarn.application.status.address</code> to current emr's yarn url in the <code>conf/common.properties</code></p>\n</li>\n<li>\n<p>Execute command <code>bin/dolphinscheduler-daemon.sh start worker-server</code> to start worker-server</p>\n</li>\n</ol>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Update process definition error: Duplicate key TaskDefinition</h2>",
"a": "\n<p>A：Before DS 2.0.4 (after 2.0.0-alpha), there may be a problem of duplicate keys TaskDefinition due to version switching, which may cause the update workflow to fail; you can refer to the following SQL to delete duplicate data, taking MySQL as an example: (Note: Before operating, be sure to back up the original data, the SQL from pr<a href=\"https://github.com/apache/dolphinscheduler/pull/8408\">#8408</a>)</p>\n<pre><code class=\"language-SQL\"><span class=\"hljs-keyword\"> [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Upgrade from 2.0.1 to 2.0.5 using PostgreSQL database failed</h2>",
"a": "\n<p>A：The repair can be completed by executing the following SQL in the database:</p>\n<pre><code class=\"language-SQL\"><span class=\"hljs-keyword\">update</span> t_ds_version <span class=\"hljs-keyword\">set</span> version<span class=\"hljs-operator\">=</span><span class=\"hljs-string\">'2.0.1'</span>;\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Can not find python-gateway-server in distribute package</h2>",
"a": "\n<p>A：After version 3.0.0-alpha, Python gateway server integrate into API server, and Python gateway service will start when you\nstart API server. If you want disabled when Python gateway service you could change API server configuration in path\n<code>api-server/conf/application.yaml</code> and change attribute <code>python-gateway.enabled : false</code>.</p>\n<hr>\n<p>We will collect more FAQ later</p>\n"
}
diff --git a/data/faq/zh-cn.json b/data/faq/zh-cn.json
index a9588cafeb..94fa1cbdae 100644
--- a/data/faq/zh-cn.json
+++ b/data/faq/zh-cn.json
@@ -1,337 +1,337 @@
[
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：项目的名称是？</h2>",
"a": "\n<p>A：DolphinScheduler</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：DolphinScheduler 服务介绍及建议运行内存</h2>",
"a": "\n<p>A：DolphinScheduler 由 5 个服务组成，MasterServer、WorkerServer、ApiServer、AlertServer、LoggerServer 和 UI。</p>\n<table>\n<thead>\n<tr>\n<th>服务</th>\n<th>说明</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>MasterServer</td>\n<td>主要负责 <strong>DAG</strong> 的切分和任务状态的监控</td>\n</tr>\n<tr>\n<td>WorkerServer/LoggerServer</td>\n<td>主要负责任务的提交、执行和任务状态的更新。LoggerServer 用于 Rest Api 通过 <strong>RPC</strong> 查看日志</td>\n</tr>\n<tr>\n<td>ApiServer</td>\n<td>提供 Rest Api 服务，供 UI 进行调用</td>\n</tr>\n<tr>\n<td>Aler [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：系统支持哪些邮箱？</h2>",
"a": "\n<p>A：支持绝大多数邮箱，qq、163、126、139、outlook、aliyun 等皆支持。支持 <strong>TLS 和 SSL</strong> 协议，可以在dolphinscheduler的ui中进行配置：\n<a href=\"../zh/guide/alert/email.md\">如何配置邮箱告警</a>。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：常用的系统变量时间参数有哪些，如何使用？</h2>",
"a": "\n<p>A：请参考<a href=\"https://dolphinscheduler.apache.org/zh-cn/docs/latest/user_doc/guide/parameter/built-in.html\">使用手册</a> 第8小节</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：pip install kazoo 这个安装报错。是必须安装的吗？</h2>",
"a": "\n<p>A： 这个是 python 连接 Zookeeper 需要使用到的，用于删除Zookeeper中的master/worker临时节点信息。所以如果是第一次安装，就可以忽略错误。在1.3.0之后，kazoo不再需要了，我们用程序来代替kazoo所做的</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：怎么指定机器运行任务</h2>",
"a": "\n<p>A：使用 <strong>管理员</strong> 创建 Worker 分组，在 <strong>流程定义启动</strong> 的时候可<strong>指定Worker分组</strong>或者在<strong>任务节点上指定Worker分组</strong>。如果不指定，则使用 Default，<strong>Default默认是使用的集群里所有的Worker中随机选取一台来进行任务提交、执行</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：任务的优先级</h2>",
"a": "\n<p>A：我们同时 <strong>支持流程和任务的优先级</strong>。优先级我们有 <strong>HIGHEST、HIGH、MEDIUM、LOW 和 LOWEST</strong> 五种级别。<strong>可以设置不同流程实例之间的优先级，也可以设置同一个流程实例中不同任务实例的优先级</strong>。详细内容请参考任务优先级设计 https://analysys.github.io/easyscheduler_docs_cn/%E7%B3%BB%E7%BB%9F%E6%9E%B6%E6%9E%84%E8%AE%BE%E8%AE%A1.html#%E7%B3%BB%E7%BB%9F%E6%9E%B6%E6%9E%84%E8%AE%BE%E8%AE%A1</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：dolphinscheduler-grpc 报错</h2>",
"a": "\n<p>A：在 1.2 及以前版本中，在根目录下执行：mvn -U clean package assembly:assembly -Dmaven.test.skip=true,然后刷新下整个项目就好，1.3版本中不再使用 GRPC 进行通信了</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：DolphinScheduler 支持 windows 上运行么</h2>",
"a": "\n<p>A： 理论上只有 <strong>Worker 是需要在 Linux 上运行的</strong>，其它的服务都是可以在 windows 上正常运行的。但是还是建议最好能在 linux 上部署使用</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：UI 在 linux 编译 node-sass 提示：Error：EACCESS:permission denied，mkdir xxxx</h2>",
"a": "\n<p>A：单独安装 <strong>npm install node-sass --unsafe-perm</strong>，之后再 <strong>npm install</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：UI 不能正常登陆访问</h2>",
"a": "\n<p>A： 1，如果是 node 启动的查看 dolphinscheduler-ui 下的 .env 文件里的 API_BASE 配置是否是 Api Server 服务地址</p>\n<p> 2，如果是 nginx 启动的并且是通过 <strong>install-dolphinscheduler-ui.sh</strong> 安装的，查看</p>\n<p> <strong>/etc/nginx/conf.d/dolphinscheduler.conf</strong> 中的 proxy_pass 配置是否是 Api Server 服务地址</p>\n<p> 3，如果以上配置都是正确的，那么请查看 Api Server 服务是否是正常的，</p>\n<p>\t\t\tcurl http://localhost:12345/dolphinscheduler/users/get-user-info 查看 Api Server 日志，</p>\n<p>\t\t\t如果提示 cn.dol [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：流程定义手动启动或调度启动之后，没有流程实例生成</h2>",
"a": "\n<p>A： \t 1，首先通过 <strong>jps 查看MasterServer服务是否存在</strong>，或者从服务监控直接查看 zk 中是否存在 master 服务</p>\n<p>\t 2，如果存在 master 服务，查看 <strong>命令状态统计</strong> 或者 <strong>t_ds_error_command</strong> 中是否增加的新记录，如果增加了，<strong>请查看 message 字段定位启动异常原因</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：任务状态一直处于提交成功状态</h2>",
"a": "\n<p>A： 1，首先通过 <strong>jps 查看 WorkerServer 服务是否存在</strong>，或者从服务监控直接查看 zk 中是否存在 worker 服务</p>\n<p> 2，如果 <strong>WorkerServer</strong> 服务正常，需要 <strong>查看 MasterServer 是否把 task 任务放到 zk 队列中</strong> ，<strong>需要查看 MasterServer 日志及 zk 队列中是否有任务阻塞</strong></p>\n<p>\t 3，如果以上都没有问题，需要定位是否指定了 Worker 分组，但是 <strong>Worker 分组的机器不是在线状态</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：install.sh 中需要注意问题</h2>",
"a": "\n<p>A： \t 1，如果替换变量中包含特殊字符，<strong>请用 \\ 转移符进行转移</strong></p>\n<p>\t 2，installPath="/data1_1T/dolphinscheduler"，<strong>这个目录不能和当前要一键安装的 install.sh 目录是一样的</strong></p>\n<p>\t 3，deployUser="dolphinscheduler"，<strong>部署用户必须具有 sudo 权限</strong>，因为 worker 是通过 sudo -u 租户 sh xxx.command 进行执行的</p>\n<p>\t 4，monitorServerState="false"，服务监控脚本是否启动，默认是不启动服务监控脚本的。<strong>如果启动服务监控脚本，则每 5 分钟定时来监控 master 和 worker 的服务是否 down 机，如果 down 机则会自动重启</strong>< [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：流程定义和流程实例下线异常</h2>",
"a": "\n<p>A ： 对于 <strong>1.0.4 以前的版本中</strong>，修改 dolphinscheduler-api cn.dolphinscheduler.api.quartz 包下的代码即可</p>\n<pre><code>public boolean deleteJob(String jobName, String jobGroupName) {\n lock.writeLock().lock();\n try {\n JobKey jobKey = new JobKey(jobName,jobGroupName);\n if(scheduler.checkExists(jobKey)){\n logger.info("try to delete job, job name: {}, job group name: {},", jobName, jobGroupName);\n return scheduler.deleteJob(jobKey);\n [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：HDFS 启动之前创建的租户，能正常使用资源中心吗</h2>",
"a": "\n<p>A： 不能。因为在未启动 HDFS 创建的租户，不会在 HDFS 中注册租户目录。所以上次资源会报错</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：多 Master 和多 Worker 状态下，服务掉了，怎么容错</h2>",
"a": "\n<p>A： <strong>注意：Master 监控 Master 及 Worker 服务。</strong></p>\n<p>\t1，如果 Master 服务掉了，其它的 Master 会接管挂掉的 Master 的流程，继续监控 Worker task 状态</p>\n<p>\t2，如果 Worker 服务掉了，Master 会监控到 Worker 服务掉了，如果存在 Yarn 任务，Kill Yarn 任务之后走重试</p>\n<p>具体请看容错设计：https://analysys.github.io/easyscheduler_docs_cn/%E7%B3%BB%E7%BB%9F%E6%9E%B6%E6%9E%84%E8%AE%BE%E8%AE%A1.html#%E7%B3%BB%E7%BB%9F%E6%9E%B6%E6%9E%84%E8%AE%BE%E8%AE%A1</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：对于 Master 和 Worker 一台机器伪分布式下的容错</h2>",
"a": "\n<p>A ： 1.0.3 版本只实现了 Master 启动流程容错，不走 Worker 容错。也就是说如果 Worker 挂掉的时候，没有 Master 存在。这流程将会出现问题。我们会在 <strong>1.1.0</strong> 版本中增加 Master 和 Worker 启动自容错，修复这个问题。如果想手动修改这个问题，需要针对 <strong>跨重启正在运行流程</strong> <strong>并且已经掉的正在运行的 Worker 任务，需要修改为失败</strong>，<strong>同时跨重启正在运行流程设置为失败状态</strong>。然后从失败节点进行流程恢复即可</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：定时容易设置成每秒执行</h2>",
"a": "\n<p>A ： 设置定时的时候需要注意，如果第一位（* * * * * ? *）设置成 * ，则表示每秒执行。<strong>我们将会在 1.1.0 版本中加入显示最近调度的时间列表</strong> ，使用 http://cron.qqe2.com/ 可以在线看近 5 次运行时间</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：定时有有效时间范围吗</h2>",
"a": "\n<p>A：有的，<strong>如果定时的起止时间是同一个时间，那么此定时将是无效的定时</strong>。<strong>如果起止时间的结束时间比当前的时间小，很有可能定时会被自动删除</strong></p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：任务依赖有几种实现</h2>",
"a": "\n<p>A： 1，<strong>DAG</strong> 之间的任务依赖关系，是从 <strong>入度为零</strong> 进行 DAG 切分的</p>\n<p>\t 2，有 <strong>任务依赖节点</strong> ，可以实现跨流程的任务或者流程依赖，具体请参考 依赖(DEPENDENT)节点：https://analysys.github.io/easyscheduler_docs_cn/%E7%B3%BB%E7%BB%9F%E4%BD%BF%E7%94%A8%E6%89%8B%E5%86%8C.html#%E4%BB%BB%E5%8A%A1%E8%8A%82%E7%82%B9%E7%B1%BB%E5%9E%8B%E5%92%8C%E5%8F%82%E6%95%B0%E8%AE%BE%E7%BD%AE</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：流程定义有几种启动方式</h2>",
"a": "\n<p>A： 1，在 <strong>流程定义列表</strong>，点击 <strong>启动</strong> 按钮</p>\n<p>\t\t2，<strong>流程定义列表添加定时器</strong>，调度启动流程定义</p>\n<p>\t\t3，流程定义 <strong>查看或编辑</strong> DAG 页面，任意 <strong>任务节点右击</strong> 启动流程定义</p>\n<p>\t\t4，可以对流程定义 DAG 编辑，设置某些任务的运行标志位 <strong>禁止运行</strong>，则在启动流程定义的时候，将该节点的连线将从 DAG 中去掉</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Python 任务设置 Python 版本</h2>",
"a": "\n<p>A： 只需要修改 <code>bin/env/dolphinscheduler_env.sh</code> 中的 PYTHON_HOME</p>\n<pre><code>export PYTHON_HOME=/bin/python\n</code></pre>\n<p>注意：这了 <strong>PYTHON_HOME</strong> ，是 python 命令的绝对路径，而不是单纯的 PYTHON_HOME，还需要注意的是 export PATH 的时候，需要直接</p>\n<pre><code>export PATH=$HADOOP_HOME/bin:$SPARK_HOME1/bin:$SPARK_HOME2/bin:$PYTHON_HOME:$JAVA_HOME/bin:$HIVE_HOME/bin:$PATH\n</code></pre>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Worker Task 通过 sudo -u 租户 sh xxx.command 会产生子进程，在 kill 的时候，是否会杀掉</h2>",
"a": "\n<p>A： 我们会在 1.0.4 中增加 kill 任务同时，kill 掉任务产生的各种所有子进程</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：DolphinScheduler 中的队列怎么用，用户队列和租户队列是什么意思</h2>",
"a": "\n<p>A ： DolphinScheduler 中的队列可以在用户或者租户上指定队列，<strong>用户指定的队列优先级是高于租户队列的优先级的。</strong>，例如：对 MR 任务指定队列，是通过 mapreduce.job.queuename 来指定队列的。</p>\n<p>注意：MR 在用以上方法指定队列的时候，传递参数请使用如下方式：</p>\n<pre><code>Configuration conf = new Configuration();\n GenericOptionsParser optionParser = new GenericOptionsParser(conf, args);\n String[] remainingArgs = optionParser.getRemainingArgs();\n</code></pre>\n<p>如果是 Spark 任务 --queue 方式指定队列</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Master 或者 Worker 报如下告警</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://analysys.github.io/easyscheduler_docs_cn/images/master_worker_lack_res.png\" width=\"60%\" />\n </p>\n<p>A ： 修改 conf 下的 master.properties <strong>master.reserved.memory</strong> 的值为更小的值，比如说 0.1 或者</p>\n<p>worker.properties <strong>worker.reserved.memory</strong> 的值为更小的值，比如说 0.1</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：hive 版本是 1.1.0+cdh5.15.0，SQL hive 任务连接报错</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://analysys.github.io/easyscheduler_docs_cn/images/cdh_hive_error.png\" width=\"60%\" />\n </p>\n<p>A： 将 hive pom</p>\n<pre><code><dependency>\n <groupId>org.apache.hive</groupId>\n <artifactId>hive-jdbc</artifactId>\n <version>2.3.9</version>\n</dependency>\n</code></pre>\n<p>修改为</p>\n<pre><code><dependency>\n <groupId>org.apache.hive</groupId>\n <arti [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：如何增加一台工作服务器</h2>",
"a": "\n<p>A： 1，参考官网<a href=\"https://dolphinscheduler.apache.org/zh-cn/docs/laster/user_doc/installation/cluster.html\">部署文档</a> 1.3 小节，创建部署用户和 hosts 映射</p>\n<p>\t2，参考官网<a href=\"https://dolphinscheduler.apache.org/zh-cn/docs/laster/user_doc/installation/cluster.html\">部署文档</a> 1.4 小节，配置 hosts 映射和 ssh 打通及修改目录权限.\n 1.4 小节的最后一步是在当前新增机器上执行的，即需要给部署目录部署用户的权限</p>\n<p>\t3，复制正在运行的服务器上的部署目录到新机器的同样的部署目录下</p>\n<p>\t4，到 bin 下，启动 worker server</p>\n<pre><code>./dolphinscheduler-daem [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：DolphinScheduler 什么时候发布新版本，同时新旧版本区别，以及如何升级，版本号规范</h2>",
"a": "\n<p>A：1，Apache 项目的发版流程是通过邮件列表完成的。 你可以订阅 DolphinScheduler 的邮件列表，订阅之后如果有发版，你就可以收到邮件。请参照这篇<a href=\"https://github.com/apache/dolphinscheduler#get-help\">指引</a>来订阅 DolphinScheduler 的邮件列表。</p>\n<p>2，当项目发版的时候，会有发版说明告知具体的变更内容，同时也会有从旧版本升级到新版本的升级文档。</p>\n<p>3，版本号为 x.y.z, 当 x 增加时代表全新架构的版本。当 y 增加时代表与 y 版本之前的不兼容需要升级脚本或其他人工处理才能升级。当 z 增加代表是 bug 修复，升级完全兼容。无需额外处理。之前有个问题 1.0.2 的升级不兼容 1.0.1 需要升级脚本。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：后续任务在前置任务失败情况下仍旧可以执行</h2>",
"a": "\n<p>A：在启动工作流的时候，你可以设置失败策略：继续还是失败。\n<img src=\"https://user-images.githubusercontent.com/15833811/80368215-ee378080-88be-11ea-9074-01a33d012b23.png\" alt=\"设置任务失败策略\"></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：工作流模板 DAG、工作流实例、工作任务及实例之间是什么关系 工作流模板 DAG、工作流实例、工作任务及实例之间是什么关系，一个 dag 支持最大并发 100，是指产生 100 个工作流实例并发运行吗？一个 dag 中的任务节点，也有并发数的配置，是指任务也可以并发多个线程运行吗？最大数 100 吗？</h2>",
"a": "\n<p>A：</p>\n<p>1.2.1 version</p>\n<pre><code> master.properties\n 设置 master 节点并发执行的最大工作流数\n master.exec.threads=100\n\n Control the number of parallel tasks in each workflow\n 设置每个工作流可以并发执行的最大任务数\n master.exec.task.number=20\n\n worker.properties\n 设置 worker 节点并发执行的最大任务数\n worker.exec.threads=100\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：工作组管理页面没有展示按钮</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/39816903/81903776-d8cb9180-95f4-11ea-98cb-94ca1e6a1db5.png\" width=\"60%\" />\n</p>\nA：1.3.0 版本，为了支持 k8s，worker ip 一直变动，因此我们不能在 UI 界面上配置，工作组可以配置在 worker.properties 上配置名称。\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：为什么不把 mysql 的 jdbc 连接包添加到 docker 镜像里面</h2>",
"a": "\n<p>A：Mysql jdbc 连接包的许可证和 apache v2 的许可证不兼容，因此它不能被加入到 docker 镜像里面。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：当一个任务提交多个 yarn 程序的时候经常失败</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/16174111/81312485-476e9380-90b9-11ea-9aad-ed009db899b1.png\" width=\"60%\" />\n</p>\nA：这个 Bug 在 dev 分支已修复，并加入到需求/待做列表。\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Master 服务和 Worker 服务在运行几天之后停止了</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/18378986/81293969-c3101680-90a0-11ea-87e5-ac9f0dd53f5e.png\" width=\"60%\" />\n</p>\nA：会话超时时间太短了，只有 0.3 秒，修改 zookeeper.properties 的配置项：\n<pre><code>zookeeper.session.timeout=60000\nzookeeper.connection.timeout=30000\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：使用 docker-compose 默认配置启动，显示 zookeeper 错误</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/42579056/80374318-13c98780-88c9-11ea-8d5f-53448b957f02.png\" width=\"60%\" />\n </p>\nA：这个问题在 dev-1.3.0 版本解决了。这个 [pr](https://github.com/apache/dolphinscheduler/pull/2595) 已经解决了这个 bug，主要的改动点：\n<pre><code>在docker-compose.yml文件中增加zookeeper的环境变量ZOO_4LW_COMMANDS_WHITELIST。\n把minLatency,avgLatency and maxLatency的类型从int改成float。\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：界面上显示任务一直运行，结束不了，从日志上看任务实例为空</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/51871547/80302626-b1478d00-87dd-11ea-97d4-08aa2244a6d0.jpg\" width=\"60%\" />\n </p>\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/51871547/80302626-b1478d00-87dd-11ea-97d4-08aa2244a6d0.jpg\" width=\"60%\" />\n </p>\nA：这个 [bug](https://github.com/apache/dolphinscheduler/issues/1477) 描述了问题的详情。这个问题在 1.2.1 版本已经被修复了。\n对于 1.2.1 以下的版本，这种情况的一些提示：\n<pre><code>1，清空 zk 下这个路径的 [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：zk 中注册的 master 信息 ip 地址是 127.0.0.1，而不是配置的域名所对应或者解析的 ip 地址，可能导致不能查看任务日志</h2>",
"a": "\n<p>A：修复 bug：</p>\n<pre><code>1、confirm hostname\n$hostname\nhadoop1\n2、hostname -i\n127.0.0.1 10.3.57.15\n3、edit /etc/hosts,delete hadoop1 from 127.0.0.1 record\n$cat /etc/hosts\n127.0.0.1 localhost\n10.3.57.15 ds1 hadoop1\n4、hostname -i\n10.3.57.15\n</code></pre>\n<p>hostname 命令返回服务器主机名，hostname -i 返回的是服务器主机名在 /etc/hosts 中所有匹配的ip地址。所以我把 /etc/hosts 中 127.0.0.1 中的主机名删掉，只保留内网 ip 的解析就可以了，没必要把 127.0.0.1 整条注释掉, 只要 hostname 命令返回值在 /etc/hosts 中对应的内网 ip 正确就可以，ds 程序取了第一个值，我理解上 ds 程序不应 [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：调度系统设置了一个秒级的任务，导致系统挂掉</h2>",
"a": "\n<p>A：调度系统不支持秒级任务。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：编译前后端代码 (dolphinscheduler-ui) 报错不能下载"https://github.com/sass/node-sass/releases/download/v4.13.1/darwin-x64-72_binding.node"</h2>",
"a": "\n<p>A：1，cd dolphinscheduler-ui 然后删除 node_modules 目录</p>\n<pre><code>sudo rm -rf node_modules\n</code></pre>\n<p>\t2，通过 npm.taobao.org 下载 node-sass</p>\n<pre><code>sudo npm uninstall node-sass\nsudo npm i node-sass --sass_binary_site=https://npm.taobao.org/mirrors/node-sass/\n</code></pre>\n<p>3，如果步骤 2 报错，请重新构建 node-saas <a href=\"https://dolphinscheduler.apache.org/en-us/development/frontend-development.html\">参考链接</a></p>\n<pre><code>sudo npm rebuild node-sass\n</code></pre> [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：当使用 mysql 作为 ds 数据库需要如何配置</h2>",
"a": "\n<p>A：1，修改项目根目录 maven 配置文件，移除 scope 的 test 属性，这样 mysql 的包就可以在其它阶段被加载</p>\n<pre><code><dependency>\n\t<groupId>mysql</groupId>\n\t<artifactId>mysql-connector-java</artifactId>\n\t<version>${mysql.connector.version}</version>\n\t<scope>test<scope>\n</dependency>\n</code></pre>\n<p>\t2，修改 application-dao.properties 和 quzrtz.properties 来使用 mysql 驱动\n默认驱动是 postgres 主要由于许可证原因。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：shell 任务是如何运行的</h2>",
"a": "\n<p>A：1，被执行的服务器在哪里配置，以及实际执行的服务器是哪台? 要指定在某个 worker 上去执行，可以在 worker 分组中配置，固定 IP，这样就可以把路径写死。如果配置的 worker 分组有多个 worker，实际执行的服务器由调度决定的，具有随机性。</p>\n<p>\t2，如果是服务器上某个路径的一个 shell 文件，怎么指向这个路径？服务器上某个路径下的 shell 文件，涉及到权限问题，不建议这么做。建议你可以使用资源中心的存储功能，然后在 shell 编辑器里面使用资源引用就可以，系统会帮助你把脚本下载到执行目录下。如果以 hdfs 作为资源中心，在执行的时候，调度器会把依赖的 jar 包，文件等资源拉到 worker 的执行目录上，我这边是 /tmp/escheduler/exec/process，该配置可以在 install.sh 中进行指定。</p>\n<p>3，以哪个用户来执行任务？执行任务的时候�
��调度器会采用 sudo -u 租户的方式去执行，租户是一个 linux 用户。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：生产环境部署方式有推荐的最佳实践吗</h2>",
"a": "\n<p>A：1，如果没有很多任务要运行，出于稳定性考虑我们建议使用 3 个节点，并且最好把 Master/Worder 服务部署在不同的节点。如果你只有一个节点，当然只能把所有的服务部署在同一个节点！通常来说，需要多少节点取决于你的业务，海豚调度系统本身不需要很多的资源。充分测试之后，你们将找到使用较少节点的合适的部署方式。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：DEPENDENT 节点</h2>",
"a": "\n<p>A：1，DEPENDENT 节点实际是没有执行体的，是专门用来配置数据周期依赖逻辑，然后再把执行节点挂载后面，来实现任务间的周期依赖。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：如何改变 Master 服务的启动端口</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/8263441/62352160-0f3e9100-b53a-11e9-95ba-3ae3dde49c72.png\" width=\"60%\" />\n </p>\nA：1，修改 application_master.properties 配置文件，例如：server.port=12345。\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：调度任务不能上线</h2>",
"a": "\n<p>A：1，我们可以成功创建调度任务，并且表 t_scheduler_schedules 中也成功加入了一条记录，但当我点击上线后，前端页面无反应且会把 t_scheduler_schedules 这张表锁定，我测试过将 t_scheduler_schedules 中的 RELEASE_state 字段手动更新为 1 这样前端会显示为上线状态。DS 版本 1.2+ 表名是 t_ds_schedules，其它版本表名是 t_scheduler_schedules。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：请问 swagger ui 的地址是什么</h2>",
"a": "\n<p>A：1， 3.1.0+ 版本地址是 http://apiServerIp:apiServerPort/dolphinscheduler/swagger-ui/index.html, 1.2+ 版本地址是：http://apiServerIp:apiServerPort/dolphinscheduler/swagger-ui/index.html?language=zh_CN&lang=cn，其它版本是 http://apiServerIp:apiServerPort/escheduler/swagger-ui/index.html?language=zh_CN&lang=cn。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：前端安装包缺少文件</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/41460919/61437083-d960b080-a96e-11e9-87f1-297ba3aca5e3.png\" width=\"60%\" />\n </p>\n <p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/41460919/61437218-1b89f200-a96f-11e9-8e48-3fac47eb2389.png\" width=\"60%\" />\n </p>\nA： 1，用户修改了 api server 配置文件中的![apiServerContextPath](https://user-images.githubusercontent.com/41460919/61678323-1b09a680-ad35-11e9-9707-3ba68bbc70d6. [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：上传比较大的文件卡住</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/21357069/58231400-805b0e80-7d69-11e9-8107-7f37b06a95df.png\" width=\"60%\" />\n </p>\nA：1，编辑 ngnix 配置文件 vi /etc/nginx/nginx.conf，更改上传大小 client_max_body_size 1024m。\n<p>\t2，更新 google chrome 版本到最新版本。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：创建 spark 数据源，点击“测试连接”，系统回退回到登入页面</h2>",
"a": "\n<p>A：1，edit /etc/nginx/conf.d/escheduler.conf</p>\n<pre><code>proxy_connect_timeout 300s;\nproxy_read_timeout 300s;\nproxy_send_timeout 300s;\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：工作流依赖</h2>",
"a": "\n<p>A：1，目前是按照自然天来判断，上月末：判断时间是工作流 A start_time/scheduler_time between '2019-05-31 00:00:00' and '2019-05-31 23:59:59'。上月：是判断上个月从 1 号到月末每天都要有完成的A实例。上周： 上周 7 天都要有完成的 A 实例。前两天： 判断昨天和前天，两天都要有完成的 A 实例。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：DS 后端接口文档</h2>",
"a": "\n<p>A：1，http://106.75.43.194:8888/dolphinscheduler/swagger-ui/index.html?language=zh_CN&lang=zh。</p>\n<h2>dolphinscheduler 在运行过程中，ip 地址获取错误的问题</h2>\n<p>master 服务、worker 服务在 zookeeper 注册时，会以 ip:port 的形式创建相关信息</p>\n<p>如果 ip 地址获取错误，请检查网络信息，如 Linux 系统通过 <code>ifconfig</code> 命令查看网络信息，以下图为例：</p>\n<p align=\"center\">\n <img src=\"/img/network/network_config.png\" width=\"60%\" />\n</p>\n<p>可以使用 dolphinscheduler 提供的三种策略，获取可用 ip：</p>\n<ul>\n<li>default: 优先获取内网网卡获取 ip 地址，其次获取外网网卡 [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Yarn多集群支持</h2>",
"a": "\n<p>A：将Worker节点分别部署至多个Yarn集群，步骤如下（例如AWS EMR）：</p>\n<ol>\n<li>\n<p>将 Worker 节点部署至 EMR 集群的 Master 节点</p>\n</li>\n<li>\n<p>将 <code>conf/common.properties</code> 中的 <code>yarn.application.status.address</code> 修改为当前集群的 Yarn 的信息</p>\n</li>\n<li>\n<p>通过 <code>bin/dolphinscheduler-daemon.sh start worker-server</code> 启动 worker-server</p>\n</li>\n</ol>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：Update process definition error: Duplicate key TaskDefinition</h2>",
"a": "\n<p>A：在DS 2.0.4之前（2.0.0-alpha之后），可能存在版本切换的重复键问题，导致更新工作流失败；可参考如下SQL进行重复数据的删除，以MySQL为例：（注意：操作前请务必备份原数据，SQL来源于pr <a href=\"https://github.com/apache/dolphinscheduler/pull/8408\">#8408</a>）</p>\n<pre><code class=\"language-SQL\"><span class=\"hljs-keyword\">DELETE</span> <span class=\"hljs-keyword\">FROM</span> t_ds_process_task_relation_log <span class=\"hljs-keyword\">WHERE</span> id <span class=\"hljs-keyword\">IN</span>\n(\n <span class=\"hljs-keyword\">SELECT</span>\n x.i [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：使用Postgresql数据库从2.0.1升级至2.0.5更新失败</h2>",
"a": "\n<p>A：在数据库中执行以下SQL即可完成修复:</p>\n<pre><code class=\"language-SQL\"><span class=\"hljs-keyword\">update</span> t_ds_version <span class=\"hljs-keyword\">set</span> version<span class=\"hljs-operator\">=</span><span class=\"hljs-string\">'2.0.1'</span>;\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
+ "time": "2023-05-15",
+ "version": "3.1.6",
"q": "<h2>Q：在二进制分发包中找不到 python-gateway-server 文件夹</h2>",
"a": "\n<p>A：在 3.0.0-alpha 版本之后，Python gateway server 集成到 api server 中，当您启动 api server 后，Python gateway server 将启动。\n如果您不想在 api server 启动的时候启动 Python gateway server，您可以修改 api server 中的配置文件 <code>api-server/conf/application.yaml</code>\n并更改可选项 <code>python-gateway.enabled</code> 中的值设置为 <code>false</code>。</p>\n<hr>\n<p>我们会持续收集更多的 FAQ。</p>\n"
}
diff --git a/fetch/deployment.json b/fetch/deployment.json
index ac0b81fed9..7c11968ea6 100644
--- a/fetch/deployment.json
+++ b/fetch/deployment.json
@@ -19,7 +19,8 @@
"3.1.2",
"3.1.3",
"3.1.4",
- "3.1.5"
+ "3.1.5",
+ "3.1.6"
],
"Pseudo Cluster": [
"2.0.0",
@@ -41,7 +42,8 @@
"3.1.2",
"3.1.3",
"3.1.4",
- "3.1.5"
+ "3.1.5",
+ "3.1.6"
],
"Cluster": [
"2.0.0",
@@ -63,7 +65,8 @@
"3.1.2",
"3.1.3",
"3.1.4",
- "3.1.5"
+ "3.1.5",
+ "3.1.6"
],
"Kubernetes": [
"2.0.0",
@@ -85,7 +88,8 @@
"3.1.2",
"3.1.3",
"3.1.4",
- "3.1.5"
+ "3.1.5",
+ "3.1.6"
],
"Cloud": []
}
\ No newline at end of file
diff --git a/fetch/doc/en-us/3.1.6.json b/fetch/doc/en-us/3.1.6.json
new file mode 100644
index 0000000000..ba51a3fda0
--- /dev/null
+++ b/fetch/doc/en-us/3.1.6.json
@@ -0,0 +1,1127 @@
+[
+ {
+ "title": "About",
+ "children": [
+ {
+ "title": "Introduction",
+ "children": [],
+ "location": [
+ "About",
+ "Introduction"
+ ],
+ "key": "/about/introduction"
+ },
+ {
+ "title": "Features",
+ "children": [],
+ "location": [
+ "About",
+ "Features"
+ ],
+ "key": "/about/features"
+ },
+ {
+ "title": "Hardware Environment",
+ "children": [],
+ "location": [
+ "About",
+ "Hardware Environment"
+ ],
+ "key": "/about/hardware"
+ },
+ {
+ "title": "Glossary",
+ "children": [],
+ "location": [
+ "About",
+ "Glossary"
+ ],
+ "key": "/about/glossary"
+ }
+ ],
+ "location": [
+ "About"
+ ],
+ "key": "/about_menu"
+ },
+ {
+ "title": "Quick Start",
+ "children": [
+ {
+ "title": "Quick Start",
+ "children": [],
+ "location": [
+ "Quick Start",
+ "Quick Start"
+ ],
+ "key": "/guide/start/quick-start"
+ },
+ {
+ "title": "Docker Deployment",
+ "children": [],
+ "location": [
+ "Quick Start",
+ "Docker Deployment"
+ ],
+ "key": "/guide/start/docker"
+ }
+ ],
+ "location": [
+ "Quick Start"
+ ],
+ "key": "/quick-start_menu"
+ },
+ {
+ "title": "Introduction to Functions",
+ "children": [
+ {
+ "title": "Application Homepage",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Application Homepage"
+ ],
+ "key": "/guide/homepage"
+ },
+ {
+ "title": "Project",
+ "children": [
+ {
+ "title": "Project List",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Project",
+ "Project List"
+ ],
+ "key": "/guide/project/project-list"
+ },
+ {
+ "title": "Workflow Definition",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Project",
+ "Workflow Definition"
+ ],
+ "key": "/guide/project/workflow-definition"
+ },
+ {
+ "title": "Workflow Instance",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Project",
+ "Workflow Instance"
+ ],
+ "key": "/guide/project/workflow-instance"
+ },
+ {
+ "title": "Task Instance",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Project",
+ "Task Instance"
+ ],
+ "key": "/guide/project/task-instance"
+ },
+ {
+ "title": "Task Definition",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Project",
+ "Task Definition"
+ ],
+ "key": "/guide/project/task-definition"
+ }
+ ],
+ "location": [
+ "Introduction to Functions",
+ "Project"
+ ],
+ "key": "/introduction-to-functions_menu/project_menu"
+ },
+ {
+ "title": "Task",
+ "children": [
+ {
+ "title": "Appendix",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Appendix"
+ ],
+ "key": "/guide/task/appendix"
+ },
+ {
+ "title": "Shell",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Shell"
+ ],
+ "key": "/guide/task/shell"
+ },
+ {
+ "title": "SubProcess",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "SubProcess"
+ ],
+ "key": "/guide/task/sub-process"
+ },
+ {
+ "title": "Dependent",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Dependent"
+ ],
+ "key": "/guide/task/dependent"
+ },
+ {
+ "title": "Stored Procedure",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Stored Procedure"
+ ],
+ "key": "/guide/task/stored-procedure"
+ },
+ {
+ "title": "SQL",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "SQL"
+ ],
+ "key": "/guide/task/sql"
+ },
+ {
+ "title": "Spark",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Spark"
+ ],
+ "key": "/guide/task/spark"
+ },
+ {
+ "title": "MapReduce",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "MapReduce"
+ ],
+ "key": "/guide/task/map-reduce"
+ },
+ {
+ "title": "Python",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Python"
+ ],
+ "key": "/guide/task/python"
+ },
+ {
+ "title": "Flink",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Flink"
+ ],
+ "key": "/guide/task/flink"
+ },
+ {
+ "title": "HTTP",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "HTTP"
+ ],
+ "key": "/guide/task/http"
+ },
+ {
+ "title": "DataX",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "DataX"
+ ],
+ "key": "/guide/task/datax"
+ },
+ {
+ "title": "Pigeon",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Pigeon"
+ ],
+ "key": "/guide/task/pigeon"
+ },
+ {
+ "title": "Conditions",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Conditions"
+ ],
+ "key": "/guide/task/conditions"
+ },
+ {
+ "title": "Switch",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Switch"
+ ],
+ "key": "/guide/task/switch"
+ },
+ {
+ "title": "SeaTunnel",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "SeaTunnel"
+ ],
+ "key": "/guide/task/seatunnel"
+ },
+ {
+ "title": "Amazon EMR",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Amazon EMR"
+ ],
+ "key": "/guide/task/emr"
+ },
+ {
+ "title": "Apache Zeppelin",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Apache Zeppelin"
+ ],
+ "key": "/guide/task/zeppelin"
+ },
+ {
+ "title": "Jupyter",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Jupyter"
+ ],
+ "key": "/guide/task/jupyter"
+ },
+ {
+ "title": "Hive CLI",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Hive CLI"
+ ],
+ "key": "/guide/task/hive-cli"
+ },
+ {
+ "title": "Kubernetes",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Kubernetes"
+ ],
+ "key": "/guide/task/kubernetes"
+ },
+ {
+ "title": "MLflow",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "MLflow"
+ ],
+ "key": "/guide/task/mlflow"
+ },
+ {
+ "title": "Openmldb",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Openmldb"
+ ],
+ "key": "/guide/task/openmldb"
+ },
+ {
+ "title": "DVC",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "DVC"
+ ],
+ "key": "/guide/task/dvc"
+ },
+ {
+ "title": "Dinky",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Dinky"
+ ],
+ "key": "/guide/task/dinky"
+ },
+ {
+ "title": "SageMaker",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "SageMaker"
+ ],
+ "key": "/guide/task/sagemaker"
+ },
+ {
+ "title": "ChunJun",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "ChunJun"
+ ],
+ "key": "/guide/task/chunjun"
+ },
+ {
+ "title": "Pytorch",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "Pytorch"
+ ],
+ "key": "/guide/task/pytorch"
+ }
+ ],
+ "location": [
+ "Introduction to Functions",
+ "Task"
+ ],
+ "key": "/introduction-to-functions_menu/task_menu"
+ },
+ {
+ "title": "Parameter",
+ "children": [
+ {
+ "title": "Built-in Parameter",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Parameter",
+ "Built-in Parameter"
+ ],
+ "key": "/guide/parameter/built-in"
+ },
+ {
+ "title": "Global Parameter",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Parameter",
+ "Global Parameter"
+ ],
+ "key": "/guide/parameter/global"
+ },
+ {
+ "title": "Local Parameter",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Parameter",
+ "Local Parameter"
+ ],
+ "key": "/guide/parameter/local"
+ },
+ {
+ "title": "Parameter Context",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Parameter",
+ "Parameter Context"
+ ],
+ "key": "/guide/parameter/context"
+ },
+ {
+ "title": "Parameter Priority",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Parameter",
+ "Parameter Priority"
+ ],
+ "key": "/guide/parameter/priority"
+ }
+ ],
+ "location": [
+ "Introduction to Functions",
+ "Parameter"
+ ],
+ "key": "/introduction-to-functions_menu/parameter_menu"
+ },
+ {
+ "title": "Data Source",
+ "children": [
+ {
+ "title": "MySQL",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "MySQL"
+ ],
+ "key": "/guide/datasource/mysql"
+ },
+ {
+ "title": "PostgreSQL",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "PostgreSQL"
+ ],
+ "key": "/guide/datasource/postgresql"
+ },
+ {
+ "title": "HIVE",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "HIVE"
+ ],
+ "key": "/guide/datasource/hive"
+ },
+ {
+ "title": "Spark",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "Spark"
+ ],
+ "key": "/guide/datasource/spark"
+ },
+ {
+ "title": "Presto",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "Presto"
+ ],
+ "key": "/guide/datasource/presto"
+ },
+ {
+ "title": "SQL SERVER",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "SQL SERVER"
+ ],
+ "key": "/guide/datasource/sqlserver"
+ },
+ {
+ "title": "Amazon Redshift",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "Amazon Redshift"
+ ],
+ "key": "/guide/datasource/redshift"
+ },
+ {
+ "title": "ClickHouse",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "ClickHouse"
+ ],
+ "key": "/guide/datasource/clickhouse"
+ },
+ {
+ "title": "IBM DB2",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "IBM DB2"
+ ],
+ "key": "/guide/datasource/db2"
+ },
+ {
+ "title": "Oracle",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "Oracle"
+ ],
+ "key": "/guide/datasource/oracle"
+ },
+ {
+ "title": "Amazon Athena",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Source",
+ "Amazon Athena"
+ ],
+ "key": "/guide/datasource/athena"
+ }
+ ],
+ "location": [
+ "Introduction to Functions",
+ "Data Source"
+ ],
+ "key": "/introduction-to-functions_menu/data-source_menu"
+ },
+ {
+ "title": "Alert",
+ "children": [
+ {
+ "title": "Alert Component User Guide ",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Alert",
+ "Alert Component User Guide "
+ ],
+ "key": "/guide/alert/alert_plugin_user_guide"
+ },
+ {
+ "title": "Email",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Alert",
+ "Email"
+ ],
+ "key": "/guide/alert/email"
+ },
+ {
+ "title": "Telegram",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Alert",
+ "Telegram"
+ ],
+ "key": "/guide/alert/telegram"
+ },
+ {
+ "title": "Ding Talk",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Alert",
+ "Ding Talk"
+ ],
+ "key": "/guide/alert/dingtalk"
+ },
+ {
+ "title": "Enterprise Wechat",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Alert",
+ "Enterprise Wechat"
+ ],
+ "key": "/guide/alert/enterprise-wechat"
+ },
+ {
+ "title": "Enterprise Webexteams",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Alert",
+ "Enterprise Webexteams"
+ ],
+ "key": "/guide/alert/enterprise-webexteams"
+ },
+ {
+ "title": "Script",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Alert",
+ "Script"
+ ],
+ "key": "/guide/alert/script"
+ },
+ {
+ "title": "Http",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Alert",
+ "Http"
+ ],
+ "key": "/guide/alert/http"
+ },
+ {
+ "title": "Feishu",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Alert",
+ "Feishu"
+ ],
+ "key": "/guide/alert/feishu"
+ }
+ ],
+ "location": [
+ "Introduction to Functions",
+ "Alert"
+ ],
+ "key": "/introduction-to-functions_menu/alert_menu"
+ },
+ {
+ "title": "Resource",
+ "children": [
+ {
+ "title": "Introduction",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Resource",
+ "Introduction"
+ ],
+ "key": "/guide/resource/intro"
+ },
+ {
+ "title": "Configuration",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Resource",
+ "Configuration"
+ ],
+ "key": "/guide/resource/configuration"
+ },
+ {
+ "title": "File Manage",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Resource",
+ "File Manage"
+ ],
+ "key": "/guide/resource/file-manage"
+ },
+ {
+ "title": "UDF Manage",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Resource",
+ "UDF Manage"
+ ],
+ "key": "/guide/resource/udf-manage"
+ },
+ {
+ "title": "Task Group Manage",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Resource",
+ "Task Group Manage"
+ ],
+ "key": "/guide/resource/task-group"
+ }
+ ],
+ "location": [
+ "Introduction to Functions",
+ "Resource"
+ ],
+ "key": "/introduction-to-functions_menu/resource_menu"
+ },
+ {
+ "title": "Monitor",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Monitor"
+ ],
+ "key": "/guide/monitor"
+ },
+ {
+ "title": "Security",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Security"
+ ],
+ "key": "/guide/security"
+ },
+ {
+ "title": "Metrics",
+ "children": [
+ {
+ "title": "Metrics",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Metrics",
+ "Metrics"
+ ],
+ "key": "/guide/metrics/metrics"
+ }
+ ],
+ "location": [
+ "Introduction to Functions",
+ "Metrics"
+ ],
+ "key": "/introduction-to-functions_menu/metrics_menu"
+ },
+ {
+ "title": "Data Quality",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Data Quality"
+ ],
+ "key": "/guide/data-quality"
+ },
+ {
+ "title": "Upgrade",
+ "children": [
+ {
+ "title": "Incompatible",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Upgrade",
+ "Incompatible"
+ ],
+ "key": "/guide/upgrade/incompatible"
+ },
+ {
+ "title": "Upgrade",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Upgrade",
+ "Upgrade"
+ ],
+ "key": "/guide/upgrade/upgrade"
+ }
+ ],
+ "location": [
+ "Introduction to Functions",
+ "Upgrade"
+ ],
+ "key": "/introduction-to-functions_menu/upgrade_menu"
+ },
+ {
+ "title": "Expansion and Reduction",
+ "children": [],
+ "location": [
+ "Introduction to Functions",
+ "Expansion and Reduction"
+ ],
+ "key": "/guide/expansion-reduction"
+ }
+ ],
+ "location": [
+ "Introduction to Functions"
+ ],
+ "key": "/introduction-to-functions_menu"
+ },
+ {
+ "title": "Installation",
+ "children": [
+ {
+ "title": "Standalone Deployment",
+ "children": [],
+ "location": [
+ "Installation",
+ "Standalone Deployment"
+ ],
+ "key": "/guide/installation/standalone"
+ },
+ {
+ "title": "Pseudo Cluster Deployment",
+ "children": [],
+ "location": [
+ "Installation",
+ "Pseudo Cluster Deployment"
+ ],
+ "key": "/guide/installation/pseudo-cluster"
+ },
+ {
+ "title": "Cluster Deployment",
+ "children": [],
+ "location": [
+ "Installation",
+ "Cluster Deployment"
+ ],
+ "key": "/guide/installation/cluster"
+ },
+ {
+ "title": "Kubernetes Deployment",
+ "children": [],
+ "location": [
+ "Installation",
+ "Kubernetes Deployment"
+ ],
+ "key": "/guide/installation/kubernetes"
+ },
+ {
+ "title": "integration",
+ "children": [
+ {
+ "title": "Rainbond Deployment",
+ "children": [],
+ "location": [
+ "Installation",
+ "integration",
+ "Rainbond Deployment"
+ ],
+ "key": "/guide/integration/rainbond"
+ }
+ ],
+ "location": [
+ "Installation",
+ "integration"
+ ],
+ "key": "/installation_menu/integration_menu"
+ }
+ ],
+ "location": [
+ "Installation"
+ ],
+ "key": "/installation_menu"
+ },
+ {
+ "title": "Architecture Guide",
+ "children": [
+ {
+ "title": "Architecture Design",
+ "children": [],
+ "location": [
+ "Architecture Guide",
+ "Architecture Design"
+ ],
+ "key": "/architecture/design"
+ },
+ {
+ "title": "Metadata",
+ "children": [],
+ "location": [
+ "Architecture Guide",
+ "Metadata"
+ ],
+ "key": "/architecture/metadata"
+ },
+ {
+ "title": "Configuration File",
+ "children": [],
+ "location": [
+ "Architecture Guide",
+ "Configuration File"
+ ],
+ "key": "/architecture/configuration"
+ },
+ {
+ "title": "Task Structure",
+ "children": [],
+ "location": [
+ "Architecture Guide",
+ "Task Structure"
+ ],
+ "key": "/architecture/task-structure"
+ },
+ {
+ "title": "Load Balance",
+ "children": [],
+ "location": [
+ "Architecture Guide",
+ "Load Balance"
+ ],
+ "key": "/architecture/load-balance"
+ },
+ {
+ "title": "Cache",
+ "children": [],
+ "location": [
+ "Architecture Guide",
+ "Cache"
+ ],
+ "key": "/architecture/cache"
+ }
+ ],
+ "location": [
+ "Architecture Guide"
+ ],
+ "key": "/architecture-guide_menu"
+ },
+ {
+ "title": "API",
+ "children": [
+ {
+ "title": "Open API",
+ "children": [],
+ "location": [
+ "API",
+ "Open API"
+ ],
+ "key": "/guide/api/open-api"
+ },
+ {
+ "title": "PyDolphinScheduler",
+ "children": [],
+ "location": [
+ "API",
+ "PyDolphinScheduler"
+ ],
+ "key": "/guide/api/pydolphinscheduler"
+ },
+ {
+ "title": "Health Check",
+ "children": [],
+ "location": [
+ "API",
+ "Health Check"
+ ],
+ "key": "/guide/api/healthcheck"
+ }
+ ],
+ "location": [
+ "API"
+ ],
+ "key": "/api_menu"
+ },
+ {
+ "title": "Contribution",
+ "children": [
+ {
+ "title": "SPI",
+ "children": [
+ {
+ "title": "Alert SPI",
+ "children": [],
+ "location": [
+ "Contribution",
+ "SPI",
+ "Alert SPI"
+ ],
+ "key": "/contribute/backend/spi/alert"
+ },
+ {
+ "title": "Datasource SPI",
+ "children": [],
+ "location": [
+ "Contribution",
+ "SPI",
+ "Datasource SPI"
+ ],
+ "key": "/contribute/backend/spi/datasource"
+ },
+ {
+ "title": "Registry SPI",
+ "children": [],
+ "location": [
+ "Contribution",
+ "SPI",
+ "Registry SPI"
+ ],
+ "key": "/contribute/backend/spi/registry"
+ },
+ {
+ "title": "Task SPI",
+ "children": [],
+ "location": [
+ "Contribution",
+ "SPI",
+ "Task SPI"
+ ],
+ "key": "/contribute/backend/spi/task"
+ }
+ ],
+ "location": [
+ "Contribution",
+ "SPI"
+ ],
+ "key": "/contribution_menu/spi_menu"
+ },
+ {
+ "title": "Development Environment Setup",
+ "children": [],
+ "location": [
+ "Contribution",
+ "Development Environment Setup"
+ ],
+ "key": "/contribute/development-environment-setup"
+ },
+ {
+ "title": "Frontend Development",
+ "children": [],
+ "location": [
+ "Contribution",
+ "Frontend Development"
+ ],
+ "key": "/contribute/frontend-development"
+ }
+ ],
+ "location": [
+ "Contribution"
+ ],
+ "key": "/contribution_menu"
+ },
+ {
+ "title": "DSIP",
+ "children": [
+ {
+ "title": "DSIP",
+ "children": [],
+ "location": [
+ "DSIP",
+ "DSIP"
+ ],
+ "key": "/DSIP"
+ }
+ ],
+ "location": [
+ "DSIP"
+ ],
+ "key": "/dsip_menu"
+ }
+]
\ No newline at end of file
diff --git a/fetch/doc/zh-cn/3.1.6.json b/fetch/doc/zh-cn/3.1.6.json
new file mode 100644
index 0000000000..23a2b5f74b
--- /dev/null
+++ b/fetch/doc/zh-cn/3.1.6.json
@@ -0,0 +1,1067 @@
+[
+ {
+ "title": "关于Apache DolphinScheduler",
+ "children": [
+ {
+ "title": "简介",
+ "children": [],
+ "location": [
+ "关于Apache DolphinScheduler",
+ "简介"
+ ],
+ "key": "/about/introduction"
+ },
+ {
+ "title": "特性",
+ "children": [],
+ "location": [
+ "关于Apache DolphinScheduler",
+ "特性"
+ ],
+ "key": "/about/features"
+ },
+ {
+ "title": "建议配置",
+ "children": [],
+ "location": [
+ "关于Apache DolphinScheduler",
+ "建议配置"
+ ],
+ "key": "/about/hardware"
+ },
+ {
+ "title": "名词解释",
+ "children": [],
+ "location": [
+ "关于Apache DolphinScheduler",
+ "名词解释"
+ ],
+ "key": "/about/glossary"
+ }
+ ],
+ "location": [
+ "关于Apache DolphinScheduler"
+ ],
+ "key": "/关于apache-dolphinscheduler_menu"
+ },
+ {
+ "title": "快速上手",
+ "children": [
+ {
+ "title": "快速上手",
+ "children": [],
+ "location": [
+ "快速上手",
+ "快速上手"
+ ],
+ "key": "/guide/start/quick-start"
+ },
+ {
+ "title": "Docker部署(Docker)",
+ "children": [],
+ "location": [
+ "快速上手",
+ "Docker部署(Docker)"
+ ],
+ "key": "/guide/start/docker"
+ }
+ ],
+ "location": [
+ "快速上手"
+ ],
+ "key": "/快速上手_menu"
+ },
+ {
+ "title": "功能介绍",
+ "children": [
+ {
+ "title": "应用首页",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "应用首页"
+ ],
+ "key": "/guide/homepage"
+ },
+ {
+ "title": "项目管理",
+ "children": [
+ {
+ "title": "项目列表",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "项目管理",
+ "项目列表"
+ ],
+ "key": "/guide/project/project-list"
+ },
+ {
+ "title": "工作流定义",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "项目管理",
+ "工作流定义"
+ ],
+ "key": "/guide/project/workflow-definition"
+ },
+ {
+ "title": "工作流实例",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "项目管理",
+ "工作流实例"
+ ],
+ "key": "/guide/project/workflow-instance"
+ },
+ {
+ "title": "任务实例",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "项目管理",
+ "任务实例"
+ ],
+ "key": "/guide/project/task-instance"
+ },
+ {
+ "title": "任务定义",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "项目管理",
+ "任务定义"
+ ],
+ "key": "/guide/project/task-definition"
+ }
+ ],
+ "location": [
+ "功能介绍",
+ "项目管理"
+ ],
+ "key": "/功能介绍_menu/项目管理_menu"
+ },
+ {
+ "title": "任务类型",
+ "children": [
+ {
+ "title": "Appendix",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Appendix"
+ ],
+ "key": "/guide/task/appendix"
+ },
+ {
+ "title": "Shell",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Shell"
+ ],
+ "key": "/guide/task/shell"
+ },
+ {
+ "title": "SubProcess",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "SubProcess"
+ ],
+ "key": "/guide/task/sub-process"
+ },
+ {
+ "title": "Dependent",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Dependent"
+ ],
+ "key": "/guide/task/dependent"
+ },
+ {
+ "title": "Stored Procedure",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Stored Procedure"
+ ],
+ "key": "/guide/task/stored-procedure"
+ },
+ {
+ "title": "SQL",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "SQL"
+ ],
+ "key": "/guide/task/sql"
+ },
+ {
+ "title": "Spark",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Spark"
+ ],
+ "key": "/guide/task/spark"
+ },
+ {
+ "title": "MapReduce",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "MapReduce"
+ ],
+ "key": "/guide/task/map-reduce"
+ },
+ {
+ "title": "Python",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Python"
+ ],
+ "key": "/guide/task/python"
+ },
+ {
+ "title": "Flink",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Flink"
+ ],
+ "key": "/guide/task/flink"
+ },
+ {
+ "title": "HTTP",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "HTTP"
+ ],
+ "key": "/guide/task/http"
+ },
+ {
+ "title": "DataX",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "DataX"
+ ],
+ "key": "/guide/task/datax"
+ },
+ {
+ "title": "Pigeon",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Pigeon"
+ ],
+ "key": "/guide/task/pigeon"
+ },
+ {
+ "title": "Conditions",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Conditions"
+ ],
+ "key": "/guide/task/conditions"
+ },
+ {
+ "title": "Switch",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Switch"
+ ],
+ "key": "/guide/task/switch"
+ },
+ {
+ "title": "SeaTunnel",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "SeaTunnel"
+ ],
+ "key": "/guide/task/seatunnel"
+ },
+ {
+ "title": "Amazon EMR",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Amazon EMR"
+ ],
+ "key": "/guide/task/emr"
+ },
+ {
+ "title": "Apache Zeppelin",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Apache Zeppelin"
+ ],
+ "key": "/guide/task/zeppelin"
+ },
+ {
+ "title": "Jupyter",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Jupyter"
+ ],
+ "key": "/guide/task/jupyter"
+ },
+ {
+ "title": "Hive CLI",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Hive CLI"
+ ],
+ "key": "/guide/task/hive-cli"
+ },
+ {
+ "title": "Kubernetes",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Kubernetes"
+ ],
+ "key": "/guide/task/kubernetes"
+ },
+ {
+ "title": "MLflow",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "MLflow"
+ ],
+ "key": "/guide/task/mlflow"
+ },
+ {
+ "title": "Openmldb",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Openmldb"
+ ],
+ "key": "/guide/task/openmldb"
+ },
+ {
+ "title": "DVC",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "DVC"
+ ],
+ "key": "/guide/task/dvc"
+ },
+ {
+ "title": "Dinky",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Dinky"
+ ],
+ "key": "/guide/task/dinky"
+ },
+ {
+ "title": "SageMaker",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "SageMaker"
+ ],
+ "key": "/guide/task/sagemaker"
+ },
+ {
+ "title": "ChunJun",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "ChunJun"
+ ],
+ "key": "/guide/task/chunjun"
+ },
+ {
+ "title": "Pytorch",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "任务类型",
+ "Pytorch"
+ ],
+ "key": "/guide/task/pytorch"
+ }
+ ],
+ "location": [
+ "功能介绍",
+ "任务类型"
+ ],
+ "key": "/功能介绍_menu/任务类型_menu"
+ },
+ {
+ "title": "参数",
+ "children": [
+ {
+ "title": "内置参数",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "参数",
+ "内置参数"
+ ],
+ "key": "/guide/parameter/built-in"
+ },
+ {
+ "title": "全局参数",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "参数",
+ "全局参数"
+ ],
+ "key": "/guide/parameter/global"
+ },
+ {
+ "title": "本地参数",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "参数",
+ "本地参数"
+ ],
+ "key": "/guide/parameter/local"
+ },
+ {
+ "title": "参数传递",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "参数",
+ "参数传递"
+ ],
+ "key": "/guide/parameter/context"
+ },
+ {
+ "title": "参数优先级",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "参数",
+ "参数优先级"
+ ],
+ "key": "/guide/parameter/priority"
+ }
+ ],
+ "location": [
+ "功能介绍",
+ "参数"
+ ],
+ "key": "/功能介绍_menu/参数_menu"
+ },
+ {
+ "title": "数据源中心",
+ "children": [
+ {
+ "title": "MySQL",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "数据源中心",
+ "MySQL"
+ ],
+ "key": "/guide/datasource/mysql"
+ },
+ {
+ "title": "PostgreSQL",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "数据源中心",
+ "PostgreSQL"
+ ],
+ "key": "/guide/datasource/postgresql"
+ },
+ {
+ "title": "HIVE",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "数据源中心",
+ "HIVE"
+ ],
+ "key": "/guide/datasource/hive"
+ },
+ {
+ "title": "Spark",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "数据源中心",
+ "Spark"
+ ],
+ "key": "/guide/datasource/spark"
+ },
+ {
+ "title": "Amazon Athena",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "数据源中心",
+ "Amazon Athena"
+ ],
+ "key": "/guide/datasource/athena"
+ }
+ ],
+ "location": [
+ "功能介绍",
+ "数据源中心"
+ ],
+ "key": "/功能介绍_menu/数据源中心_menu"
+ },
+ {
+ "title": "告警",
+ "children": [
+ {
+ "title": "告警组件向导",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "告警",
+ "告警组件向导"
+ ],
+ "key": "/guide/alert/alert_plugin_user_guide"
+ },
+ {
+ "title": "Email",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "告警",
+ "Email"
+ ],
+ "key": "/guide/alert/email"
+ },
+ {
+ "title": "Telegram",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "告警",
+ "Telegram"
+ ],
+ "key": "/guide/alert/telegram"
+ },
+ {
+ "title": "钉钉告警",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "告警",
+ "钉钉告警"
+ ],
+ "key": "/guide/alert/dingtalk"
+ },
+ {
+ "title": "企业微信",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "告警",
+ "企业微信"
+ ],
+ "key": "/guide/alert/enterprise-wechat"
+ },
+ {
+ "title": "Webexteams",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "告警",
+ "Webexteams"
+ ],
+ "key": "/guide/alert/enterprise-webexteams"
+ },
+ {
+ "title": "脚本告警",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "告警",
+ "脚本告警"
+ ],
+ "key": "/guide/alert/script"
+ },
+ {
+ "title": "Http告警",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "告警",
+ "Http告警"
+ ],
+ "key": "/guide/alert/http"
+ },
+ {
+ "title": "飞书告警",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "告警",
+ "飞书告警"
+ ],
+ "key": "/guide/alert/feishu"
+ }
+ ],
+ "location": [
+ "功能介绍",
+ "告警"
+ ],
+ "key": "/功能介绍_menu/告警_menu"
+ },
+ {
+ "title": "资源中心",
+ "children": [
+ {
+ "title": "简介",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "资源中心",
+ "简介"
+ ],
+ "key": "/guide/resource/intro"
+ },
+ {
+ "title": "配置详情",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "资源中心",
+ "配置详情"
+ ],
+ "key": "/guide/resource/configuration"
+ },
+ {
+ "title": "文件管理",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "资源中心",
+ "文件管理"
+ ],
+ "key": "/guide/resource/file-manage"
+ },
+ {
+ "title": "UDF 管理",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "资源中心",
+ "UDF 管理"
+ ],
+ "key": "/guide/resource/udf-manage"
+ },
+ {
+ "title": "任务组管理",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "资源中心",
+ "任务组管理"
+ ],
+ "key": "/guide/resource/task-group"
+ }
+ ],
+ "location": [
+ "功能介绍",
+ "资源中心"
+ ],
+ "key": "/功能介绍_menu/资源中心_menu"
+ },
+ {
+ "title": "监控中心",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "监控中心"
+ ],
+ "key": "/guide/monitor"
+ },
+ {
+ "title": "安全中心",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "安全中心"
+ ],
+ "key": "/guide/security"
+ },
+ {
+ "title": "指标相关",
+ "children": [
+ {
+ "title": "指标",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "指标相关",
+ "指标"
+ ],
+ "key": "/guide/metrics/metrics"
+ }
+ ],
+ "location": [
+ "功能介绍",
+ "指标相关"
+ ],
+ "key": "/功能介绍_menu/指标相关_menu"
+ },
+ {
+ "title": "数据质量",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "数据质量"
+ ],
+ "key": "/guide/data-quality"
+ },
+ {
+ "title": "升级",
+ "children": [
+ {
+ "title": "不向前兼容的更新",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "升级",
+ "不向前兼容的更新"
+ ],
+ "key": "/guide/upgrade/incompatible"
+ },
+ {
+ "title": "升级步骤",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "升级",
+ "升级步骤"
+ ],
+ "key": "/guide/upgrade/upgrade"
+ }
+ ],
+ "location": [
+ "功能介绍",
+ "升级"
+ ],
+ "key": "/功能介绍_menu/升级_menu"
+ },
+ {
+ "title": "扩/缩容",
+ "children": [],
+ "location": [
+ "功能介绍",
+ "扩/缩容"
+ ],
+ "key": "/guide/expansion-reduction"
+ }
+ ],
+ "location": [
+ "功能介绍"
+ ],
+ "key": "/功能介绍_menu"
+ },
+ {
+ "title": "部署指南",
+ "children": [
+ {
+ "title": "单机部署(Standalone)",
+ "children": [],
+ "location": [
+ "部署指南",
+ "单机部署(Standalone)"
+ ],
+ "key": "/guide/installation/standalone"
+ },
+ {
+ "title": "伪集群部署(Pseudo-Cluster)",
+ "children": [],
+ "location": [
+ "部署指南",
+ "伪集群部署(Pseudo-Cluster)"
+ ],
+ "key": "/guide/installation/pseudo-cluster"
+ },
+ {
+ "title": "集群部署(Cluster)",
+ "children": [],
+ "location": [
+ "部署指南",
+ "集群部署(Cluster)"
+ ],
+ "key": "/guide/installation/cluster"
+ },
+ {
+ "title": "Kubernetes部署(Kubernetes)",
+ "children": [],
+ "location": [
+ "部署指南",
+ "Kubernetes部署(Kubernetes)"
+ ],
+ "key": "/guide/installation/kubernetes"
+ },
+ {
+ "title": "集成",
+ "children": [
+ {
+ "title": "基于Rainbond部署(Cluster)",
+ "children": [],
+ "location": [
+ "部署指南",
+ "集成",
+ "基于Rainbond部署(Cluster)"
+ ],
+ "key": "/guide/integration/rainbond"
+ }
+ ],
+ "location": [
+ "部署指南",
+ "集成"
+ ],
+ "key": "/部署指南_menu/集成_menu"
+ }
+ ],
+ "location": [
+ "部署指南"
+ ],
+ "key": "/部署指南_menu"
+ },
+ {
+ "title": "架构设计",
+ "children": [
+ {
+ "title": "元数据文档",
+ "children": [],
+ "location": [
+ "架构设计",
+ "元数据文档"
+ ],
+ "key": "/architecture/metadata"
+ },
+ {
+ "title": "架构设计",
+ "children": [],
+ "location": [
+ "架构设计",
+ "架构设计"
+ ],
+ "key": "/architecture/design"
+ },
+ {
+ "title": "配置文件",
+ "children": [],
+ "location": [
+ "架构设计",
+ "配置文件"
+ ],
+ "key": "/architecture/configuration"
+ },
+ {
+ "title": "任务结构",
+ "children": [],
+ "location": [
+ "架构设计",
+ "任务结构"
+ ],
+ "key": "/architecture/task-structure"
+ },
+ {
+ "title": "负载均衡",
+ "children": [],
+ "location": [
+ "架构设计",
+ "负载均衡"
+ ],
+ "key": "/architecture/load-balance"
+ },
+ {
+ "title": "缓存",
+ "children": [],
+ "location": [
+ "架构设计",
+ "缓存"
+ ],
+ "key": "/architecture/cache"
+ }
+ ],
+ "location": [
+ "架构设计"
+ ],
+ "key": "/架构设计_menu"
+ },
+ {
+ "title": "API",
+ "children": [
+ {
+ "title": "API调用",
+ "children": [],
+ "location": [
+ "API",
+ "API调用"
+ ],
+ "key": "/guide/api/open-api"
+ },
+ {
+ "title": "PyDolphinScheduler",
+ "children": [],
+ "location": [
+ "API",
+ "PyDolphinScheduler"
+ ],
+ "key": "/guide/api/pydolphinscheduler"
+ },
+ {
+ "title": "健康检查",
+ "children": [],
+ "location": [
+ "API",
+ "健康检查"
+ ],
+ "key": "/guide/api/healthcheck"
+ }
+ ],
+ "location": [
+ "API"
+ ],
+ "key": "/api_menu"
+ },
+ {
+ "title": "贡献指南",
+ "children": [
+ {
+ "title": "SPI",
+ "children": [
+ {
+ "title": "Alert SPI",
+ "children": [],
+ "location": [
+ "贡献指南",
+ "SPI",
+ "Alert SPI"
+ ],
+ "key": "/contribute/backend/spi/alert"
+ },
+ {
+ "title": "Datasource SPI",
+ "children": [],
+ "location": [
+ "贡献指南",
+ "SPI",
+ "Datasource SPI"
+ ],
+ "key": "/contribute/backend/spi/datasource"
+ },
+ {
+ "title": "Registry SPI",
+ "children": [],
+ "location": [
+ "贡献指南",
+ "SPI",
+ "Registry SPI"
+ ],
+ "key": "/contribute/backend/spi/registry"
+ },
+ {
+ "title": "Task SPI",
+ "children": [],
+ "location": [
+ "贡献指南",
+ "SPI",
+ "Task SPI"
+ ],
+ "key": "/contribute/backend/spi/task"
+ }
+ ],
+ "location": [
+ "贡献指南",
+ "SPI"
+ ],
+ "key": "/贡献指南_menu/spi_menu"
+ },
+ {
+ "title": "环境搭建",
+ "children": [],
+ "location": [
+ "贡献指南",
+ "环境搭建"
+ ],
+ "key": "/contribute/development-environment-setup"
+ },
+ {
+ "title": "前端开发",
+ "children": [],
+ "location": [
+ "贡献指南",
+ "前端开发"
+ ],
+ "key": "/contribute/frontend-development"
+ }
+ ],
+ "location": [
+ "贡献指南"
+ ],
+ "key": "/贡献指南_menu"
+ },
+ {
+ "title": "DSIP",
+ "children": [
+ {
+ "title": "DSIP",
+ "children": [],
+ "location": [
+ "DSIP",
+ "DSIP"
+ ],
+ "key": "/DSIP"
+ }
+ ],
+ "location": [
+ "DSIP"
+ ],
+ "key": "/dsip_menu"
+ }
+]
\ No newline at end of file
diff --git a/fetch/download.json b/fetch/download.json
index 6ee33cc968..f2de46e9df 100644
--- a/fetch/download.json
+++ b/fetch/download.json
@@ -1,6 +1,25 @@
{
+ "3.1.6": {
+ "time": "2023-05-15",
+ "src": {
+ "src": "https://www.apache.org/dyn/closer.lua/dolphinscheduler/3.1.6/apache-dolphinscheduler-3.1.6-src.tar.gz",
+ "asc": "https://downloads.apache.org/dolphinscheduler/3.1.6/apache-dolphinscheduler-3.1.6-src.tar.gz.asc",
+ "sha512": "https://downloads.apache.org/dolphinscheduler/3.1.6/apache-dolphinscheduler-3.1.6-src.tar.gz.sha512"
+ },
+ "bin": {
+ "src": "https://www.apache.org/dyn/closer.lua/dolphinscheduler/3.1.6/apache-dolphinscheduler-3.1.6-bin.tar.gz",
+ "asc": "https://downloads.apache.org/dolphinscheduler/3.1.6/apache-dolphinscheduler-3.1.6-bin.tar.gz.asc",
+ "sha512": "https://downloads.apache.org/dolphinscheduler/3.1.6/apache-dolphinscheduler-3.1.6-bin.tar.gz.sha512"
+ },
+ "deployment": [
+ "Standalone",
+ "Pseudo Cluster",
+ "Cluster",
+ "Kubernetes"
+ ]
+ },
"3.1.5": {
- "time": "2023-4-6",
+ "time": "2023-04-06",
"src": {
"src": "https://www.apache.org/dyn/closer.lua/dolphinscheduler/3.1.5/apache-dolphinscheduler-3.1.5-src.tar.gz",
"asc": "https://downloads.apache.org/dolphinscheduler/3.1.5/apache-dolphinscheduler-3.1.5-src.tar.gz.asc",
diff --git a/data/faq/en-us.json b/fetch/faq/en-us/3.1.6.json
similarity index 93%
copy from data/faq/en-us.json
copy to fetch/faq/en-us/3.1.6.json
index f3e8df33a6..76b73292c4 100644
--- a/data/faq/en-us.json
+++ b/fetch/faq/en-us/3.1.6.json
@@ -1,343 +1,229 @@
[
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: What's the name of this project?</h2>",
"a": "\n<p>A: DolphinScheduler</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: DolphinScheduler service introduction and recommended running memory</h2>",
"a": "\n<p>A: DolphinScheduler consists of 5 services, MasterServer, WorkerServer, ApiServer, AlertServer, LoggerServer and UI.</p>\n<table>\n<thead>\n<tr>\n<th>Service</th>\n<th>Description</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>MasterServer</td>\n<td>Mainly responsible for DAG segmentation and task status monitoring</td>\n</tr>\n<tr>\n<td>WorkerServer/LoggerServer</td>\n<td>Mainly responsible for the submission, execution and update of task status. LoggerServer is used for Rest [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: Which mailboxes does the system support?</h2>",
"a": "\n<p>A: Support most mailboxes, qq, 163, 126, 139, outlook, aliyun, etc. are supported. Support TLS and SSL protocols, these can be configured in the ui of dolphinscheduler:\n<a href=\"../en/guide/alert/email.md\">How to setup email alarm</a>.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: What are the common system variable time parameters and how do I use them?</h2>",
"a": "\n<p>A: Please refer to 'System parameter' in the system-manual</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: pip install kazoo This installation gives an error. Is it necessary to install?</h2>",
"a": "\n<p>A: This is the python connection Zookeeper needs to use, it is used to delete the master/worker temporary node info in the Zookeeper. so you can ignore error if it's your first install. after version 1.3.0, kazoo is not been needed, we use program to replace what kazoo done</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: How to specify the machine running task</h2>",
"a": "\n<p>A: version 1.2 and berfore, Use <strong>the administrator</strong> to create a Worker group, <strong>specify the Worker group</strong> when the <strong>process definition starts</strong>, or <strong>specify the Worker group on the task node</strong>. If not specified, use Default, <strong>Default is to select one of all the workers in the cluster to use for task submission and execution.</strong>\nversion 1.3, you can set worker group for the worker</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: Priority of the task</h2>",
"a": "\n<p>A: We also support <strong>the priority of processes and tasks</strong>. Priority We have five levels of <strong>HIGHEST, HIGH, MEDIUM, LOW and LOWEST</strong>. <strong>You can set the priority between different process instances, or you can set the priority of different task instances in the same process instance.</strong> For details, please refer to the task priority design in the architecture-design.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: dolphinscheduler-grpc gives an error</h2>",
"a": "\n<p>A: Execute in the root directory: mvn -U clean package assembly:assembly -Dmaven.test.skip=true , then refresh the entire project.\nversion 1.3 not use grpc, we use netty directly</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: Does DolphinScheduler support running on windows?</h2>",
"a": "\n<p>A: In theory, <strong>only the Worker needs to run on Linux</strong>. Other services can run normally on Windows. But it is still recommended to deploy on Linux.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: UI compiles node-sass prompt in linux: Error: EACCESS: permission denied, mkdir xxxx</h2>",
"a": "\n<p>A: Install <strong>npm install node-sass --unsafe-perm</strong> separately, then <strong>npm install</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: UI cannot log in normally.</h2>",
"a": "\n<p>A: 1, if it is node startup, check whether the .env API_BASE configuration under dolphinscheduler-ui is the Api Server service address.</p>\n<p> 2, If it is nginx booted and installed via <strong>install-dolphinscheduler-ui.sh</strong>, check if the proxy_pass \t\t\tconfiguration in <strong>/etc/nginx/conf.d/dolphinscheduler.conf</strong> is the Api Server service address</p>\n<p> 3, if the above configuration is correct, then please check if the Api S [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: After the process definition is manually started or scheduled, no process instance is generated.</h2>",
"a": "\n<p>A: 1, first <strong>check whether the MasterServer service exists through jps</strong>, or directly check whether there is a master service in zk from the service monitoring.</p>\n<p> 2,If there is a master service, check <strong>the command status statistics</strong> or whether new records are added in <strong>t_ds_error_command</strong>. If it is added, <strong>please check the message field.</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : The task status is always in the successful submission status.</h2>",
"a": "\n<p>A: 1, <strong>first check whether the WorkerServer service exists through jps</strong>, or directly check whether there is a worker service in zk from the service monitoring.</p>\n<p> 2,If the <strong>WorkerServer</strong> service is normal, you need to <strong>check whether the MasterServer puts the task task in the zk queue. You need to check whether the task is blocked in the MasterServer log and the zk queue.</strong></p>\n<p> 3, if there is no problem [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: Is there a Docker image and a Dockerfile?</h2>",
"a": "\n<p>A: Provide Docker image and Dockerfile.</p>\n<p>Docker image address: https://hub.docker.com/r/escheduler/escheduler_images</p>\n<p>Dockerfile address: https://github.com/qiaozhanwei/escheduler_dockerfile/tree/master/docker_escheduler</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Need to pay attention to the problem in install.sh</h2>",
"a": "\n<p>A: 1, if the replacement variable contains special characters, <strong>use the \\ transfer character to transfer</strong></p>\n<p> 2, installPath="/data1_1T/dolphinscheduler", <strong>this directory can not be the same as the install.sh directory currently installed with one click.</strong></p>\n<p> 3, deployUser = "dolphinscheduler", <strong>the deployment user must have sudo privileges</strong>, because the worker is executed by sudo - [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Process definition and process instance offline exception</h2>",
"a": "\n<p>A : For <strong>versions prior to 1.0.4</strong>, modify the code under the escheduler-api cn.escheduler.api.quartz package.</p>\n<pre><code>public boolean deleteJob(String jobName, String jobGroupName) {\n lock.writeLock().lock();\n try {\n JobKey jobKey = new JobKey(jobName,jobGroupName);\n if(scheduler.checkExists(jobKey)){\n logger.info("try to delete job, job name: {}, job group name: {},", jobName, jobGroupName);\n return sched [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: Can the tenant created before the HDFS startup use the resource center normally?</h2>",
"a": "\n<p>A: No. Because the tenant created by HDFS is not started, the tenant directory will not be registered in HDFS. So the last resource will report an error.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: In the multi-master and multi-worker state, the service is lost, how to be fault-tolerant</h2>",
"a": "\n<p>A: <strong>Note:</strong> <strong>Master monitors Master and Worker services.</strong></p>\n<p> 1，If the Master service is lost, other Masters will take over the process of the hanged Master and continue to monitor the Worker task status.</p>\n<p> 2，If the Worker service is lost, the Master will monitor that the Worker service is gone. If there is a Yarn task, the Kill Yarn task will be retried.</p>\n<p>Please see the fault-tolerant design in the architecture for d [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Fault tolerance for a machine distributed by Master and Worker</h2>",
"a": "\n<p>A: The 1.0.3 version only implements the fault tolerance of the Master startup process, and does not take the Worker Fault Tolerance. That is to say, if the Worker hangs, no Master exists. There will be problems with this process. We will add Master and Worker startup fault tolerance in version <strong>1.1.0</strong> to fix this problem. If you want to manually modify this problem, you need to <strong>modify the running task for the running worker task that is running the [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Timing is easy to set to execute every second</h2>",
"a": "\n<p>A : Note when setting the timing. If the first digit (* * * * * ? *) is set to *, it means execution every second. <strong>We will add a list of recently scheduled times in version 1.1.0.</strong> You can see the last 5 running times online at http://cron.qqe2.com/</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: Is there a valid time range for timing?</h2>",
"a": "\n<p>A: Yes, <strong>if the timing start and end time is the same time, then this timing will be invalid timing. If the end time of the start and end time is smaller than the current time, it is very likely that the timing will be automatically deleted.</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : There are several implementations of task dependencies</h2>",
"a": "\n<p>A:\t1, the task dependency between <strong>DAG</strong>, is <strong>from the zero degree</strong> of the DAG segmentation</p>\n<p>\t\t2, there are <strong>task dependent nodes</strong>, you can achieve cross-process tasks or process dependencies, please refer to the (DEPENDENT) node design in the system-manual.</p>\n<p>\tNote: <strong>Cross-project processes or task dependencies are not supported</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: There are several ways to start the process definition.</h2>",
"a": "\n<p>A: 1, in <strong>the process definition list</strong>, click the <strong>Start</strong> button.</p>\n<p> 2, <strong>the process definition list adds a timer</strong>, scheduling start process definition.</p>\n<p> 3, process definition <strong>view or edit</strong> the DAG page, any <strong>task node right click</strong> Start process definition.</p>\n<p> 4, you can define DAG editing for the process, set the running flag of some tasks to <strong>proh [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Python task setting Python version</h2>",
"a": "\n<p>A:\t1，<strong>for the version after 1.0.3</strong> only need to modify PYTHON_HOME in <code>bin/env/dolphinscheduler_env.sh</code></p>\n<pre><code>export PYTHON_HOME=/bin/python\n</code></pre>\n<p>Note: This is <strong>PYTHON_HOME</strong> , which is the absolute path of the python command, not the simple PYTHON_HOME. Also note that when exporting the PATH, you need to directly</p>\n<pre><code>export PATH=$HADOOP_HOME/bin:$SPARK_HOME1/bin:$SPARK_HOME2/bin:$PYTHON_HOME:$JAV [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Worker Task will generate a child process through sudo -u tenant sh xxx.command, will kill when kill</h2>",
"a": "\n<p>A： We will add the kill task in 1.0.4 and kill all the various child processes generated by the task.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q ： How to use the queue in DolphinScheduler, what does the user queue and tenant queue mean?</h2>",
"a": "\n<p>A ： The queue in the DolphinScheduler can be configured on the user or the tenant. <strong>The priority of the queue specified by the user is higher than the priority of the tenant queue.</strong> For example, to specify a queue for an MR task, the queue is specified by mapreduce.job.queuename.</p>\n<p>Note: When using the above method to specify the queue, the MR uses the following methods:</p>\n<pre><code> Configuration conf = new Configuration();\nGenericOptionsParser [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Master or Worker reports the following alarm</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://analysys.github.io/easyscheduler_docs/images/master_worker_lack_res.png\" width=\"60%\" />\n </p>\n<p>A ： Change the value of master.properties <strong>master.reserved.memory</strong> under conf to a smaller value, say 0.1 or the value of worker.properties <strong>worker.reserved.memory</strong> is a smaller value, say 0.1</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q: The hive version is 1.1.0+cdh5.15.0, and the SQL hive task connection is reported incorrectly.</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://analysys.github.io/easyscheduler_docs/images/cdh_hive_error.png\" width=\"60%\" />\n </p>\n<p>A ： Will hive pom</p>\n<pre><code><dependency>\n <groupId>org.apache.hive</groupId>\n <artifactId>hive-jdbc</artifactId>\n <version>2.3.9</version>\n</dependency>\n</code></pre>\n<p>change into</p>\n<pre><code><dependency>\n <groupId>org.apache.hive</groupId>\n [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : how to add a worker server</h2>",
"a": "\n<p>A: 1, Create deployment user and hosts mapping, please refer 1.3 part of <a href=\"https://dolphinscheduler.apache.org/en-us/docs/laster/user_doc/installation/cluster.html\">cluster deployment</a></p>\n<p>\t\t2, Configure hosts mapping and ssh access and modify directory permissions. please refer 1.4 part of <a href=\"https://dolphinscheduler.apache.org/en-us/docs/laster/user_doc/installation/cluster.html\">cluster deployment</a></p>\n<p>\t\t3, Copy the deployment direct [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : When DolphinScheduler release a new version, and the change between current version and latest, and how to upgrade, and version number specification</h2>",
"a": "\n<p>A: 1, The release process of Apache Project happens in the mailing list. You can subscribe DolphinScheduler's mailing list and then when the release is in process, you'll receive release emails. Please follow this <a href=\"https://github.com/apache/dolphinscheduler#get-help\">introduction</a> to subscribe DolphinScheduler's mailing list.</p>\n<p>2, When new version published, there would be release note which describe the change log, and there also have upgrade document f [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Subsequent tasks can execute even front task failed</h2>",
"a": "\n<p>A: When start the workflow, you can set the task failure strategy: continue or failure.\n<img src=\"https://user-images.githubusercontent.com/15833811/80368215-ee378080-88be-11ea-9074-01a33d012b23.png\" alt=\"set task failure strategy\"></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Workflow template DAG, workflow instance, work task and what is the relationship among them? A DAG supports a maximum concurrency of 100, does it mean that 100 workflow instances are generated and run concurrently? A task node in a DAG also has a concurrent number configuration. Does it mean that tasks can run concurrently with multiple threads? Is the maximum number 100?</h2>",
"a": "\n<p>A:</p>\n<p>1.2.1 version</p>\n<pre><code>master.properties\nControl the max parallel number of master node workflows\nmaster.exec.threads=100\n\nControl the max number of parallel tasks in each workflow\nmaster.exec.task.number=20\n\nworker.properties\nControl the max parallel number of worker node tasks\nworker.exec.threads=100\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Worker group manage page no buttons displayed</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/39816903/81903776-d8cb9180-95f4-11ea-98cb-94ca1e6a1db5.png\" width=\"60%\" />\n</p>\nA: For version 1.3.0, we want to support k8s, while the ip always will be changed, so can't config on the UI, worker can config group name in the worker.properties.\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Why not add mysql jdbc connector to docker image</h2>",
"a": "\n<p>A: The license of mysql jdbc connector is not compatible with apache v2 license, so it can't be included by docker image.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Allways fail when a task instance submit multiple yarn application</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/16174111/81312485-476e9380-90b9-11ea-9aad-ed009db899b1.png\" width=\"60%\" />\n </p>\nA： This bug have fix in dev and in Requirement/TODO list.\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Master server and worker server stop abnormally after run for a few days</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/18378986/81293969-c3101680-90a0-11ea-87e5-ac9f0dd53f5e.png\" width=\"60%\" />\n </p>\nA: Session timeout is too short, only 0.3 seconds. Change the config item in zookeeper.properties:\n<pre><code>zookeeper.session.timeout=60000\nzookeeper.connection.timeout=30000\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Started using the docker-compose default configuration and display zookeeper errors</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/42579056/80374318-13c98780-88c9-11ea-8d5f-53448b957f02.png\" width=\"60%\" />\n </p>\nA: This problem is solved in dev-1.3.0. This [pr](https://github.com/apache/dolphinscheduler/pull/2595) has solved this bug, brief change log:\n<pre><code>1. add zookeeper environment variable ZOO_4LW_COMMANDS_WHITELIST in docker-compose.yml file.\n2. change the data type of minLatency, avgLatency and maxLatency fr [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Interface show some task would be running all the time when db delayed and log show task instance is null</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/51871547/80302626-b1478d00-87dd-11ea-97d4-08aa2244a6d0.jpg\" width=\"60%\" />\n </p>\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/51871547/80302626-b1478d00-87dd-11ea-97d4-08aa2244a6d0.jpg\" width=\"60%\" />\n </p>\n<p>A: This <a href=\"https://github.com/apache/dolphinscheduler/issues/1477\">bug</a> describe the problem detail and it has been been solved in version [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Zookeeper masters znode list ip address is 127.0.0.1, instead of wanted ip eth0 or eth1, and may can't see task log</h2>",
"a": "\n<p>A: bug fix:</p>\n<pre><code>1, confirm hostname\n$hostname\nhadoop1\n2, hostname -i\n127.0.0.1 10.3.57.15\n3, edit /etc/hosts,delete hadoop1 from 127.0.0.1 record\n$cat /etc/hosts\n127.0.0.1 localhost\n10.3.57.15 ds1 hadoop1\n4, hostname -i\n10.3.57.15\n</code></pre>\n<p>Hostname cmd return server hostname, hostname -i return all matched ips configured in /etc/hosts. So after I delete the hostname matched with 127.0.0.1, and only remain internal ip resolution, instead of r [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : The scheduling system set a second frequency task, causing the system to crash</h2>",
"a": "\n<p>A: The scheduling system not support second frequency task.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Compile front-end code(dolphinscheduler-ui) show error cannot download "https://github.com/sass/node-sass/releases/download/v4.13.1/darwin-x64-72_binding.node"</h2>",
"a": "\n<p>A: 1, cd dolphinscheduler-ui and delete node_modules directory</p>\n<pre><code>sudo rm -rf node_modules\n</code></pre>\n<p>\t2, install node-sass through npm.taobao.org</p>\n<pre><code>sudo npm uninstall node-sass\nsudo npm i node-sass --sass_binary_site=https://npm.taobao.org/mirrors/node-sass/\n</code></pre>\n<p>3, if the 2nd step failure, please, <a href=\"https://dolphinscheduler.apache.org/en-us/development/frontend-development.html\">referer url</a></p>\n<pre><code> [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : How to config when use mysql as database instead of postgres</h2>",
"a": "\n<p>A: 1, Edit project root dir maven config file, remove scope test property so that mysql driver can be loaded.</p>\n<pre><code><dependency>\n\t<groupId>mysql</groupId>\n\t<artifactId>mysql-connector-java</artifactId>\n\t<version>${mysql.connector.version}</version>\n\t<scope>test<scope>\n</dependency>\n</code></pre>\n<p>\t2, Edit application-dao.properties and quzrtz.properties config file to use mysql driver.\nDe [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : How does a shell task run</h2>",
"a": "\n<p>A: 1, Where is the executed server? Specify one worker to run the task, you can create worker group in Security Center, then the task can be send to the particular worker. If a worker group have multiple servers, which server actually execute is determined by scheduling and has randomness.</p>\n<p>\t2, If it is a shell file of a path on the server, how to point to the path? The server shell file, involving permissions issues, it is not recommended to do so. It is recommen [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : What’s the best deploy mode you suggest in production env</h2>",
"a": "\n<p>A: 1, I suggest you use 3 nodes for stability if you don't have too many tasks to run. And deploy Master/Worker server on different nodes is better. If you only have one node, you of course only can deploy them together! By the way, how many machines you need is determined by your business. The DolphinScheduler system itself does not use too many resources. Test more, and you'll find the right way to use a few machines.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : DEPENDENT Task Node</h2>",
"a": "\n<p>A: 1, DEPENDENT task node actually does not have script, it used for config data cycle dependent logic, and then add task node after that to realize task cycle dependent.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : How to change the boot port of the master</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/8263441/62352160-0f3e9100-b53a-11e9-95ba-3ae3dde49c72.png\" width=\"60%\" />\n </p>\nA: 1, modify application_master.properties, for example: server.port=12345.\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Scheduled tasks cannot be online</h2>",
"a": "\n<p>A: 1, We can successly create scheduled task and add one record into t_scheduler_schedules table, but when I click online, front page no reaction and will lock table t_scheduler_schedules, and tested set field release_state value to 1 in table t_scheduler_schedules, and task display online state. For DS version above 1.2 table name is t_ds_schedules, other version table name is t_scheduler_schedules.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : What is the address of swagger ui</h2>",
"a": "\n<p>A: 1, For version 3.1.0+ is http://apiServerIp:apiServerPort/dolphinscheduler/swagger-ui/index.html,\nfor version 1.2+ is http://apiServerIp:apiServerPort/dolphinscheduler/doc.html others is http://apiServerIp:apiServerPort/escheduler/doc.html.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Front-end installation package is missing files</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/41460919/61437083-d960b080-a96e-11e9-87f1-297ba3aca5e3.png\" width=\"60%\" />\n </p>\n <p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/41460919/61437218-1b89f200-a96f-11e9-8e48-3fac47eb2389.png\" width=\"60%\" />\n </p>\n<p>A: 1, User changed the config api server config file and item\n<img src=\"https://user-images.githubusercontent.com/41460919/61678323-1b09a680-ad3 [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Upload a relatively large file blocked</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/21357069/58231400-805b0e80-7d69-11e9-8107-7f37b06a95df.png\" width=\"60%\" />\n </p>\nA: 1, Edit ngnix config file, edit upload max size client_max_body_size 1024m.\n<p>\t2, the version of Google Chrome is old, and the latest version of the browser has been updated.</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Create a spark data source, click "Test Connection", the system will fall back to the login page</h2>",
"a": "\n<p>A: 1, edit nginx config file /etc/nginx/conf.d/escheduler.conf</p>\n<pre><code>proxy_connect_timeout 300s;\nproxy_read_timeout 300s;\nproxy_send_timeout 300s;\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : Workflow Dependency</h2>",
"a": "\n<p>A: 1, It is currently judged according to natural days, at the end of last month: the judgment time is the workflow A start_time/scheduler_time between '2019-05-31 00:00:00' and '2019-05-31 23:59:59'. Last month: It is judged that there is an A instance completed every day from the 1st to the end of the month. Last week: There are completed A instances 7 days last week. The first two days: Judging yesterday and the day before yesterday, there must be a completed A instance [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q : DS Backend Inteface Document</h2>",
"a": "\n<p>A: 1, http://106.75.43.194:8888/dolphinscheduler/swagger-ui/index.html?language=en.</p>\n<h2>During the operation of dolphinscheduler, the ip address is obtained incorrectly</h2>\n<p>When the master service and worker service are registered with zookeeper, relevant information will be created in the form of ip:port</p>\n<p>If the ip address is obtained incorrectly, please check the network information. For example, in the Linux system, use the <code>ifconfig</code> command [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Deploy for multiple YARN clusters</h2>",
"a": "\n<p>A：By deploying different worker in different yarn clusters，the steps are as follows(eg: AWS EMR):</p>\n<ol>\n<li>\n<p>Deploying the worker server on the master node of the EMR cluster</p>\n</li>\n<li>\n<p>Changing <code>yarn.application.status.address</code> to current emr's yarn url in the <code>conf/common.properties</code></p>\n</li>\n<li>\n<p>Execute command <code>bin/dolphinscheduler-daemon.sh start worker-server</code> to start worker-server</p>\n</li>\n</ol>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Update process definition error: Duplicate key TaskDefinition</h2>",
"a": "\n<p>A：Before DS 2.0.4 (after 2.0.0-alpha), there may be a problem of duplicate keys TaskDefinition due to version switching, which may cause the update workflow to fail; you can refer to the following SQL to delete duplicate data, taking MySQL as an example: (Note: Before operating, be sure to back up the original data, the SQL from pr<a href=\"https://github.com/apache/dolphinscheduler/pull/8408\">#8408</a>)</p>\n<pre><code class=\"language-SQL\"><span class=\"hljs-keyword\"> [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Upgrade from 2.0.1 to 2.0.5 using PostgreSQL database failed</h2>",
"a": "\n<p>A：The repair can be completed by executing the following SQL in the database:</p>\n<pre><code class=\"language-SQL\"><span class=\"hljs-keyword\">update</span> t_ds_version <span class=\"hljs-keyword\">set</span> version<span class=\"hljs-operator\">=</span><span class=\"hljs-string\">'2.0.1'</span>;\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Can not find python-gateway-server in distribute package</h2>",
"a": "\n<p>A：After version 3.0.0-alpha, Python gateway server integrate into API server, and Python gateway service will start when you\nstart API server. If you want disabled when Python gateway service you could change API server configuration in path\n<code>api-server/conf/application.yaml</code> and change attribute <code>python-gateway.enabled : false</code>.</p>\n<hr>\n<p>We will collect more FAQ later</p>\n"
}
diff --git a/fetch/faq/version.json b/fetch/faq/version.json
index d14eada7c0..2105b6566b 100644
--- a/fetch/faq/version.json
+++ b/fetch/faq/version.json
@@ -10,5 +10,6 @@
"3.1.2",
"3.1.3",
"3.1.4",
- "3.1.5"
+ "3.1.5",
+ "3.1.6"
]
\ No newline at end of file
diff --git a/data/faq/zh-cn.json b/fetch/faq/zh-cn/3.1.6.json
similarity index 93%
copy from data/faq/zh-cn.json
copy to fetch/faq/zh-cn/3.1.6.json
index a9588cafeb..d6354e6ee0 100644
--- a/data/faq/zh-cn.json
+++ b/fetch/faq/zh-cn/3.1.6.json
@@ -1,337 +1,225 @@
[
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：项目的名称是？</h2>",
"a": "\n<p>A：DolphinScheduler</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：DolphinScheduler 服务介绍及建议运行内存</h2>",
"a": "\n<p>A：DolphinScheduler 由 5 个服务组成，MasterServer、WorkerServer、ApiServer、AlertServer、LoggerServer 和 UI。</p>\n<table>\n<thead>\n<tr>\n<th>服务</th>\n<th>说明</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>MasterServer</td>\n<td>主要负责 <strong>DAG</strong> 的切分和任务状态的监控</td>\n</tr>\n<tr>\n<td>WorkerServer/LoggerServer</td>\n<td>主要负责任务的提交、执行和任务状态的更新。LoggerServer 用于 Rest Api 通过 <strong>RPC</strong> 查看日志</td>\n</tr>\n<tr>\n<td>ApiServer</td>\n<td>提供 Rest Api 服务，供 UI 进行调用</td>\n</tr>\n<tr>\n<td>Aler [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：系统支持哪些邮箱？</h2>",
"a": "\n<p>A：支持绝大多数邮箱，qq、163、126、139、outlook、aliyun 等皆支持。支持 <strong>TLS 和 SSL</strong> 协议，可以在dolphinscheduler的ui中进行配置：\n<a href=\"../zh/guide/alert/email.md\">如何配置邮箱告警</a>。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：常用的系统变量时间参数有哪些，如何使用？</h2>",
"a": "\n<p>A：请参考<a href=\"https://dolphinscheduler.apache.org/zh-cn/docs/latest/user_doc/guide/parameter/built-in.html\">使用手册</a> 第8小节</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：pip install kazoo 这个安装报错。是必须安装的吗？</h2>",
"a": "\n<p>A： 这个是 python 连接 Zookeeper 需要使用到的，用于删除Zookeeper中的master/worker临时节点信息。所以如果是第一次安装，就可以忽略错误。在1.3.0之后，kazoo不再需要了，我们用程序来代替kazoo所做的</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：怎么指定机器运行任务</h2>",
"a": "\n<p>A：使用 <strong>管理员</strong> 创建 Worker 分组，在 <strong>流程定义启动</strong> 的时候可<strong>指定Worker分组</strong>或者在<strong>任务节点上指定Worker分组</strong>。如果不指定，则使用 Default，<strong>Default默认是使用的集群里所有的Worker中随机选取一台来进行任务提交、执行</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：任务的优先级</h2>",
"a": "\n<p>A：我们同时 <strong>支持流程和任务的优先级</strong>。优先级我们有 <strong>HIGHEST、HIGH、MEDIUM、LOW 和 LOWEST</strong> 五种级别。<strong>可以设置不同流程实例之间的优先级，也可以设置同一个流程实例中不同任务实例的优先级</strong>。详细内容请参考任务优先级设计 https://analysys.github.io/easyscheduler_docs_cn/%E7%B3%BB%E7%BB%9F%E6%9E%B6%E6%9E%84%E8%AE%BE%E8%AE%A1.html#%E7%B3%BB%E7%BB%9F%E6%9E%B6%E6%9E%84%E8%AE%BE%E8%AE%A1</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：dolphinscheduler-grpc 报错</h2>",
"a": "\n<p>A：在 1.2 及以前版本中，在根目录下执行：mvn -U clean package assembly:assembly -Dmaven.test.skip=true,然后刷新下整个项目就好，1.3版本中不再使用 GRPC 进行通信了</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：DolphinScheduler 支持 windows 上运行么</h2>",
"a": "\n<p>A： 理论上只有 <strong>Worker 是需要在 Linux 上运行的</strong>，其它的服务都是可以在 windows 上正常运行的。但是还是建议最好能在 linux 上部署使用</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：UI 在 linux 编译 node-sass 提示：Error：EACCESS:permission denied，mkdir xxxx</h2>",
"a": "\n<p>A：单独安装 <strong>npm install node-sass --unsafe-perm</strong>，之后再 <strong>npm install</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：UI 不能正常登陆访问</h2>",
"a": "\n<p>A： 1，如果是 node 启动的查看 dolphinscheduler-ui 下的 .env 文件里的 API_BASE 配置是否是 Api Server 服务地址</p>\n<p> 2，如果是 nginx 启动的并且是通过 <strong>install-dolphinscheduler-ui.sh</strong> 安装的，查看</p>\n<p> <strong>/etc/nginx/conf.d/dolphinscheduler.conf</strong> 中的 proxy_pass 配置是否是 Api Server 服务地址</p>\n<p> 3，如果以上配置都是正确的，那么请查看 Api Server 服务是否是正常的，</p>\n<p>\t\t\tcurl http://localhost:12345/dolphinscheduler/users/get-user-info 查看 Api Server 日志，</p>\n<p>\t\t\t如果提示 cn.dol [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：流程定义手动启动或调度启动之后，没有流程实例生成</h2>",
"a": "\n<p>A： \t 1，首先通过 <strong>jps 查看MasterServer服务是否存在</strong>，或者从服务监控直接查看 zk 中是否存在 master 服务</p>\n<p>\t 2，如果存在 master 服务，查看 <strong>命令状态统计</strong> 或者 <strong>t_ds_error_command</strong> 中是否增加的新记录，如果增加了，<strong>请查看 message 字段定位启动异常原因</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：任务状态一直处于提交成功状态</h2>",
"a": "\n<p>A： 1，首先通过 <strong>jps 查看 WorkerServer 服务是否存在</strong>，或者从服务监控直接查看 zk 中是否存在 worker 服务</p>\n<p> 2，如果 <strong>WorkerServer</strong> 服务正常，需要 <strong>查看 MasterServer 是否把 task 任务放到 zk 队列中</strong> ，<strong>需要查看 MasterServer 日志及 zk 队列中是否有任务阻塞</strong></p>\n<p>\t 3，如果以上都没有问题，需要定位是否指定了 Worker 分组，但是 <strong>Worker 分组的机器不是在线状态</strong></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：install.sh 中需要注意问题</h2>",
"a": "\n<p>A： \t 1，如果替换变量中包含特殊字符，<strong>请用 \\ 转移符进行转移</strong></p>\n<p>\t 2，installPath="/data1_1T/dolphinscheduler"，<strong>这个目录不能和当前要一键安装的 install.sh 目录是一样的</strong></p>\n<p>\t 3，deployUser="dolphinscheduler"，<strong>部署用户必须具有 sudo 权限</strong>，因为 worker 是通过 sudo -u 租户 sh xxx.command 进行执行的</p>\n<p>\t 4，monitorServerState="false"，服务监控脚本是否启动，默认是不启动服务监控脚本的。<strong>如果启动服务监控脚本，则每 5 分钟定时来监控 master 和 worker 的服务是否 down 机，如果 down 机则会自动重启</strong>< [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：流程定义和流程实例下线异常</h2>",
"a": "\n<p>A ： 对于 <strong>1.0.4 以前的版本中</strong>，修改 dolphinscheduler-api cn.dolphinscheduler.api.quartz 包下的代码即可</p>\n<pre><code>public boolean deleteJob(String jobName, String jobGroupName) {\n lock.writeLock().lock();\n try {\n JobKey jobKey = new JobKey(jobName,jobGroupName);\n if(scheduler.checkExists(jobKey)){\n logger.info("try to delete job, job name: {}, job group name: {},", jobName, jobGroupName);\n return scheduler.deleteJob(jobKey);\n [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：HDFS 启动之前创建的租户，能正常使用资源中心吗</h2>",
"a": "\n<p>A： 不能。因为在未启动 HDFS 创建的租户，不会在 HDFS 中注册租户目录。所以上次资源会报错</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：多 Master 和多 Worker 状态下，服务掉了，怎么容错</h2>",
"a": "\n<p>A： <strong>注意：Master 监控 Master 及 Worker 服务。</strong></p>\n<p>\t1，如果 Master 服务掉了，其它的 Master 会接管挂掉的 Master 的流程，继续监控 Worker task 状态</p>\n<p>\t2，如果 Worker 服务掉了，Master 会监控到 Worker 服务掉了，如果存在 Yarn 任务，Kill Yarn 任务之后走重试</p>\n<p>具体请看容错设计：https://analysys.github.io/easyscheduler_docs_cn/%E7%B3%BB%E7%BB%9F%E6%9E%B6%E6%9E%84%E8%AE%BE%E8%AE%A1.html#%E7%B3%BB%E7%BB%9F%E6%9E%B6%E6%9E%84%E8%AE%BE%E8%AE%A1</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：对于 Master 和 Worker 一台机器伪分布式下的容错</h2>",
"a": "\n<p>A ： 1.0.3 版本只实现了 Master 启动流程容错，不走 Worker 容错。也就是说如果 Worker 挂掉的时候，没有 Master 存在。这流程将会出现问题。我们会在 <strong>1.1.0</strong> 版本中增加 Master 和 Worker 启动自容错，修复这个问题。如果想手动修改这个问题，需要针对 <strong>跨重启正在运行流程</strong> <strong>并且已经掉的正在运行的 Worker 任务，需要修改为失败</strong>，<strong>同时跨重启正在运行流程设置为失败状态</strong>。然后从失败节点进行流程恢复即可</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：定时容易设置成每秒执行</h2>",
"a": "\n<p>A ： 设置定时的时候需要注意，如果第一位（* * * * * ? *）设置成 * ，则表示每秒执行。<strong>我们将会在 1.1.0 版本中加入显示最近调度的时间列表</strong> ，使用 http://cron.qqe2.com/ 可以在线看近 5 次运行时间</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：定时有有效时间范围吗</h2>",
"a": "\n<p>A：有的，<strong>如果定时的起止时间是同一个时间，那么此定时将是无效的定时</strong>。<strong>如果起止时间的结束时间比当前的时间小，很有可能定时会被自动删除</strong></p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：任务依赖有几种实现</h2>",
"a": "\n<p>A： 1，<strong>DAG</strong> 之间的任务依赖关系，是从 <strong>入度为零</strong> 进行 DAG 切分的</p>\n<p>\t 2，有 <strong>任务依赖节点</strong> ，可以实现跨流程的任务或者流程依赖，具体请参考 依赖(DEPENDENT)节点：https://analysys.github.io/easyscheduler_docs_cn/%E7%B3%BB%E7%BB%9F%E4%BD%BF%E7%94%A8%E6%89%8B%E5%86%8C.html#%E4%BB%BB%E5%8A%A1%E8%8A%82%E7%82%B9%E7%B1%BB%E5%9E%8B%E5%92%8C%E5%8F%82%E6%95%B0%E8%AE%BE%E7%BD%AE</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：流程定义有几种启动方式</h2>",
"a": "\n<p>A： 1，在 <strong>流程定义列表</strong>，点击 <strong>启动</strong> 按钮</p>\n<p>\t\t2，<strong>流程定义列表添加定时器</strong>，调度启动流程定义</p>\n<p>\t\t3，流程定义 <strong>查看或编辑</strong> DAG 页面，任意 <strong>任务节点右击</strong> 启动流程定义</p>\n<p>\t\t4，可以对流程定义 DAG 编辑，设置某些任务的运行标志位 <strong>禁止运行</strong>，则在启动流程定义的时候，将该节点的连线将从 DAG 中去掉</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Python 任务设置 Python 版本</h2>",
"a": "\n<p>A： 只需要修改 <code>bin/env/dolphinscheduler_env.sh</code> 中的 PYTHON_HOME</p>\n<pre><code>export PYTHON_HOME=/bin/python\n</code></pre>\n<p>注意：这了 <strong>PYTHON_HOME</strong> ，是 python 命令的绝对路径，而不是单纯的 PYTHON_HOME，还需要注意的是 export PATH 的时候，需要直接</p>\n<pre><code>export PATH=$HADOOP_HOME/bin:$SPARK_HOME1/bin:$SPARK_HOME2/bin:$PYTHON_HOME:$JAVA_HOME/bin:$HIVE_HOME/bin:$PATH\n</code></pre>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Worker Task 通过 sudo -u 租户 sh xxx.command 会产生子进程，在 kill 的时候，是否会杀掉</h2>",
"a": "\n<p>A： 我们会在 1.0.4 中增加 kill 任务同时，kill 掉任务产生的各种所有子进程</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：DolphinScheduler 中的队列怎么用，用户队列和租户队列是什么意思</h2>",
"a": "\n<p>A ： DolphinScheduler 中的队列可以在用户或者租户上指定队列，<strong>用户指定的队列优先级是高于租户队列的优先级的。</strong>，例如：对 MR 任务指定队列，是通过 mapreduce.job.queuename 来指定队列的。</p>\n<p>注意：MR 在用以上方法指定队列的时候，传递参数请使用如下方式：</p>\n<pre><code>Configuration conf = new Configuration();\n GenericOptionsParser optionParser = new GenericOptionsParser(conf, args);\n String[] remainingArgs = optionParser.getRemainingArgs();\n</code></pre>\n<p>如果是 Spark 任务 --queue 方式指定队列</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Master 或者 Worker 报如下告警</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://analysys.github.io/easyscheduler_docs_cn/images/master_worker_lack_res.png\" width=\"60%\" />\n </p>\n<p>A ： 修改 conf 下的 master.properties <strong>master.reserved.memory</strong> 的值为更小的值，比如说 0.1 或者</p>\n<p>worker.properties <strong>worker.reserved.memory</strong> 的值为更小的值，比如说 0.1</p>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：hive 版本是 1.1.0+cdh5.15.0，SQL hive 任务连接报错</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://analysys.github.io/easyscheduler_docs_cn/images/cdh_hive_error.png\" width=\"60%\" />\n </p>\n<p>A： 将 hive pom</p>\n<pre><code><dependency>\n <groupId>org.apache.hive</groupId>\n <artifactId>hive-jdbc</artifactId>\n <version>2.3.9</version>\n</dependency>\n</code></pre>\n<p>修改为</p>\n<pre><code><dependency>\n <groupId>org.apache.hive</groupId>\n <arti [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：如何增加一台工作服务器</h2>",
"a": "\n<p>A： 1，参考官网<a href=\"https://dolphinscheduler.apache.org/zh-cn/docs/laster/user_doc/installation/cluster.html\">部署文档</a> 1.3 小节，创建部署用户和 hosts 映射</p>\n<p>\t2，参考官网<a href=\"https://dolphinscheduler.apache.org/zh-cn/docs/laster/user_doc/installation/cluster.html\">部署文档</a> 1.4 小节，配置 hosts 映射和 ssh 打通及修改目录权限.\n 1.4 小节的最后一步是在当前新增机器上执行的，即需要给部署目录部署用户的权限</p>\n<p>\t3，复制正在运行的服务器上的部署目录到新机器的同样的部署目录下</p>\n<p>\t4，到 bin 下，启动 worker server</p>\n<pre><code>./dolphinscheduler-daem [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：DolphinScheduler 什么时候发布新版本，同时新旧版本区别，以及如何升级，版本号规范</h2>",
"a": "\n<p>A：1，Apache 项目的发版流程是通过邮件列表完成的。 你可以订阅 DolphinScheduler 的邮件列表，订阅之后如果有发版，你就可以收到邮件。请参照这篇<a href=\"https://github.com/apache/dolphinscheduler#get-help\">指引</a>来订阅 DolphinScheduler 的邮件列表。</p>\n<p>2，当项目发版的时候，会有发版说明告知具体的变更内容，同时也会有从旧版本升级到新版本的升级文档。</p>\n<p>3，版本号为 x.y.z, 当 x 增加时代表全新架构的版本。当 y 增加时代表与 y 版本之前的不兼容需要升级脚本或其他人工处理才能升级。当 z 增加代表是 bug 修复，升级完全兼容。无需额外处理。之前有个问题 1.0.2 的升级不兼容 1.0.1 需要升级脚本。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：后续任务在前置任务失败情况下仍旧可以执行</h2>",
"a": "\n<p>A：在启动工作流的时候，你可以设置失败策略：继续还是失败。\n<img src=\"https://user-images.githubusercontent.com/15833811/80368215-ee378080-88be-11ea-9074-01a33d012b23.png\" alt=\"设置任务失败策略\"></p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：工作流模板 DAG、工作流实例、工作任务及实例之间是什么关系 工作流模板 DAG、工作流实例、工作任务及实例之间是什么关系，一个 dag 支持最大并发 100，是指产生 100 个工作流实例并发运行吗？一个 dag 中的任务节点，也有并发数的配置，是指任务也可以并发多个线程运行吗？最大数 100 吗？</h2>",
"a": "\n<p>A：</p>\n<p>1.2.1 version</p>\n<pre><code> master.properties\n 设置 master 节点并发执行的最大工作流数\n master.exec.threads=100\n\n Control the number of parallel tasks in each workflow\n 设置每个工作流可以并发执行的最大任务数\n master.exec.task.number=20\n\n worker.properties\n 设置 worker 节点并发执行的最大任务数\n worker.exec.threads=100\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：工作组管理页面没有展示按钮</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/39816903/81903776-d8cb9180-95f4-11ea-98cb-94ca1e6a1db5.png\" width=\"60%\" />\n</p>\nA：1.3.0 版本，为了支持 k8s，worker ip 一直变动，因此我们不能在 UI 界面上配置，工作组可以配置在 worker.properties 上配置名称。\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：为什么不把 mysql 的 jdbc 连接包添加到 docker 镜像里面</h2>",
"a": "\n<p>A：Mysql jdbc 连接包的许可证和 apache v2 的许可证不兼容，因此它不能被加入到 docker 镜像里面。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：当一个任务提交多个 yarn 程序的时候经常失败</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/16174111/81312485-476e9380-90b9-11ea-9aad-ed009db899b1.png\" width=\"60%\" />\n</p>\nA：这个 Bug 在 dev 分支已修复，并加入到需求/待做列表。\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Master 服务和 Worker 服务在运行几天之后停止了</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/18378986/81293969-c3101680-90a0-11ea-87e5-ac9f0dd53f5e.png\" width=\"60%\" />\n</p>\nA：会话超时时间太短了，只有 0.3 秒，修改 zookeeper.properties 的配置项：\n<pre><code>zookeeper.session.timeout=60000\nzookeeper.connection.timeout=30000\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：使用 docker-compose 默认配置启动，显示 zookeeper 错误</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/42579056/80374318-13c98780-88c9-11ea-8d5f-53448b957f02.png\" width=\"60%\" />\n </p>\nA：这个问题在 dev-1.3.0 版本解决了。这个 [pr](https://github.com/apache/dolphinscheduler/pull/2595) 已经解决了这个 bug，主要的改动点：\n<pre><code>在docker-compose.yml文件中增加zookeeper的环境变量ZOO_4LW_COMMANDS_WHITELIST。\n把minLatency,avgLatency and maxLatency的类型从int改成float。\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：界面上显示任务一直运行，结束不了，从日志上看任务实例为空</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/51871547/80302626-b1478d00-87dd-11ea-97d4-08aa2244a6d0.jpg\" width=\"60%\" />\n </p>\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/51871547/80302626-b1478d00-87dd-11ea-97d4-08aa2244a6d0.jpg\" width=\"60%\" />\n </p>\nA：这个 [bug](https://github.com/apache/dolphinscheduler/issues/1477) 描述了问题的详情。这个问题在 1.2.1 版本已经被修复了。\n对于 1.2.1 以下的版本，这种情况的一些提示：\n<pre><code>1，清空 zk 下这个路径的 [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：zk 中注册的 master 信息 ip 地址是 127.0.0.1，而不是配置的域名所对应或者解析的 ip 地址，可能导致不能查看任务日志</h2>",
"a": "\n<p>A：修复 bug：</p>\n<pre><code>1、confirm hostname\n$hostname\nhadoop1\n2、hostname -i\n127.0.0.1 10.3.57.15\n3、edit /etc/hosts,delete hadoop1 from 127.0.0.1 record\n$cat /etc/hosts\n127.0.0.1 localhost\n10.3.57.15 ds1 hadoop1\n4、hostname -i\n10.3.57.15\n</code></pre>\n<p>hostname 命令返回服务器主机名，hostname -i 返回的是服务器主机名在 /etc/hosts 中所有匹配的ip地址。所以我把 /etc/hosts 中 127.0.0.1 中的主机名删掉，只保留内网 ip 的解析就可以了，没必要把 127.0.0.1 整条注释掉, 只要 hostname 命令返回值在 /etc/hosts 中对应的内网 ip 正确就可以，ds 程序取了第一个值，我理解上 ds 程序不应 [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：调度系统设置了一个秒级的任务，导致系统挂掉</h2>",
"a": "\n<p>A：调度系统不支持秒级任务。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：编译前后端代码 (dolphinscheduler-ui) 报错不能下载"https://github.com/sass/node-sass/releases/download/v4.13.1/darwin-x64-72_binding.node"</h2>",
"a": "\n<p>A：1，cd dolphinscheduler-ui 然后删除 node_modules 目录</p>\n<pre><code>sudo rm -rf node_modules\n</code></pre>\n<p>\t2，通过 npm.taobao.org 下载 node-sass</p>\n<pre><code>sudo npm uninstall node-sass\nsudo npm i node-sass --sass_binary_site=https://npm.taobao.org/mirrors/node-sass/\n</code></pre>\n<p>3，如果步骤 2 报错，请重新构建 node-saas <a href=\"https://dolphinscheduler.apache.org/en-us/development/frontend-development.html\">参考链接</a></p>\n<pre><code>sudo npm rebuild node-sass\n</code></pre> [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：当使用 mysql 作为 ds 数据库需要如何配置</h2>",
"a": "\n<p>A：1，修改项目根目录 maven 配置文件，移除 scope 的 test 属性，这样 mysql 的包就可以在其它阶段被加载</p>\n<pre><code><dependency>\n\t<groupId>mysql</groupId>\n\t<artifactId>mysql-connector-java</artifactId>\n\t<version>${mysql.connector.version}</version>\n\t<scope>test<scope>\n</dependency>\n</code></pre>\n<p>\t2，修改 application-dao.properties 和 quzrtz.properties 来使用 mysql 驱动\n默认驱动是 postgres 主要由于许可证原因。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：shell 任务是如何运行的</h2>",
"a": "\n<p>A：1，被执行的服务器在哪里配置，以及实际执行的服务器是哪台? 要指定在某个 worker 上去执行，可以在 worker 分组中配置，固定 IP，这样就可以把路径写死。如果配置的 worker 分组有多个 worker，实际执行的服务器由调度决定的，具有随机性。</p>\n<p>\t2，如果是服务器上某个路径的一个 shell 文件，怎么指向这个路径？服务器上某个路径下的 shell 文件，涉及到权限问题，不建议这么做。建议你可以使用资源中心的存储功能，然后在 shell 编辑器里面使用资源引用就可以，系统会帮助你把脚本下载到执行目录下。如果以 hdfs 作为资源中心，在执行的时候，调度器会把依赖的 jar 包，文件等资源拉到 worker 的执行目录上，我这边是 /tmp/escheduler/exec/process，该配置可以在 install.sh 中进行指定。</p>\n<p>3，以哪个用户来执行任务？执行任务的时候�
��调度器会采用 sudo -u 租户的方式去执行，租户是一个 linux 用户。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：生产环境部署方式有推荐的最佳实践吗</h2>",
"a": "\n<p>A：1，如果没有很多任务要运行，出于稳定性考虑我们建议使用 3 个节点，并且最好把 Master/Worder 服务部署在不同的节点。如果你只有一个节点，当然只能把所有的服务部署在同一个节点！通常来说，需要多少节点取决于你的业务，海豚调度系统本身不需要很多的资源。充分测试之后，你们将找到使用较少节点的合适的部署方式。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：DEPENDENT 节点</h2>",
"a": "\n<p>A：1，DEPENDENT 节点实际是没有执行体的，是专门用来配置数据周期依赖逻辑，然后再把执行节点挂载后面，来实现任务间的周期依赖。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：如何改变 Master 服务的启动端口</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/8263441/62352160-0f3e9100-b53a-11e9-95ba-3ae3dde49c72.png\" width=\"60%\" />\n </p>\nA：1，修改 application_master.properties 配置文件，例如：server.port=12345。\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：调度任务不能上线</h2>",
"a": "\n<p>A：1，我们可以成功创建调度任务，并且表 t_scheduler_schedules 中也成功加入了一条记录，但当我点击上线后，前端页面无反应且会把 t_scheduler_schedules 这张表锁定，我测试过将 t_scheduler_schedules 中的 RELEASE_state 字段手动更新为 1 这样前端会显示为上线状态。DS 版本 1.2+ 表名是 t_ds_schedules，其它版本表名是 t_scheduler_schedules。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：请问 swagger ui 的地址是什么</h2>",
"a": "\n<p>A：1， 3.1.0+ 版本地址是 http://apiServerIp:apiServerPort/dolphinscheduler/swagger-ui/index.html, 1.2+ 版本地址是：http://apiServerIp:apiServerPort/dolphinscheduler/swagger-ui/index.html?language=zh_CN&lang=cn，其它版本是 http://apiServerIp:apiServerPort/escheduler/swagger-ui/index.html?language=zh_CN&lang=cn。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：前端安装包缺少文件</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/41460919/61437083-d960b080-a96e-11e9-87f1-297ba3aca5e3.png\" width=\"60%\" />\n </p>\n <p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/41460919/61437218-1b89f200-a96f-11e9-8e48-3fac47eb2389.png\" width=\"60%\" />\n </p>\nA： 1，用户修改了 api server 配置文件中的![apiServerContextPath](https://user-images.githubusercontent.com/41460919/61678323-1b09a680-ad35-11e9-9707-3ba68bbc70d6. [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：上传比较大的文件卡住</h2>",
"a": "\n<p align=\"center\">\n <img src=\"https://user-images.githubusercontent.com/21357069/58231400-805b0e80-7d69-11e9-8107-7f37b06a95df.png\" width=\"60%\" />\n </p>\nA：1，编辑 ngnix 配置文件 vi /etc/nginx/nginx.conf，更改上传大小 client_max_body_size 1024m。\n<p>\t2，更新 google chrome 版本到最新版本。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：创建 spark 数据源，点击“测试连接”，系统回退回到登入页面</h2>",
"a": "\n<p>A：1，edit /etc/nginx/conf.d/escheduler.conf</p>\n<pre><code>proxy_connect_timeout 300s;\nproxy_read_timeout 300s;\nproxy_send_timeout 300s;\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：工作流依赖</h2>",
"a": "\n<p>A：1，目前是按照自然天来判断，上月末：判断时间是工作流 A start_time/scheduler_time between '2019-05-31 00:00:00' and '2019-05-31 23:59:59'。上月：是判断上个月从 1 号到月末每天都要有完成的A实例。上周： 上周 7 天都要有完成的 A 实例。前两天： 判断昨天和前天，两天都要有完成的 A 实例。</p>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：DS 后端接口文档</h2>",
"a": "\n<p>A：1，http://106.75.43.194:8888/dolphinscheduler/swagger-ui/index.html?language=zh_CN&lang=zh。</p>\n<h2>dolphinscheduler 在运行过程中，ip 地址获取错误的问题</h2>\n<p>master 服务、worker 服务在 zookeeper 注册时，会以 ip:port 的形式创建相关信息</p>\n<p>如果 ip 地址获取错误，请检查网络信息，如 Linux 系统通过 <code>ifconfig</code> 命令查看网络信息，以下图为例：</p>\n<p align=\"center\">\n <img src=\"/img/network/network_config.png\" width=\"60%\" />\n</p>\n<p>可以使用 dolphinscheduler 提供的三种策略，获取可用 ip：</p>\n<ul>\n<li>default: 优先获取内网网卡获取 ip 地址，其次获取外网网卡 [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Yarn多集群支持</h2>",
"a": "\n<p>A：将Worker节点分别部署至多个Yarn集群，步骤如下（例如AWS EMR）：</p>\n<ol>\n<li>\n<p>将 Worker 节点部署至 EMR 集群的 Master 节点</p>\n</li>\n<li>\n<p>将 <code>conf/common.properties</code> 中的 <code>yarn.application.status.address</code> 修改为当前集群的 Yarn 的信息</p>\n</li>\n<li>\n<p>通过 <code>bin/dolphinscheduler-daemon.sh start worker-server</code> 启动 worker-server</p>\n</li>\n</ol>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：Update process definition error: Duplicate key TaskDefinition</h2>",
"a": "\n<p>A：在DS 2.0.4之前（2.0.0-alpha之后），可能存在版本切换的重复键问题，导致更新工作流失败；可参考如下SQL进行重复数据的删除，以MySQL为例：（注意：操作前请务必备份原数据，SQL来源于pr <a href=\"https://github.com/apache/dolphinscheduler/pull/8408\">#8408</a>）</p>\n<pre><code class=\"language-SQL\"><span class=\"hljs-keyword\">DELETE</span> <span class=\"hljs-keyword\">FROM</span> t_ds_process_task_relation_log <span class=\"hljs-keyword\">WHERE</span> id <span class=\"hljs-keyword\">IN</span>\n(\n <span class=\"hljs-keyword\">SELECT</span>\n x.i [...]
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：使用Postgresql数据库从2.0.1升级至2.0.5更新失败</h2>",
"a": "\n<p>A：在数据库中执行以下SQL即可完成修复:</p>\n<pre><code class=\"language-SQL\"><span class=\"hljs-keyword\">update</span> t_ds_version <span class=\"hljs-keyword\">set</span> version<span class=\"hljs-operator\">=</span><span class=\"hljs-string\">'2.0.1'</span>;\n</code></pre>\n<hr>\n"
},
{
- "time": "2023-4-6",
- "version": "3.1.5",
"q": "<h2>Q：在二进制分发包中找不到 python-gateway-server 文件夹</h2>",
"a": "\n<p>A：在 3.0.0-alpha 版本之后，Python gateway server 集成到 api server 中，当您启动 api server 后，Python gateway server 将启动。\n如果您不想在 api server 启动的时候启动 Python gateway server，您可以修改 api server 中的配置文件 <code>api-server/conf/application.yaml</code>\n并更改可选项 <code>python-gateway.enabled</code> 中的值设置为 <code>false</code>。</p>\n<hr>\n<p>我们会持续收集更多的 FAQ。</p>\n"
}
diff --git a/fetch/version.json b/fetch/version.json
index 6c07b0d3af..5bc71be9ea 100644
--- a/fetch/version.json
+++ b/fetch/version.json
@@ -28,5 +28,6 @@
"3.1.2",
"3.1.3",
"3.1.4",
- "3.1.5"
+ "3.1.5",
+ "3.1.6"
]
\ No newline at end of file
diff --git a/img/tasks/demo/dinky_task_id.png b/img/tasks/demo/dinky_task_id.png
index 280da5f30f..f1e791caad 100644
Binary files a/img/tasks/demo/dinky_task_id.png and b/img/tasks/demo/dinky_task_id.png differ
diff --git a/pages/doc/en-us/3.1.5/DSIP.json b/pages/doc/en-us/3.1.5/DSIP.json
index b60cbe5c28..89d3615adc 100644
--- a/pages/doc/en-us/3.1.5/DSIP.json
+++ b/pages/doc/en-us/3.1.5/DSIP.json
@@ -4,7 +4,7 @@
"DSIP",
"DSIP"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "What is considered as DSIP",
diff --git a/pages/doc/en-us/3.1.5/about/features.json b/pages/doc/en-us/3.1.5/about/features.json
index 5e3f81d377..01d85bb74b 100644
--- a/pages/doc/en-us/3.1.5/about/features.json
+++ b/pages/doc/en-us/3.1.5/about/features.json
@@ -4,7 +4,7 @@
"About",
"Features"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Simple to Use",
diff --git a/pages/doc/en-us/3.1.5/about/glossary.json b/pages/doc/en-us/3.1.5/about/glossary.json
index e91bf8cdce..8df36402e8 100644
--- a/pages/doc/en-us/3.1.5/about/glossary.json
+++ b/pages/doc/en-us/3.1.5/about/glossary.json
@@ -4,7 +4,7 @@
"About",
"Glossary"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "System Architecture Design",
diff --git a/pages/doc/en-us/3.1.5/about/hardware.json b/pages/doc/en-us/3.1.5/about/hardware.json
index 1b3dadfb27..0828f347ac 100644
--- a/pages/doc/en-us/3.1.5/about/hardware.json
+++ b/pages/doc/en-us/3.1.5/about/hardware.json
@@ -4,7 +4,7 @@
"About",
"Hardware Environment"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Linux Operating System Version Requirements",
diff --git a/pages/doc/en-us/3.1.5/about/introduction.json b/pages/doc/en-us/3.1.5/about/introduction.json
index 1f4bf0277d..08681daa7a 100644
--- a/pages/doc/en-us/3.1.5/about/introduction.json
+++ b/pages/doc/en-us/3.1.5/about/introduction.json
@@ -4,7 +4,7 @@
"About",
"Introduction"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "About DolphinScheduler",
"link": "/about/introduction"
diff --git a/pages/doc/en-us/3.1.5/architecture/cache.json b/pages/doc/en-us/3.1.5/architecture/cache.json
index dcbe07ba08..88a7c505f1 100644
--- a/pages/doc/en-us/3.1.5/architecture/cache.json
+++ b/pages/doc/en-us/3.1.5/architecture/cache.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Cache"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Purpose",
diff --git a/pages/doc/en-us/3.1.5/architecture/configuration.json b/pages/doc/en-us/3.1.5/architecture/configuration.json
index da186e8a45..c517f2fd24 100644
--- a/pages/doc/en-us/3.1.5/architecture/configuration.json
+++ b/pages/doc/en-us/3.1.5/architecture/configuration.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Configuration File"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Preface",
diff --git a/pages/doc/en-us/3.1.5/architecture/design.json b/pages/doc/en-us/3.1.5/architecture/design.json
index bfba9c6038..dc48c51fa3 100644
--- a/pages/doc/en-us/3.1.5/architecture/design.json
+++ b/pages/doc/en-us/3.1.5/architecture/design.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Architecture Design"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "System Structure",
diff --git a/pages/doc/en-us/3.1.5/architecture/load-balance.json b/pages/doc/en-us/3.1.5/architecture/load-balance.json
index e3905bcc4e..f1ae97379c 100644
--- a/pages/doc/en-us/3.1.5/architecture/load-balance.json
+++ b/pages/doc/en-us/3.1.5/architecture/load-balance.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Load Balance"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "DolphinScheduler-Worker Load Balancing Algorithms",
diff --git a/pages/doc/en-us/3.1.5/architecture/metadata.json b/pages/doc/en-us/3.1.5/architecture/metadata.json
index db6235a601..e7f021e3dd 100644
--- a/pages/doc/en-us/3.1.5/architecture/metadata.json
+++ b/pages/doc/en-us/3.1.5/architecture/metadata.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Metadata"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Table Schema",
diff --git a/pages/doc/en-us/3.1.5/architecture/task-structure.json b/pages/doc/en-us/3.1.5/architecture/task-structure.json
index 6f9eb3f992..3fd2bc1f7c 100644
--- a/pages/doc/en-us/3.1.5/architecture/task-structure.json
+++ b/pages/doc/en-us/3.1.5/architecture/task-structure.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Task Structure"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overall Tasks Storage Structure",
diff --git a/pages/doc/en-us/3.1.5/contribute/backend/spi/alert.json b/pages/doc/en-us/3.1.5/contribute/backend/spi/alert.json
index 596bb3a5d3..5ad451132b 100644
--- a/pages/doc/en-us/3.1.5/contribute/backend/spi/alert.json
+++ b/pages/doc/en-us/3.1.5/contribute/backend/spi/alert.json
@@ -5,7 +5,7 @@
"SPI",
"Alert SPI"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "DolphinScheduler Alert SPI main design",
diff --git a/pages/doc/en-us/3.1.5/contribute/backend/spi/datasource.json b/pages/doc/en-us/3.1.5/contribute/backend/spi/datasource.json
index 1a60a67ab7..37ea3c1f97 100644
--- a/pages/doc/en-us/3.1.5/contribute/backend/spi/datasource.json
+++ b/pages/doc/en-us/3.1.5/contribute/backend/spi/datasource.json
@@ -5,7 +5,7 @@
"SPI",
"Datasource SPI"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "DolphinScheduler Datasource SPI main design",
diff --git a/pages/doc/en-us/3.1.5/contribute/backend/spi/registry.json b/pages/doc/en-us/3.1.5/contribute/backend/spi/registry.json
index 8074daa6ad..58af07c206 100644
--- a/pages/doc/en-us/3.1.5/contribute/backend/spi/registry.json
+++ b/pages/doc/en-us/3.1.5/contribute/backend/spi/registry.json
@@ -5,7 +5,7 @@
"SPI",
"Registry SPI"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "DolphinScheduler Registry SPI Extension",
diff --git a/pages/doc/en-us/3.1.5/contribute/backend/spi/task.json b/pages/doc/en-us/3.1.5/contribute/backend/spi/task.json
index 1e3acbd257..fb427c0885 100644
--- a/pages/doc/en-us/3.1.5/contribute/backend/spi/task.json
+++ b/pages/doc/en-us/3.1.5/contribute/backend/spi/task.json
@@ -5,7 +5,7 @@
"SPI",
"Task SPI"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "DolphinScheduler Task SPI extension",
diff --git a/pages/doc/en-us/3.1.5/contribute/development-environment-setup.json b/pages/doc/en-us/3.1.5/contribute/development-environment-setup.json
index 84e79e9612..72b74e7b65 100644
--- a/pages/doc/en-us/3.1.5/contribute/development-environment-setup.json
+++ b/pages/doc/en-us/3.1.5/contribute/development-environment-setup.json
@@ -4,7 +4,7 @@
"Contribution",
"Development Environment Setup"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Software Requirements",
diff --git a/pages/doc/en-us/3.1.5/contribute/frontend-development.json b/pages/doc/en-us/3.1.5/contribute/frontend-development.json
index 09bc1a7706..ac1c8dd6cd 100644
--- a/pages/doc/en-us/3.1.5/contribute/frontend-development.json
+++ b/pages/doc/en-us/3.1.5/contribute/frontend-development.json
@@ -4,7 +4,7 @@
"Contribution",
"Frontend Development"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Routing and state management",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/alert_plugin_user_guide.json b/pages/doc/en-us/3.1.5/guide/alert/alert_plugin_user_guide.json
index d2decb96a0..aad63495fa 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/alert_plugin_user_guide.json
+++ b/pages/doc/en-us/3.1.5/guide/alert/alert_plugin_user_guide.json
@@ -5,7 +5,7 @@
"Alert",
"Alert Component User Guide "
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Alert Plugins and Alert Groups Creation",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/dingtalk.json b/pages/doc/en-us/3.1.5/guide/alert/dingtalk.json
index b1fb9dc335..4817e44507 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/dingtalk.json
+++ b/pages/doc/en-us/3.1.5/guide/alert/dingtalk.json
@@ -5,7 +5,7 @@
"Alert",
"Ding Talk"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/email.json b/pages/doc/en-us/3.1.5/guide/alert/email.json
index cee1cff2bb..0564e1e9bb 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/email.json
+++ b/pages/doc/en-us/3.1.5/guide/alert/email.json
@@ -5,7 +5,7 @@
"Alert",
"Email"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "Email",
"link": "/guide/alert/email"
diff --git a/pages/doc/en-us/3.1.5/guide/alert/enterprise-webexteams.json b/pages/doc/en-us/3.1.5/guide/alert/enterprise-webexteams.json
index 6bb5a16346..17fb44b57a 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/enterprise-webexteams.json
+++ b/pages/doc/en-us/3.1.5/guide/alert/enterprise-webexteams.json
@@ -5,7 +5,7 @@
"Alert",
"Enterprise Webexteams"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/enterprise-wechat.json b/pages/doc/en-us/3.1.5/guide/alert/enterprise-wechat.json
index 121a0ec729..2e19449efa 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/enterprise-wechat.json
+++ b/pages/doc/en-us/3.1.5/guide/alert/enterprise-wechat.json
@@ -5,7 +5,7 @@
"Alert",
"Enterprise Wechat"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Send Type",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/feishu.json b/pages/doc/en-us/3.1.5/guide/alert/feishu.json
index f62c8f371d..a96f36dd11 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/feishu.json
+++ b/pages/doc/en-us/3.1.5/guide/alert/feishu.json
@@ -5,7 +5,7 @@
"Alert",
"Feishu"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/http.json b/pages/doc/en-us/3.1.5/guide/alert/http.json
index beda6656ad..3ce4e84b1a 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/http.json
+++ b/pages/doc/en-us/3.1.5/guide/alert/http.json
@@ -5,7 +5,7 @@
"Alert",
"Http"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/script.json b/pages/doc/en-us/3.1.5/guide/alert/script.json
index 0064dab25b..83e8dc5696 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/script.json
+++ b/pages/doc/en-us/3.1.5/guide/alert/script.json
@@ -5,7 +5,7 @@
"Alert",
"Script"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/telegram.json b/pages/doc/en-us/3.1.5/guide/alert/telegram.json
index 6d3e91332f..8493e2199d 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/telegram.json
+++ b/pages/doc/en-us/3.1.5/guide/alert/telegram.json
@@ -5,7 +5,7 @@
"Alert",
"Telegram"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/api/healthcheck.json b/pages/doc/en-us/3.1.5/guide/api/healthcheck.json
index 8de6cc0d63..d8c19d8a35 100644
--- a/pages/doc/en-us/3.1.5/guide/api/healthcheck.json
+++ b/pages/doc/en-us/3.1.5/guide/api/healthcheck.json
@@ -4,7 +4,7 @@
"API",
"Health Check"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Background",
diff --git a/pages/doc/en-us/3.1.5/guide/api/open-api.json b/pages/doc/en-us/3.1.5/guide/api/open-api.json
index 1a72e50b33..c173cca071 100644
--- a/pages/doc/en-us/3.1.5/guide/api/open-api.json
+++ b/pages/doc/en-us/3.1.5/guide/api/open-api.json
@@ -4,7 +4,7 @@
"API",
"Open API"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Background",
diff --git a/pages/doc/en-us/3.1.5/guide/api/pydolphinscheduler.json b/pages/doc/en-us/3.1.5/guide/api/pydolphinscheduler.json
index d56d313a0d..4e0ce7bea3 100644
--- a/pages/doc/en-us/3.1.5/guide/api/pydolphinscheduler.json
+++ b/pages/doc/en-us/3.1.5/guide/api/pydolphinscheduler.json
@@ -4,7 +4,7 @@
"API",
"PyDolphinScheduler"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "PyDolphinScheduler",
"link": "/guide/api/pydolphinscheduler"
diff --git a/pages/doc/en-us/3.1.5/guide/data-quality.json b/pages/doc/en-us/3.1.5/guide/data-quality.json
index ca9b44116c..457bcc9125 100644
--- a/pages/doc/en-us/3.1.5/guide/data-quality.json
+++ b/pages/doc/en-us/3.1.5/guide/data-quality.json
@@ -4,7 +4,7 @@
"Introduction to Functions",
"Data Quality"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Introduction",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/athena.json b/pages/doc/en-us/3.1.5/guide/datasource/athena.json
index c85539f919..1d8b654b92 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/athena.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/athena.json
@@ -5,7 +5,7 @@
"Data Source",
"Amazon Athena"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/clickhouse.json b/pages/doc/en-us/3.1.5/guide/datasource/clickhouse.json
index bbfdb380bc..00819d8fe0 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/clickhouse.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/clickhouse.json
@@ -5,7 +5,7 @@
"Data Source",
"ClickHouse"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/db2.json b/pages/doc/en-us/3.1.5/guide/datasource/db2.json
index a5f1d5aee5..ba932ee4ee 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/db2.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/db2.json
@@ -5,7 +5,7 @@
"Data Source",
"IBM DB2"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/hive.json b/pages/doc/en-us/3.1.5/guide/datasource/hive.json
index 399e08554d..540d2b0b41 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/hive.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/hive.json
@@ -5,7 +5,7 @@
"Data Source",
"HIVE"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Use HiveServer2",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/mysql.json b/pages/doc/en-us/3.1.5/guide/datasource/mysql.json
index 63466cae41..4bd37c266c 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/mysql.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/mysql.json
@@ -5,7 +5,7 @@
"Data Source",
"MySQL"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/oracle.json b/pages/doc/en-us/3.1.5/guide/datasource/oracle.json
index c63911f76a..e03b08e964 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/oracle.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/oracle.json
@@ -5,7 +5,7 @@
"Data Source",
"Oracle"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/postgresql.json b/pages/doc/en-us/3.1.5/guide/datasource/postgresql.json
index e71e557077..35e503361d 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/postgresql.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/postgresql.json
@@ -5,7 +5,7 @@
"Data Source",
"PostgreSQL"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/presto.json b/pages/doc/en-us/3.1.5/guide/datasource/presto.json
index 4302833a09..b5ab4fbf07 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/presto.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/presto.json
@@ -5,7 +5,7 @@
"Data Source",
"Presto"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/redshift.json b/pages/doc/en-us/3.1.5/guide/datasource/redshift.json
index 84d6cd20b5..3a43967a16 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/redshift.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/redshift.json
@@ -5,7 +5,7 @@
"Data Source",
"Amazon Redshift"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/spark.json b/pages/doc/en-us/3.1.5/guide/datasource/spark.json
index d3324454a0..26989fc7a4 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/spark.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/spark.json
@@ -5,7 +5,7 @@
"Data Source",
"Spark"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/sqlserver.json b/pages/doc/en-us/3.1.5/guide/datasource/sqlserver.json
index 018325dfe5..2a8c9dba7a 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/sqlserver.json
+++ b/pages/doc/en-us/3.1.5/guide/datasource/sqlserver.json
@@ -5,7 +5,7 @@
"Data Source",
"SQL SERVER"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/expansion-reduction.json b/pages/doc/en-us/3.1.5/guide/expansion-reduction.json
index 676311d62e..abe3d14874 100644
--- a/pages/doc/en-us/3.1.5/guide/expansion-reduction.json
+++ b/pages/doc/en-us/3.1.5/guide/expansion-reduction.json
@@ -4,7 +4,7 @@
"Introduction to Functions",
"Expansion and Reduction"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Expansion",
diff --git a/pages/doc/en-us/3.1.5/guide/homepage.json b/pages/doc/en-us/3.1.5/guide/homepage.json
index 4e6f223ee8..57184b6a59 100644
--- a/pages/doc/en-us/3.1.5/guide/homepage.json
+++ b/pages/doc/en-us/3.1.5/guide/homepage.json
@@ -4,7 +4,7 @@
"Introduction to Functions",
"Application Homepage"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "Home Page",
"link": "/guide/homepage"
diff --git a/pages/doc/en-us/3.1.5/guide/installation/cluster.json b/pages/doc/en-us/3.1.5/guide/installation/cluster.json
index e90659ce3e..e7c9ddd303 100644
--- a/pages/doc/en-us/3.1.5/guide/installation/cluster.json
+++ b/pages/doc/en-us/3.1.5/guide/installation/cluster.json
@@ -4,7 +4,7 @@
"Installation",
"Cluster Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Deployment Steps",
diff --git a/pages/doc/en-us/3.1.5/guide/installation/kubernetes.json b/pages/doc/en-us/3.1.5/guide/installation/kubernetes.json
index d1796a9ae6..4d7f036617 100644
--- a/pages/doc/en-us/3.1.5/guide/installation/kubernetes.json
+++ b/pages/doc/en-us/3.1.5/guide/installation/kubernetes.json
@@ -4,7 +4,7 @@
"Installation",
"Kubernetes Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Prerequisites",
diff --git a/pages/doc/en-us/3.1.5/guide/installation/pseudo-cluster.json b/pages/doc/en-us/3.1.5/guide/installation/pseudo-cluster.json
index 7535b47bf2..00392a2bc0 100644
--- a/pages/doc/en-us/3.1.5/guide/installation/pseudo-cluster.json
+++ b/pages/doc/en-us/3.1.5/guide/installation/pseudo-cluster.json
@@ -4,7 +4,7 @@
"Installation",
"Pseudo Cluster Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Preparation",
diff --git a/pages/doc/en-us/3.1.5/guide/installation/standalone.json b/pages/doc/en-us/3.1.5/guide/installation/standalone.json
index 6153e83ffb..769f8a9bbe 100644
--- a/pages/doc/en-us/3.1.5/guide/installation/standalone.json
+++ b/pages/doc/en-us/3.1.5/guide/installation/standalone.json
@@ -4,7 +4,7 @@
"Installation",
"Standalone Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Preparation",
diff --git a/pages/doc/en-us/3.1.5/guide/integration/rainbond.json b/pages/doc/en-us/3.1.5/guide/integration/rainbond.json
index 499d3afa17..245354a8a2 100644
--- a/pages/doc/en-us/3.1.5/guide/integration/rainbond.json
+++ b/pages/doc/en-us/3.1.5/guide/integration/rainbond.json
@@ -5,7 +5,7 @@
"integration",
"Rainbond Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Prerequisites",
diff --git a/pages/doc/en-us/3.1.5/guide/metrics/metrics.json b/pages/doc/en-us/3.1.5/guide/metrics/metrics.json
index 7d42e7c321..6233cab859 100644
--- a/pages/doc/en-us/3.1.5/guide/metrics/metrics.json
+++ b/pages/doc/en-us/3.1.5/guide/metrics/metrics.json
@@ -5,7 +5,7 @@
"Metrics",
"Metrics"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Quick Start",
diff --git a/pages/doc/en-us/3.1.5/guide/monitor.json b/pages/doc/en-us/3.1.5/guide/monitor.json
index 3c0e4feae0..0388071b0d 100644
--- a/pages/doc/en-us/3.1.5/guide/monitor.json
+++ b/pages/doc/en-us/3.1.5/guide/monitor.json
@@ -4,7 +4,7 @@
"Introduction to Functions",
"Monitor"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Service Management",
diff --git a/pages/doc/en-us/3.1.5/guide/parameter/built-in.json b/pages/doc/en-us/3.1.5/guide/parameter/built-in.json
index 31bd8e25aa..cd8a1ebe2c 100644
--- a/pages/doc/en-us/3.1.5/guide/parameter/built-in.json
+++ b/pages/doc/en-us/3.1.5/guide/parameter/built-in.json
@@ -5,7 +5,7 @@
"Parameter",
"Built-in Parameter"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Basic Built-in Parameter",
diff --git a/pages/doc/en-us/3.1.5/guide/parameter/context.json b/pages/doc/en-us/3.1.5/guide/parameter/context.json
index 7fe1f5df03..1724d51941 100644
--- a/pages/doc/en-us/3.1.5/guide/parameter/context.json
+++ b/pages/doc/en-us/3.1.5/guide/parameter/context.json
@@ -5,7 +5,7 @@
"Parameter",
"Parameter Context"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Local Task Refers to Global Parameter",
diff --git a/pages/doc/en-us/3.1.5/guide/parameter/global.json b/pages/doc/en-us/3.1.5/guide/parameter/global.json
index f505c6e3ce..0ee3be70c2 100644
--- a/pages/doc/en-us/3.1.5/guide/parameter/global.json
+++ b/pages/doc/en-us/3.1.5/guide/parameter/global.json
@@ -5,7 +5,7 @@
"Parameter",
"Global Parameter"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Scope",
diff --git a/pages/doc/en-us/3.1.5/guide/parameter/local.json b/pages/doc/en-us/3.1.5/guide/parameter/local.json
index 998f102565..c3a621e54a 100644
--- a/pages/doc/en-us/3.1.5/guide/parameter/local.json
+++ b/pages/doc/en-us/3.1.5/guide/parameter/local.json
@@ -5,7 +5,7 @@
"Parameter",
"Local Parameter"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Scope",
diff --git a/pages/doc/en-us/3.1.5/guide/parameter/priority.json b/pages/doc/en-us/3.1.5/guide/parameter/priority.json
index d4a8415114..cad5675324 100644
--- a/pages/doc/en-us/3.1.5/guide/parameter/priority.json
+++ b/pages/doc/en-us/3.1.5/guide/parameter/priority.json
@@ -5,7 +5,7 @@
"Parameter",
"Parameter Priority"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Example",
diff --git a/pages/doc/en-us/3.1.5/guide/project/project-list.json b/pages/doc/en-us/3.1.5/guide/project/project-list.json
index 04d4f238a2..154f82f70d 100644
--- a/pages/doc/en-us/3.1.5/guide/project/project-list.json
+++ b/pages/doc/en-us/3.1.5/guide/project/project-list.json
@@ -5,7 +5,7 @@
"Project",
"Project List"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Project List",
diff --git a/pages/doc/en-us/3.1.5/guide/project/task-definition.json b/pages/doc/en-us/3.1.5/guide/project/task-definition.json
index bee9a5f9d1..d1c6e1c857 100644
--- a/pages/doc/en-us/3.1.5/guide/project/task-definition.json
+++ b/pages/doc/en-us/3.1.5/guide/project/task-definition.json
@@ -5,7 +5,7 @@
"Project",
"Task Definition"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Batch Task Definition",
diff --git a/pages/doc/en-us/3.1.5/guide/project/task-instance.json b/pages/doc/en-us/3.1.5/guide/project/task-instance.json
index 7c644b115f..5912509cbb 100644
--- a/pages/doc/en-us/3.1.5/guide/project/task-instance.json
+++ b/pages/doc/en-us/3.1.5/guide/project/task-instance.json
@@ -5,7 +5,7 @@
"Project",
"Task Instance"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Batch Task Instance",
diff --git a/pages/doc/en-us/3.1.5/guide/project/workflow-definition.json b/pages/doc/en-us/3.1.5/guide/project/workflow-definition.json
index 806f6abdeb..8330de898b 100644
--- a/pages/doc/en-us/3.1.5/guide/project/workflow-definition.json
+++ b/pages/doc/en-us/3.1.5/guide/project/workflow-definition.json
@@ -5,7 +5,7 @@
"Project",
"Workflow Definition"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/project/workflow-instance.json b/pages/doc/en-us/3.1.5/guide/project/workflow-instance.json
index c8268564da..10d05e7c3d 100644
--- a/pages/doc/en-us/3.1.5/guide/project/workflow-instance.json
+++ b/pages/doc/en-us/3.1.5/guide/project/workflow-instance.json
@@ -5,7 +5,7 @@
"Project",
"Workflow Instance"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "View Workflow Instance",
diff --git a/pages/doc/en-us/3.1.5/guide/resource/configuration.json b/pages/doc/en-us/3.1.5/guide/resource/configuration.json
index 006eefdb99..b02a727150 100644
--- a/pages/doc/en-us/3.1.5/guide/resource/configuration.json
+++ b/pages/doc/en-us/3.1.5/guide/resource/configuration.json
@@ -5,7 +5,7 @@
"Resource",
"Configuration"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Use Local File System",
diff --git a/pages/doc/en-us/3.1.5/guide/resource/file-manage.json b/pages/doc/en-us/3.1.5/guide/resource/file-manage.json
index db5b61a486..d3b7ba7f8d 100644
--- a/pages/doc/en-us/3.1.5/guide/resource/file-manage.json
+++ b/pages/doc/en-us/3.1.5/guide/resource/file-manage.json
@@ -5,7 +5,7 @@
"Resource",
"File Manage"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Basic Operations",
diff --git a/pages/doc/en-us/3.1.5/guide/resource/intro.json b/pages/doc/en-us/3.1.5/guide/resource/intro.json
index 751d9a961d..db0e773963 100644
--- a/pages/doc/en-us/3.1.5/guide/resource/intro.json
+++ b/pages/doc/en-us/3.1.5/guide/resource/intro.json
@@ -5,7 +5,7 @@
"Resource",
"Introduction"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "Resource Center Introduction",
"link": "/guide/resource/intro"
diff --git a/pages/doc/en-us/3.1.5/guide/resource/task-group.json b/pages/doc/en-us/3.1.5/guide/resource/task-group.json
index f7fe9c81fd..519862e17b 100644
--- a/pages/doc/en-us/3.1.5/guide/resource/task-group.json
+++ b/pages/doc/en-us/3.1.5/guide/resource/task-group.json
@@ -5,7 +5,7 @@
"Resource",
"Task Group Manage"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Task Group Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/resource/udf-manage.json b/pages/doc/en-us/3.1.5/guide/resource/udf-manage.json
index cd4644334e..0c087ac321 100644
--- a/pages/doc/en-us/3.1.5/guide/resource/udf-manage.json
+++ b/pages/doc/en-us/3.1.5/guide/resource/udf-manage.json
@@ -5,7 +5,7 @@
"Resource",
"UDF Manage"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Resource Management",
diff --git a/pages/doc/en-us/3.1.5/guide/security.json b/pages/doc/en-us/3.1.5/guide/security.json
index 06241cb3ad..6666517a2b 100644
--- a/pages/doc/en-us/3.1.5/guide/security.json
+++ b/pages/doc/en-us/3.1.5/guide/security.json
@@ -4,7 +4,7 @@
"Introduction to Functions",
"Security"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Create Queue",
diff --git a/pages/doc/en-us/3.1.5/guide/start/docker.json b/pages/doc/en-us/3.1.5/guide/start/docker.json
index 72c49f1b11..0fb3a5189d 100644
--- a/pages/doc/en-us/3.1.5/guide/start/docker.json
+++ b/pages/doc/en-us/3.1.5/guide/start/docker.json
@@ -4,7 +4,7 @@
"Quick Start",
"Docker Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Prepare",
diff --git a/pages/doc/en-us/3.1.5/guide/start/quick-start.json b/pages/doc/en-us/3.1.5/guide/start/quick-start.json
index cf999da0e7..3be867ff3b 100644
--- a/pages/doc/en-us/3.1.5/guide/start/quick-start.json
+++ b/pages/doc/en-us/3.1.5/guide/start/quick-start.json
@@ -4,7 +4,7 @@
"Quick Start",
"Quick Start"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Administrator User Login",
diff --git a/pages/doc/en-us/3.1.5/guide/task/appendix.json b/pages/doc/en-us/3.1.5/guide/task/appendix.json
index 865b715a49..ed98f49549 100644
--- a/pages/doc/en-us/3.1.5/guide/task/appendix.json
+++ b/pages/doc/en-us/3.1.5/guide/task/appendix.json
@@ -5,7 +5,7 @@
"Task",
"Appendix"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Default Task Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/task/chunjun.json b/pages/doc/en-us/3.1.5/guide/task/chunjun.json
index 2f62f553db..36454f62c4 100644
--- a/pages/doc/en-us/3.1.5/guide/task/chunjun.json
+++ b/pages/doc/en-us/3.1.5/guide/task/chunjun.json
@@ -5,7 +5,7 @@
"Task",
"ChunJun"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/conditions.json b/pages/doc/en-us/3.1.5/guide/task/conditions.json
index cb5ffe8baa..bbb7199f7e 100644
--- a/pages/doc/en-us/3.1.5/guide/task/conditions.json
+++ b/pages/doc/en-us/3.1.5/guide/task/conditions.json
@@ -5,7 +5,7 @@
"Task",
"Conditions"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Create Task",
diff --git a/pages/doc/en-us/3.1.5/guide/task/datax.json b/pages/doc/en-us/3.1.5/guide/task/datax.json
index 7d3506085c..c760613058 100644
--- a/pages/doc/en-us/3.1.5/guide/task/datax.json
+++ b/pages/doc/en-us/3.1.5/guide/task/datax.json
@@ -5,7 +5,7 @@
"Task",
"DataX"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/dependent.json b/pages/doc/en-us/3.1.5/guide/task/dependent.json
index 3600a1b96f..11f18e25f9 100644
--- a/pages/doc/en-us/3.1.5/guide/task/dependent.json
+++ b/pages/doc/en-us/3.1.5/guide/task/dependent.json
@@ -5,7 +5,7 @@
"Task",
"Dependent"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/dinky.json b/pages/doc/en-us/3.1.5/guide/task/dinky.json
index f9a65431a8..bbfea7393c 100644
--- a/pages/doc/en-us/3.1.5/guide/task/dinky.json
+++ b/pages/doc/en-us/3.1.5/guide/task/dinky.json
@@ -5,7 +5,7 @@
"Task",
"Dinky"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/dvc.json b/pages/doc/en-us/3.1.5/guide/task/dvc.json
index 3fc089a86f..cd4ce289bf 100644
--- a/pages/doc/en-us/3.1.5/guide/task/dvc.json
+++ b/pages/doc/en-us/3.1.5/guide/task/dvc.json
@@ -5,7 +5,7 @@
"Task",
"DVC"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/emr.json b/pages/doc/en-us/3.1.5/guide/task/emr.json
index b75365124c..0e4abf80e2 100644
--- a/pages/doc/en-us/3.1.5/guide/task/emr.json
+++ b/pages/doc/en-us/3.1.5/guide/task/emr.json
@@ -5,7 +5,7 @@
"Task",
"Amazon EMR"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/flink.json b/pages/doc/en-us/3.1.5/guide/task/flink.json
index d99ae187a5..c45c43805f 100644
--- a/pages/doc/en-us/3.1.5/guide/task/flink.json
+++ b/pages/doc/en-us/3.1.5/guide/task/flink.json
@@ -5,7 +5,7 @@
"Task",
"Flink"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/hive-cli.json b/pages/doc/en-us/3.1.5/guide/task/hive-cli.json
index f0b371112d..e27b0cff6b 100644
--- a/pages/doc/en-us/3.1.5/guide/task/hive-cli.json
+++ b/pages/doc/en-us/3.1.5/guide/task/hive-cli.json
@@ -5,7 +5,7 @@
"Task",
"Hive CLI"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/http.json b/pages/doc/en-us/3.1.5/guide/task/http.json
index d693b91308..296c9f580a 100644
--- a/pages/doc/en-us/3.1.5/guide/task/http.json
+++ b/pages/doc/en-us/3.1.5/guide/task/http.json
@@ -5,7 +5,7 @@
"Task",
"HTTP"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/jupyter.json b/pages/doc/en-us/3.1.5/guide/task/jupyter.json
index 476547cd7d..5a0bfab467 100644
--- a/pages/doc/en-us/3.1.5/guide/task/jupyter.json
+++ b/pages/doc/en-us/3.1.5/guide/task/jupyter.json
@@ -5,7 +5,7 @@
"Task",
"Jupyter"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/kubernetes.json b/pages/doc/en-us/3.1.5/guide/task/kubernetes.json
index 0cfa574f14..dab6413368 100644
--- a/pages/doc/en-us/3.1.5/guide/task/kubernetes.json
+++ b/pages/doc/en-us/3.1.5/guide/task/kubernetes.json
@@ -5,7 +5,7 @@
"Task",
"Kubernetes"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/map-reduce.json b/pages/doc/en-us/3.1.5/guide/task/map-reduce.json
index 393094ec4b..ee2a3349e4 100644
--- a/pages/doc/en-us/3.1.5/guide/task/map-reduce.json
+++ b/pages/doc/en-us/3.1.5/guide/task/map-reduce.json
@@ -5,7 +5,7 @@
"Task",
"MapReduce"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/mlflow.json b/pages/doc/en-us/3.1.5/guide/task/mlflow.json
index d60f23c5eb..7164de1d5b 100644
--- a/pages/doc/en-us/3.1.5/guide/task/mlflow.json
+++ b/pages/doc/en-us/3.1.5/guide/task/mlflow.json
@@ -5,7 +5,7 @@
"Task",
"MLflow"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/openmldb.json b/pages/doc/en-us/3.1.5/guide/task/openmldb.json
index 0e78a5041d..9c0c1b117e 100644
--- a/pages/doc/en-us/3.1.5/guide/task/openmldb.json
+++ b/pages/doc/en-us/3.1.5/guide/task/openmldb.json
@@ -5,7 +5,7 @@
"Task",
"Openmldb"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/pigeon.json b/pages/doc/en-us/3.1.5/guide/task/pigeon.json
index e2d1c52fb5..d4d06876b4 100644
--- a/pages/doc/en-us/3.1.5/guide/task/pigeon.json
+++ b/pages/doc/en-us/3.1.5/guide/task/pigeon.json
@@ -5,7 +5,7 @@
"Task",
"Pigeon"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/python.json b/pages/doc/en-us/3.1.5/guide/task/python.json
index 39b79f302b..26b2ce6f11 100644
--- a/pages/doc/en-us/3.1.5/guide/task/python.json
+++ b/pages/doc/en-us/3.1.5/guide/task/python.json
@@ -5,7 +5,7 @@
"Task",
"Python"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/pytorch.json b/pages/doc/en-us/3.1.5/guide/task/pytorch.json
index b9681ba582..ab0b02e9f9 100644
--- a/pages/doc/en-us/3.1.5/guide/task/pytorch.json
+++ b/pages/doc/en-us/3.1.5/guide/task/pytorch.json
@@ -5,7 +5,7 @@
"Task",
"Pytorch"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/sagemaker.json b/pages/doc/en-us/3.1.5/guide/task/sagemaker.json
index 0f860bf2e6..fc244d2da4 100644
--- a/pages/doc/en-us/3.1.5/guide/task/sagemaker.json
+++ b/pages/doc/en-us/3.1.5/guide/task/sagemaker.json
@@ -5,7 +5,7 @@
"Task",
"SageMaker"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/seatunnel.json b/pages/doc/en-us/3.1.5/guide/task/seatunnel.json
index ccfdb71a2b..ebaa63966f 100644
--- a/pages/doc/en-us/3.1.5/guide/task/seatunnel.json
+++ b/pages/doc/en-us/3.1.5/guide/task/seatunnel.json
@@ -5,7 +5,7 @@
"Task",
"SeaTunnel"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/shell.json b/pages/doc/en-us/3.1.5/guide/task/shell.json
index 55dc1888b1..2aeb6483f4 100644
--- a/pages/doc/en-us/3.1.5/guide/task/shell.json
+++ b/pages/doc/en-us/3.1.5/guide/task/shell.json
@@ -5,7 +5,7 @@
"Task",
"Shell"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/spark.json b/pages/doc/en-us/3.1.5/guide/task/spark.json
index 4bf650a4ad..6eee0af2f2 100644
--- a/pages/doc/en-us/3.1.5/guide/task/spark.json
+++ b/pages/doc/en-us/3.1.5/guide/task/spark.json
@@ -5,7 +5,7 @@
"Task",
"Spark"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/sql.json b/pages/doc/en-us/3.1.5/guide/task/sql.json
index 9d4c306c94..49b32c0eb6 100644
--- a/pages/doc/en-us/3.1.5/guide/task/sql.json
+++ b/pages/doc/en-us/3.1.5/guide/task/sql.json
@@ -5,7 +5,7 @@
"Task",
"SQL"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/stored-procedure.json b/pages/doc/en-us/3.1.5/guide/task/stored-procedure.json
index d71b0a2546..842a214e11 100644
--- a/pages/doc/en-us/3.1.5/guide/task/stored-procedure.json
+++ b/pages/doc/en-us/3.1.5/guide/task/stored-procedure.json
@@ -5,7 +5,7 @@
"Task",
"Stored Procedure"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Task Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/task/sub-process.json b/pages/doc/en-us/3.1.5/guide/task/sub-process.json
index dfb9cf337f..6840120d77 100644
--- a/pages/doc/en-us/3.1.5/guide/task/sub-process.json
+++ b/pages/doc/en-us/3.1.5/guide/task/sub-process.json
@@ -5,7 +5,7 @@
"Task",
"SubProcess"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/switch.json b/pages/doc/en-us/3.1.5/guide/task/switch.json
index daa9287f2b..ecb4f8dd53 100644
--- a/pages/doc/en-us/3.1.5/guide/task/switch.json
+++ b/pages/doc/en-us/3.1.5/guide/task/switch.json
@@ -5,7 +5,7 @@
"Task",
"Switch"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/zeppelin.json b/pages/doc/en-us/3.1.5/guide/task/zeppelin.json
index a3f27f6ec1..baef8eae05 100644
--- a/pages/doc/en-us/3.1.5/guide/task/zeppelin.json
+++ b/pages/doc/en-us/3.1.5/guide/task/zeppelin.json
@@ -5,7 +5,7 @@
"Task",
"Apache Zeppelin"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/upgrade/incompatible.json b/pages/doc/en-us/3.1.5/guide/upgrade/incompatible.json
index d863832edb..9f75ef0665 100644
--- a/pages/doc/en-us/3.1.5/guide/upgrade/incompatible.json
+++ b/pages/doc/en-us/3.1.5/guide/upgrade/incompatible.json
@@ -5,7 +5,7 @@
"Upgrade",
"Incompatible"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "dev",
diff --git a/pages/doc/en-us/3.1.5/guide/upgrade/upgrade.json b/pages/doc/en-us/3.1.5/guide/upgrade/upgrade.json
index b39c8e69c0..3753c1c1b6 100644
--- a/pages/doc/en-us/3.1.5/guide/upgrade/upgrade.json
+++ b/pages/doc/en-us/3.1.5/guide/upgrade/upgrade.json
@@ -5,7 +5,7 @@
"Upgrade",
"Upgrade"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Prepare",
diff --git a/pages/doc/en-us/3.1.5/DSIP.json b/pages/doc/en-us/3.1.6/DSIP.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/DSIP.json
copy to pages/doc/en-us/3.1.6/DSIP.json
index b60cbe5c28..cc9a2485f1 100644
--- a/pages/doc/en-us/3.1.5/DSIP.json
+++ b/pages/doc/en-us/3.1.6/DSIP.json
@@ -4,7 +4,7 @@
"DSIP",
"DSIP"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "What is considered as DSIP",
diff --git a/pages/doc/en-us/3.1.5/about/features.json b/pages/doc/en-us/3.1.6/about/features.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/about/features.json
copy to pages/doc/en-us/3.1.6/about/features.json
index 5e3f81d377..727373e458 100644
--- a/pages/doc/en-us/3.1.5/about/features.json
+++ b/pages/doc/en-us/3.1.6/about/features.json
@@ -4,7 +4,7 @@
"About",
"Features"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Simple to Use",
diff --git a/pages/doc/en-us/3.1.5/about/glossary.json b/pages/doc/en-us/3.1.6/about/glossary.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/about/glossary.json
copy to pages/doc/en-us/3.1.6/about/glossary.json
index e91bf8cdce..f721764624 100644
--- a/pages/doc/en-us/3.1.5/about/glossary.json
+++ b/pages/doc/en-us/3.1.6/about/glossary.json
@@ -4,7 +4,7 @@
"About",
"Glossary"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "System Architecture Design",
diff --git a/pages/doc/en-us/3.1.5/about/hardware.json b/pages/doc/en-us/3.1.6/about/hardware.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/about/hardware.json
copy to pages/doc/en-us/3.1.6/about/hardware.json
index 1b3dadfb27..e417d292c4 100644
--- a/pages/doc/en-us/3.1.5/about/hardware.json
+++ b/pages/doc/en-us/3.1.6/about/hardware.json
@@ -4,7 +4,7 @@
"About",
"Hardware Environment"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Linux Operating System Version Requirements",
diff --git a/pages/doc/en-us/3.1.5/about/introduction.json b/pages/doc/en-us/3.1.6/about/introduction.json
similarity index 97%
copy from pages/doc/en-us/3.1.5/about/introduction.json
copy to pages/doc/en-us/3.1.6/about/introduction.json
index 1f4bf0277d..896bdf9759 100644
--- a/pages/doc/en-us/3.1.5/about/introduction.json
+++ b/pages/doc/en-us/3.1.6/about/introduction.json
@@ -4,7 +4,7 @@
"About",
"Introduction"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [],
"title": "About DolphinScheduler",
"link": "/about/introduction"
diff --git a/pages/doc/en-us/3.1.5/architecture/cache.json b/pages/doc/en-us/3.1.6/architecture/cache.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/architecture/cache.json
copy to pages/doc/en-us/3.1.6/architecture/cache.json
index dcbe07ba08..80cc3f72ef 100644
--- a/pages/doc/en-us/3.1.5/architecture/cache.json
+++ b/pages/doc/en-us/3.1.6/architecture/cache.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Cache"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Purpose",
diff --git a/pages/doc/en-us/3.1.5/architecture/configuration.json b/pages/doc/en-us/3.1.6/architecture/configuration.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/architecture/configuration.json
copy to pages/doc/en-us/3.1.6/architecture/configuration.json
index da186e8a45..0f25e22f5b 100644
--- a/pages/doc/en-us/3.1.5/architecture/configuration.json
+++ b/pages/doc/en-us/3.1.6/architecture/configuration.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Configuration File"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Preface",
diff --git a/pages/doc/en-us/3.1.5/architecture/design.json b/pages/doc/en-us/3.1.6/architecture/design.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/architecture/design.json
copy to pages/doc/en-us/3.1.6/architecture/design.json
index bfba9c6038..2897b287ef 100644
--- a/pages/doc/en-us/3.1.5/architecture/design.json
+++ b/pages/doc/en-us/3.1.6/architecture/design.json
@@ -1,10 +1,10 @@
{
- "__html": "<h1 id=\"system-architecture-design\">System Architecture Design</h1>\n<h2 id=\"system-structure\">System Structure</h2>\n<h3 id=\"system-architecture-diagram\">System Architecture Diagram</h3>\n<p align=\"center\">\n <img src=\"/img/architecture-1.3.0.jpg\" alt=\"System architecture diagram\" width=\"70%\" />\n <p align=\"center\">\n <em>System architecture diagram</em>\n </p>\n</p>\n<h3 id=\"start-process-activity-diagram\">Start Process Activity Diagram</h3>\n< [...]
+ "__html": "<h1 id=\"system-architecture-design\">System Architecture Design</h1>\n<h2 id=\"system-structure\">System Structure</h2>\n<h3 id=\"system-architecture-diagram\">System Architecture Diagram</h3>\n<p align=\"center\">\n <img src=\"/img/architecture-1.3.0.jpg\" alt=\"System architecture diagram\" width=\"70%\" />\n <p align=\"center\">\n <em>System architecture diagram</em>\n </p>\n</p>\n<h3 id=\"start-process-activity-diagram\">Start Process Activity Diagram</h3>\n< [...]
"location": [
"Architecture Guide",
"Architecture Design"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "System Structure",
diff --git a/pages/doc/en-us/3.1.5/architecture/load-balance.json b/pages/doc/en-us/3.1.6/architecture/load-balance.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/architecture/load-balance.json
copy to pages/doc/en-us/3.1.6/architecture/load-balance.json
index e3905bcc4e..b9a9212876 100644
--- a/pages/doc/en-us/3.1.5/architecture/load-balance.json
+++ b/pages/doc/en-us/3.1.6/architecture/load-balance.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Load Balance"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "DolphinScheduler-Worker Load Balancing Algorithms",
diff --git a/pages/doc/en-us/3.1.5/architecture/metadata.json b/pages/doc/en-us/3.1.6/architecture/metadata.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/architecture/metadata.json
copy to pages/doc/en-us/3.1.6/architecture/metadata.json
index db6235a601..2d2697e98a 100644
--- a/pages/doc/en-us/3.1.5/architecture/metadata.json
+++ b/pages/doc/en-us/3.1.6/architecture/metadata.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Metadata"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Table Schema",
diff --git a/pages/doc/en-us/3.1.5/architecture/task-structure.json b/pages/doc/en-us/3.1.6/architecture/task-structure.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/architecture/task-structure.json
copy to pages/doc/en-us/3.1.6/architecture/task-structure.json
index 6f9eb3f992..f44cef4cda 100644
--- a/pages/doc/en-us/3.1.5/architecture/task-structure.json
+++ b/pages/doc/en-us/3.1.6/architecture/task-structure.json
@@ -4,7 +4,7 @@
"Architecture Guide",
"Task Structure"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overall Tasks Storage Structure",
diff --git a/pages/doc/en-us/3.1.5/contribute/backend/spi/alert.json b/pages/doc/en-us/3.1.6/contribute/backend/spi/alert.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/contribute/backend/spi/alert.json
copy to pages/doc/en-us/3.1.6/contribute/backend/spi/alert.json
index 596bb3a5d3..50ab3c0e09 100644
--- a/pages/doc/en-us/3.1.5/contribute/backend/spi/alert.json
+++ b/pages/doc/en-us/3.1.6/contribute/backend/spi/alert.json
@@ -5,7 +5,7 @@
"SPI",
"Alert SPI"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "DolphinScheduler Alert SPI main design",
diff --git a/pages/doc/en-us/3.1.5/contribute/backend/spi/datasource.json b/pages/doc/en-us/3.1.6/contribute/backend/spi/datasource.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/contribute/backend/spi/datasource.json
copy to pages/doc/en-us/3.1.6/contribute/backend/spi/datasource.json
index 1a60a67ab7..8f44e0ad32 100644
--- a/pages/doc/en-us/3.1.5/contribute/backend/spi/datasource.json
+++ b/pages/doc/en-us/3.1.6/contribute/backend/spi/datasource.json
@@ -5,7 +5,7 @@
"SPI",
"Datasource SPI"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "DolphinScheduler Datasource SPI main design",
diff --git a/pages/doc/en-us/3.1.5/contribute/backend/spi/registry.json b/pages/doc/en-us/3.1.6/contribute/backend/spi/registry.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/contribute/backend/spi/registry.json
copy to pages/doc/en-us/3.1.6/contribute/backend/spi/registry.json
index 8074daa6ad..46adc8b878 100644
--- a/pages/doc/en-us/3.1.5/contribute/backend/spi/registry.json
+++ b/pages/doc/en-us/3.1.6/contribute/backend/spi/registry.json
@@ -5,7 +5,7 @@
"SPI",
"Registry SPI"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "DolphinScheduler Registry SPI Extension",
diff --git a/pages/doc/en-us/3.1.5/contribute/backend/spi/task.json b/pages/doc/en-us/3.1.6/contribute/backend/spi/task.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/contribute/backend/spi/task.json
copy to pages/doc/en-us/3.1.6/contribute/backend/spi/task.json
index 1e3acbd257..e87f1686a3 100644
--- a/pages/doc/en-us/3.1.5/contribute/backend/spi/task.json
+++ b/pages/doc/en-us/3.1.6/contribute/backend/spi/task.json
@@ -5,7 +5,7 @@
"SPI",
"Task SPI"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "DolphinScheduler Task SPI extension",
diff --git a/pages/doc/en-us/3.1.5/contribute/development-environment-setup.json b/pages/doc/en-us/3.1.6/contribute/development-environment-setup.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/contribute/development-environment-setup.json
copy to pages/doc/en-us/3.1.6/contribute/development-environment-setup.json
index 84e79e9612..9f2225ae85 100644
--- a/pages/doc/en-us/3.1.5/contribute/development-environment-setup.json
+++ b/pages/doc/en-us/3.1.6/contribute/development-environment-setup.json
@@ -1,10 +1,10 @@
{
- "__html": "<h1 id=\"dolphinscheduler-development\">DolphinScheduler development</h1>\n<h2 id=\"software-requirements\">Software Requirements</h2>\n<p>Before setting up the DolphinScheduler development environment, please make sure you have installed the software as below:</p>\n<ul>\n<li><a href=\"https://git-scm.com/downloads\">Git</a></li>\n<li><a href=\"https://www.oracle.com/technetwork/java/javase/downloads/index.html\">JDK</a>: v1.8.x (Currently does not support jdk 11)</li>\n<li> [...]
+ "__html": "<h1 id=\"dolphinscheduler-development\">DolphinScheduler development</h1>\n<h2 id=\"software-requirements\">Software Requirements</h2>\n<p>Before setting up the DolphinScheduler development environment, please make sure you have installed the software as below:</p>\n<ul>\n<li><a href=\"https://git-scm.com/downloads\">Git</a></li>\n<li><a href=\"https://www.oracle.com/technetwork/java/javase/downloads/index.html\">JDK</a>: v1.8.x (Currently does not support jdk 11)</li>\n<li> [...]
"location": [
"Contribution",
"Development Environment Setup"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Software Requirements",
diff --git a/pages/doc/en-us/3.1.5/contribute/frontend-development.json b/pages/doc/en-us/3.1.6/contribute/frontend-development.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/contribute/frontend-development.json
copy to pages/doc/en-us/3.1.6/contribute/frontend-development.json
index 09bc1a7706..8f1db78840 100644
--- a/pages/doc/en-us/3.1.5/contribute/frontend-development.json
+++ b/pages/doc/en-us/3.1.6/contribute/frontend-development.json
@@ -4,7 +4,7 @@
"Contribution",
"Frontend Development"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Routing and state management",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/alert_plugin_user_guide.json b/pages/doc/en-us/3.1.6/guide/alert/alert_plugin_user_guide.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/alert/alert_plugin_user_guide.json
copy to pages/doc/en-us/3.1.6/guide/alert/alert_plugin_user_guide.json
index d2decb96a0..4f0089c64d 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/alert_plugin_user_guide.json
+++ b/pages/doc/en-us/3.1.6/guide/alert/alert_plugin_user_guide.json
@@ -5,7 +5,7 @@
"Alert",
"Alert Component User Guide "
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Alert Plugins and Alert Groups Creation",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/dingtalk.json b/pages/doc/en-us/3.1.6/guide/alert/dingtalk.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/alert/dingtalk.json
copy to pages/doc/en-us/3.1.6/guide/alert/dingtalk.json
index b1fb9dc335..06e440a375 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/dingtalk.json
+++ b/pages/doc/en-us/3.1.6/guide/alert/dingtalk.json
@@ -5,7 +5,7 @@
"Alert",
"Ding Talk"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/email.json b/pages/doc/en-us/3.1.6/guide/alert/email.json
similarity index 96%
copy from pages/doc/en-us/3.1.5/guide/alert/email.json
copy to pages/doc/en-us/3.1.6/guide/alert/email.json
index cee1cff2bb..619b11c80c 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/email.json
+++ b/pages/doc/en-us/3.1.6/guide/alert/email.json
@@ -5,7 +5,7 @@
"Alert",
"Email"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [],
"title": "Email",
"link": "/guide/alert/email"
diff --git a/pages/doc/en-us/3.1.5/guide/alert/enterprise-webexteams.json b/pages/doc/en-us/3.1.6/guide/alert/enterprise-webexteams.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/alert/enterprise-webexteams.json
copy to pages/doc/en-us/3.1.6/guide/alert/enterprise-webexteams.json
index 6bb5a16346..9eff3e401a 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/enterprise-webexteams.json
+++ b/pages/doc/en-us/3.1.6/guide/alert/enterprise-webexteams.json
@@ -5,7 +5,7 @@
"Alert",
"Enterprise Webexteams"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/enterprise-wechat.json b/pages/doc/en-us/3.1.6/guide/alert/enterprise-wechat.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/alert/enterprise-wechat.json
copy to pages/doc/en-us/3.1.6/guide/alert/enterprise-wechat.json
index 121a0ec729..423ff0244c 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/enterprise-wechat.json
+++ b/pages/doc/en-us/3.1.6/guide/alert/enterprise-wechat.json
@@ -5,7 +5,7 @@
"Alert",
"Enterprise Wechat"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Send Type",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/feishu.json b/pages/doc/en-us/3.1.6/guide/alert/feishu.json
similarity index 97%
copy from pages/doc/en-us/3.1.5/guide/alert/feishu.json
copy to pages/doc/en-us/3.1.6/guide/alert/feishu.json
index f62c8f371d..f939a0a6b3 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/feishu.json
+++ b/pages/doc/en-us/3.1.6/guide/alert/feishu.json
@@ -5,7 +5,7 @@
"Alert",
"Feishu"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/http.json b/pages/doc/en-us/3.1.6/guide/alert/http.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/alert/http.json
copy to pages/doc/en-us/3.1.6/guide/alert/http.json
index beda6656ad..4ba9793ab9 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/http.json
+++ b/pages/doc/en-us/3.1.6/guide/alert/http.json
@@ -5,7 +5,7 @@
"Alert",
"Http"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/script.json b/pages/doc/en-us/3.1.6/guide/alert/script.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/alert/script.json
copy to pages/doc/en-us/3.1.6/guide/alert/script.json
index 0064dab25b..77aa411c3e 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/script.json
+++ b/pages/doc/en-us/3.1.6/guide/alert/script.json
@@ -5,7 +5,7 @@
"Alert",
"Script"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/alert/telegram.json b/pages/doc/en-us/3.1.6/guide/alert/telegram.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/alert/telegram.json
copy to pages/doc/en-us/3.1.6/guide/alert/telegram.json
index 6d3e91332f..1d5b1bd9a0 100644
--- a/pages/doc/en-us/3.1.5/guide/alert/telegram.json
+++ b/pages/doc/en-us/3.1.6/guide/alert/telegram.json
@@ -5,7 +5,7 @@
"Alert",
"Telegram"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Parameter Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/api/healthcheck.json b/pages/doc/en-us/3.1.6/guide/api/healthcheck.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/api/healthcheck.json
copy to pages/doc/en-us/3.1.6/guide/api/healthcheck.json
index 8de6cc0d63..547afeb023 100644
--- a/pages/doc/en-us/3.1.5/guide/api/healthcheck.json
+++ b/pages/doc/en-us/3.1.6/guide/api/healthcheck.json
@@ -4,7 +4,7 @@
"API",
"Health Check"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Background",
diff --git a/pages/doc/en-us/3.1.5/guide/api/open-api.json b/pages/doc/en-us/3.1.6/guide/api/open-api.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/api/open-api.json
copy to pages/doc/en-us/3.1.6/guide/api/open-api.json
index 1a72e50b33..ac0df3aaf3 100644
--- a/pages/doc/en-us/3.1.5/guide/api/open-api.json
+++ b/pages/doc/en-us/3.1.6/guide/api/open-api.json
@@ -4,7 +4,7 @@
"API",
"Open API"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Background",
diff --git a/pages/doc/en-us/3.1.5/guide/api/pydolphinscheduler.json b/pages/doc/en-us/3.1.6/guide/api/pydolphinscheduler.json
similarity index 95%
copy from pages/doc/en-us/3.1.5/guide/api/pydolphinscheduler.json
copy to pages/doc/en-us/3.1.6/guide/api/pydolphinscheduler.json
index d56d313a0d..5d36a4c4bd 100644
--- a/pages/doc/en-us/3.1.5/guide/api/pydolphinscheduler.json
+++ b/pages/doc/en-us/3.1.6/guide/api/pydolphinscheduler.json
@@ -4,7 +4,7 @@
"API",
"PyDolphinScheduler"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [],
"title": "PyDolphinScheduler",
"link": "/guide/api/pydolphinscheduler"
diff --git a/pages/doc/en-us/3.1.5/guide/data-quality.json b/pages/doc/en-us/3.1.6/guide/data-quality.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/data-quality.json
copy to pages/doc/en-us/3.1.6/guide/data-quality.json
index ca9b44116c..54014096ec 100644
--- a/pages/doc/en-us/3.1.5/guide/data-quality.json
+++ b/pages/doc/en-us/3.1.6/guide/data-quality.json
@@ -4,7 +4,7 @@
"Introduction to Functions",
"Data Quality"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Introduction",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/athena.json b/pages/doc/en-us/3.1.6/guide/datasource/athena.json
similarity index 95%
copy from pages/doc/en-us/3.1.5/guide/datasource/athena.json
copy to pages/doc/en-us/3.1.6/guide/datasource/athena.json
index c85539f919..0065d89f1d 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/athena.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/athena.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"aws-athena\">AWS Athena</h1>\n<p><img src=\"/img/new_ui/dev/datasource/athena.png\" alt=\"AWS Athena\"></p>\n<h2 id=\"datasource-parameters\">Datasource Parameters</h2>\n<table>\n<thead>\n<tr>\n<th><strong>Datasource</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Datasource</td>\n<td>Select ATHENA.</td>\n</tr>\n<tr>\n<td>Datasource name</td>\n<td>Enter the name of the DataSource.</td>\n</tr>\n<tr>\n<td>Description</td>\n<td [...]
+ "__html": "<h1 id=\"aws-athena\">AWS Athena</h1>\n<p><img src=\"/img/new_ui/dev/datasource/athena.png\" alt=\"AWS Athena\"></p>\n<h2 id=\"datasource-parameters\">Datasource Parameters</h2>\n<table>\n<thead>\n<tr>\n<th><strong>Datasource</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Datasource</td>\n<td>Select ATHENA.</td>\n</tr>\n<tr>\n<td>Datasource name</td>\n<td>Enter the name of the DataSource.</td>\n</tr>\n<tr>\n<td>Description</td>\n<td [...]
"location": [
"Introduction to Functions",
"Data Source",
"Amazon Athena"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/clickhouse.json b/pages/doc/en-us/3.1.6/guide/datasource/clickhouse.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/datasource/clickhouse.json
copy to pages/doc/en-us/3.1.6/guide/datasource/clickhouse.json
index bbfdb380bc..e337d2e62e 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/clickhouse.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/clickhouse.json
@@ -5,7 +5,7 @@
"Data Source",
"ClickHouse"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/db2.json b/pages/doc/en-us/3.1.6/guide/datasource/db2.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/datasource/db2.json
copy to pages/doc/en-us/3.1.6/guide/datasource/db2.json
index a5f1d5aee5..d1b659933b 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/db2.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/db2.json
@@ -5,7 +5,7 @@
"Data Source",
"IBM DB2"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/hive.json b/pages/doc/en-us/3.1.6/guide/datasource/hive.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/datasource/hive.json
copy to pages/doc/en-us/3.1.6/guide/datasource/hive.json
index 399e08554d..114005f1e0 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/hive.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/hive.json
@@ -5,7 +5,7 @@
"Data Source",
"HIVE"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Use HiveServer2",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/mysql.json b/pages/doc/en-us/3.1.6/guide/datasource/mysql.json
similarity index 94%
copy from pages/doc/en-us/3.1.5/guide/datasource/mysql.json
copy to pages/doc/en-us/3.1.6/guide/datasource/mysql.json
index 63466cae41..ace6f05736 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/mysql.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/mysql.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"mysql\">MySQL</h1>\n<p><img src=\"/img/new_ui/dev/datasource/mysql.png\" alt=\"mysql\"></p>\n<h2 id=\"datasource-parameters\">Datasource Parameters</h2>\n<table>\n<thead>\n<tr>\n<th><strong>Datasource</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Datasource</td>\n<td>Select MYSQL.</td>\n</tr>\n<tr>\n<td>Datasource name</td>\n<td>Enter the name of the DataSource.</td>\n</tr>\n<tr>\n<td>Description</td>\n<td>Enter a descript [...]
+ "__html": "<h1 id=\"mysql\">MySQL</h1>\n<p><img src=\"/img/new_ui/dev/datasource/mysql.png\" alt=\"mysql\"></p>\n<h2 id=\"datasource-parameters\">Datasource Parameters</h2>\n<table>\n<thead>\n<tr>\n<th><strong>Datasource</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Datasource</td>\n<td>Select MYSQL.</td>\n</tr>\n<tr>\n<td>Datasource name</td>\n<td>Enter the name of the DataSource.</td>\n</tr>\n<tr>\n<td>Description</td>\n<td>Enter a descript [...]
"location": [
"Introduction to Functions",
"Data Source",
"MySQL"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/oracle.json b/pages/doc/en-us/3.1.6/guide/datasource/oracle.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/datasource/oracle.json
copy to pages/doc/en-us/3.1.6/guide/datasource/oracle.json
index c63911f76a..619248e57c 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/oracle.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/oracle.json
@@ -5,7 +5,7 @@
"Data Source",
"Oracle"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/postgresql.json b/pages/doc/en-us/3.1.6/guide/datasource/postgresql.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/datasource/postgresql.json
copy to pages/doc/en-us/3.1.6/guide/datasource/postgresql.json
index e71e557077..3ae4944b29 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/postgresql.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/postgresql.json
@@ -5,7 +5,7 @@
"Data Source",
"PostgreSQL"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/presto.json b/pages/doc/en-us/3.1.6/guide/datasource/presto.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/datasource/presto.json
copy to pages/doc/en-us/3.1.6/guide/datasource/presto.json
index 4302833a09..9d0bc98f6b 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/presto.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/presto.json
@@ -5,7 +5,7 @@
"Data Source",
"Presto"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/redshift.json b/pages/doc/en-us/3.1.6/guide/datasource/redshift.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/datasource/redshift.json
copy to pages/doc/en-us/3.1.6/guide/datasource/redshift.json
index 84d6cd20b5..4dd93db673 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/redshift.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/redshift.json
@@ -5,7 +5,7 @@
"Data Source",
"Amazon Redshift"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/spark.json b/pages/doc/en-us/3.1.6/guide/datasource/spark.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/datasource/spark.json
copy to pages/doc/en-us/3.1.6/guide/datasource/spark.json
index d3324454a0..6e547c3a1f 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/spark.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/spark.json
@@ -5,7 +5,7 @@
"Data Source",
"Spark"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/datasource/sqlserver.json b/pages/doc/en-us/3.1.6/guide/datasource/sqlserver.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/datasource/sqlserver.json
copy to pages/doc/en-us/3.1.6/guide/datasource/sqlserver.json
index 018325dfe5..28793d4e4a 100644
--- a/pages/doc/en-us/3.1.5/guide/datasource/sqlserver.json
+++ b/pages/doc/en-us/3.1.6/guide/datasource/sqlserver.json
@@ -5,7 +5,7 @@
"Data Source",
"SQL SERVER"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Datasource Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/expansion-reduction.json b/pages/doc/en-us/3.1.6/guide/expansion-reduction.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/expansion-reduction.json
copy to pages/doc/en-us/3.1.6/guide/expansion-reduction.json
index 676311d62e..09faa6e9d1 100644
--- a/pages/doc/en-us/3.1.5/guide/expansion-reduction.json
+++ b/pages/doc/en-us/3.1.6/guide/expansion-reduction.json
@@ -1,10 +1,10 @@
{
- "__html": "<h1 id=\"dolphinscheduler-expansion-and-reduction\">DolphinScheduler Expansion and Reduction</h1>\n<h2 id=\"expansion\">Expansion</h2>\n<p>This article describes how to add a new master service or worker service to an existing DolphinScheduler cluster.</p>\n<pre><code>Attention: There cannot be more than one master service process or worker service process on a physical machine.\n If the physical machine which locate the expansion master or worker node has already insta [...]
+ "__html": "<h1 id=\"dolphinscheduler-expansion-and-reduction\">DolphinScheduler Expansion and Reduction</h1>\n<h2 id=\"expansion\">Expansion</h2>\n<p>This article describes how to add a new master service or worker service to an existing DolphinScheduler cluster.</p>\n<pre><code>Attention: There cannot be more than one master service process or worker service process on a physical machine.\n If the physical machine which locate the expansion master or worker node has already insta [...]
"location": [
"Introduction to Functions",
"Expansion and Reduction"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Expansion",
diff --git a/pages/doc/en-us/3.1.5/guide/homepage.json b/pages/doc/en-us/3.1.6/guide/homepage.json
similarity index 95%
copy from pages/doc/en-us/3.1.5/guide/homepage.json
copy to pages/doc/en-us/3.1.6/guide/homepage.json
index 4e6f223ee8..5c888d2f6e 100644
--- a/pages/doc/en-us/3.1.5/guide/homepage.json
+++ b/pages/doc/en-us/3.1.6/guide/homepage.json
@@ -4,7 +4,7 @@
"Introduction to Functions",
"Application Homepage"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [],
"title": "Home Page",
"link": "/guide/homepage"
diff --git a/pages/doc/en-us/3.1.5/guide/installation/cluster.json b/pages/doc/en-us/3.1.6/guide/installation/cluster.json
similarity index 90%
copy from pages/doc/en-us/3.1.5/guide/installation/cluster.json
copy to pages/doc/en-us/3.1.6/guide/installation/cluster.json
index e90659ce3e..54a5f3738f 100644
--- a/pages/doc/en-us/3.1.5/guide/installation/cluster.json
+++ b/pages/doc/en-us/3.1.6/guide/installation/cluster.json
@@ -1,10 +1,10 @@
{
- "__html": "<h1 id=\"cluster-deployment\">Cluster Deployment</h1>\n<p>Cluster deployment is to deploy the DolphinScheduler on multiple machines for running massive tasks in production.</p>\n<p>If you are a new hand and want to experience DolphinScheduler functions, we recommend you install follow <a href=\"/en-us/docs/3.1.5/guide/installation/standalone\">Standalone deployment</a>. If you want to experience more complete functions and schedule massive tasks, we recommend you install fol [...]
+ "__html": "<h1 id=\"cluster-deployment\">Cluster Deployment</h1>\n<p>Cluster deployment is to deploy the DolphinScheduler on multiple machines for running massive tasks in production.</p>\n<p>If you are a new hand and want to experience DolphinScheduler functions, we recommend you install follow <a href=\"/en-us/docs/3.1.6/guide/installation/standalone\">Standalone deployment</a>. If you want to experience more complete functions and schedule massive tasks, we recommend you install fol [...]
"location": [
"Installation",
"Cluster Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Deployment Steps",
diff --git a/pages/doc/en-us/3.1.5/guide/installation/kubernetes.json b/pages/doc/en-us/3.1.6/guide/installation/kubernetes.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/installation/kubernetes.json
copy to pages/doc/en-us/3.1.6/guide/installation/kubernetes.json
index d1796a9ae6..432982d19a 100644
--- a/pages/doc/en-us/3.1.5/guide/installation/kubernetes.json
+++ b/pages/doc/en-us/3.1.6/guide/installation/kubernetes.json
@@ -1,10 +1,10 @@
{
- "__html": "<h1 id=\"quickstart-in-kubernetes\">QuickStart in Kubernetes</h1>\n<p>Kubernetes deployment is DolphinScheduler deployment in a Kubernetes cluster, which can schedule massive tasks and can be used in production.</p>\n<p>If you are a new hand and want to experience DolphinScheduler functions, we recommend you install follow <a href=\"/en-us/docs/3.1.5/guide/installation/standalone\">Standalone deployment</a>. If you want to experience more complete functions and schedule mass [...]
+ "__html": "<h1 id=\"quickstart-in-kubernetes\">QuickStart in Kubernetes</h1>\n<p>Kubernetes deployment is DolphinScheduler deployment in a Kubernetes cluster, which can schedule massive tasks and can be used in production.</p>\n<p>If you are a new hand and want to experience DolphinScheduler functions, we recommend you install follow <a href=\"/en-us/docs/3.1.6/guide/installation/standalone\">Standalone deployment</a>. If you want to experience more complete functions and schedule mass [...]
"location": [
"Installation",
"Kubernetes Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Prerequisites",
diff --git a/pages/doc/en-us/3.1.5/guide/installation/pseudo-cluster.json b/pages/doc/en-us/3.1.6/guide/installation/pseudo-cluster.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/installation/pseudo-cluster.json
copy to pages/doc/en-us/3.1.6/guide/installation/pseudo-cluster.json
index 7535b47bf2..d118fffbd7 100644
--- a/pages/doc/en-us/3.1.5/guide/installation/pseudo-cluster.json
+++ b/pages/doc/en-us/3.1.6/guide/installation/pseudo-cluster.json
@@ -1,10 +1,10 @@
{
- "__html": "<h1 id=\"pseudo-cluster-deployment\">Pseudo-Cluster Deployment</h1>\n<p>The purpose of the pseudo-cluster deployment is to deploy the DolphinScheduler service on a single machine. In this mode, DolphinScheduler's master, worker, API server, are all on the same machine.</p>\n<p>If you are a new hand and want to experience DolphinScheduler functions, we recommend you install follow <a href=\"/en-us/docs/3.1.5/guide/installation/standalone\">Standalone deployment</a>. If you wa [...]
+ "__html": "<h1 id=\"pseudo-cluster-deployment\">Pseudo-Cluster Deployment</h1>\n<p>The purpose of the pseudo-cluster deployment is to deploy the DolphinScheduler service on a single machine. In this mode, DolphinScheduler's master, worker, API server, are all on the same machine.</p>\n<p>If you are a new hand and want to experience DolphinScheduler functions, we recommend you install follow <a href=\"/en-us/docs/3.1.6/guide/installation/standalone\">Standalone deployment</a>. If you wa [...]
"location": [
"Installation",
"Pseudo Cluster Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Preparation",
diff --git a/pages/doc/en-us/3.1.5/guide/installation/standalone.json b/pages/doc/en-us/3.1.6/guide/installation/standalone.json
similarity index 50%
copy from pages/doc/en-us/3.1.5/guide/installation/standalone.json
copy to pages/doc/en-us/3.1.6/guide/installation/standalone.json
index 6153e83ffb..9894c1a215 100644
--- a/pages/doc/en-us/3.1.5/guide/installation/standalone.json
+++ b/pages/doc/en-us/3.1.6/guide/installation/standalone.json
@@ -1,10 +1,10 @@
{
- "__html": "<h1 id=\"standalone\">Standalone</h1>\n<p>Standalone only for quick experience for DolphinScheduler.</p>\n<p>If you are a new hand and want to experience DolphinScheduler functions, we recommend you install follow Standalone deployment. If you want to experience more complete functions and schedule massive tasks, we recommend you install follow <a href=\"/en-us/docs/3.1.5/guide/installation/pseudo-cluster\">pseudo-cluster deployment</a>. If you want to deploy DolphinSchedule [...]
+ "__html": "<h1 id=\"standalone\">Standalone</h1>\n<p>Standalone only for quick experience for DolphinScheduler.</p>\n<p>If you are a new hand and want to experience DolphinScheduler functions, we recommend you install follow Standalone deployment. If you want to experience more complete functions and schedule massive tasks, we recommend you install follow <a href=\"/en-us/docs/3.1.6/guide/installation/pseudo-cluster\">pseudo-cluster deployment</a>. If you want to deploy DolphinSchedule [...]
"location": [
"Installation",
"Standalone Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Preparation",
diff --git a/pages/doc/en-us/3.1.5/guide/integration/rainbond.json b/pages/doc/en-us/3.1.6/guide/integration/rainbond.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/integration/rainbond.json
copy to pages/doc/en-us/3.1.6/guide/integration/rainbond.json
index 499d3afa17..af35a0bdf0 100644
--- a/pages/doc/en-us/3.1.5/guide/integration/rainbond.json
+++ b/pages/doc/en-us/3.1.6/guide/integration/rainbond.json
@@ -5,7 +5,7 @@
"integration",
"Rainbond Deployment"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Prerequisites",
diff --git a/pages/doc/en-us/3.1.5/guide/metrics/metrics.json b/pages/doc/en-us/3.1.6/guide/metrics/metrics.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/metrics/metrics.json
copy to pages/doc/en-us/3.1.6/guide/metrics/metrics.json
index 7d42e7c321..5c91e45249 100644
--- a/pages/doc/en-us/3.1.5/guide/metrics/metrics.json
+++ b/pages/doc/en-us/3.1.6/guide/metrics/metrics.json
@@ -5,7 +5,7 @@
"Metrics",
"Metrics"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Quick Start",
diff --git a/pages/doc/en-us/3.1.5/guide/monitor.json b/pages/doc/en-us/3.1.6/guide/monitor.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/monitor.json
copy to pages/doc/en-us/3.1.6/guide/monitor.json
index 3c0e4feae0..b013f4cb7d 100644
--- a/pages/doc/en-us/3.1.5/guide/monitor.json
+++ b/pages/doc/en-us/3.1.6/guide/monitor.json
@@ -4,7 +4,7 @@
"Introduction to Functions",
"Monitor"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Service Management",
diff --git a/pages/doc/en-us/3.1.5/guide/parameter/built-in.json b/pages/doc/en-us/3.1.6/guide/parameter/built-in.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/parameter/built-in.json
copy to pages/doc/en-us/3.1.6/guide/parameter/built-in.json
index 31bd8e25aa..0849924bd3 100644
--- a/pages/doc/en-us/3.1.5/guide/parameter/built-in.json
+++ b/pages/doc/en-us/3.1.6/guide/parameter/built-in.json
@@ -5,7 +5,7 @@
"Parameter",
"Built-in Parameter"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Basic Built-in Parameter",
diff --git a/pages/doc/en-us/3.1.5/guide/parameter/context.json b/pages/doc/en-us/3.1.6/guide/parameter/context.json
similarity index 94%
copy from pages/doc/en-us/3.1.5/guide/parameter/context.json
copy to pages/doc/en-us/3.1.6/guide/parameter/context.json
index 7fe1f5df03..61fcee0cc6 100644
--- a/pages/doc/en-us/3.1.5/guide/parameter/context.json
+++ b/pages/doc/en-us/3.1.6/guide/parameter/context.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"parameter-context\">Parameter Context</h1>\n<p>DolphinScheduler provides the ability to refer to each other between parameters, including local parameters refer to global parameters and upstream and downstream parameter transfer. Due to the existence of references, it involves the priority of parameters when the parameter names are the same. see also <a href=\"/en-us/docs/3.1.5/guide/parameter/priority\">Parameter Priority</a></p>\n<h2 id=\"local-task-refers-to-glob [...]
+ "__html": "<h1 id=\"parameter-context\">Parameter Context</h1>\n<p>DolphinScheduler provides the ability to refer to each other between parameters, including local parameters refer to global parameters and upstream and downstream parameter transfer. Due to the existence of references, it involves the priority of parameters when the parameter names are the same. see also <a href=\"/en-us/docs/3.1.6/guide/parameter/priority\">Parameter Priority</a></p>\n<h2 id=\"local-task-refers-to-glob [...]
"location": [
"Introduction to Functions",
"Parameter",
"Parameter Context"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Local Task Refers to Global Parameter",
diff --git a/pages/doc/en-us/3.1.5/guide/parameter/global.json b/pages/doc/en-us/3.1.6/guide/parameter/global.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/parameter/global.json
copy to pages/doc/en-us/3.1.6/guide/parameter/global.json
index f505c6e3ce..f7e195a592 100644
--- a/pages/doc/en-us/3.1.5/guide/parameter/global.json
+++ b/pages/doc/en-us/3.1.6/guide/parameter/global.json
@@ -5,7 +5,7 @@
"Parameter",
"Global Parameter"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Scope",
diff --git a/pages/doc/en-us/3.1.5/guide/parameter/local.json b/pages/doc/en-us/3.1.6/guide/parameter/local.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/parameter/local.json
copy to pages/doc/en-us/3.1.6/guide/parameter/local.json
index 998f102565..eac468fc4c 100644
--- a/pages/doc/en-us/3.1.5/guide/parameter/local.json
+++ b/pages/doc/en-us/3.1.6/guide/parameter/local.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"local-parameter\">Local Parameter</h1>\n<h2 id=\"scope\">Scope</h2>\n<p>Parameters configured on the task definition page, the scope of this parameter is inside this task only. But if you configure according to <a href=\"/en-us/docs/3.1.5/guide/parameter/context\">Refer to Parameter Context</a>, it could pass to downstream tasks.</p>\n<h2 id=\"usage\">Usage</h2>\n<ul>\n<li>If you want to use parameter in single task, see <a href=\"#use-local-parameter-by-custom-para [...]
+ "__html": "<h1 id=\"local-parameter\">Local Parameter</h1>\n<h2 id=\"scope\">Scope</h2>\n<p>Parameters configured on the task definition page, the scope of this parameter is inside this task only. But if you configure according to <a href=\"/en-us/docs/3.1.6/guide/parameter/context\">Refer to Parameter Context</a>, it could pass to downstream tasks.</p>\n<h2 id=\"usage\">Usage</h2>\n<ul>\n<li>If you want to use parameter in single task, see <a href=\"#use-local-parameter-by-custom-para [...]
"location": [
"Introduction to Functions",
"Parameter",
"Local Parameter"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Scope",
diff --git a/pages/doc/en-us/3.1.5/guide/parameter/priority.json b/pages/doc/en-us/3.1.6/guide/parameter/priority.json
similarity index 94%
copy from pages/doc/en-us/3.1.5/guide/parameter/priority.json
copy to pages/doc/en-us/3.1.6/guide/parameter/priority.json
index d4a8415114..4c93dcdac1 100644
--- a/pages/doc/en-us/3.1.5/guide/parameter/priority.json
+++ b/pages/doc/en-us/3.1.6/guide/parameter/priority.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"parameter-priority\">Parameter Priority</h1>\n<p>DolphinScheduler has three parameter types:</p>\n<ul>\n<li><a href=\"/en-us/docs/3.1.5/guide/parameter/global\">Global Parameter</a>: parameters defined at the workflow define page.</li>\n<li><a href=\"/en-us/docs/3.1.5/guide/parameter/context\">Parameter Context</a>: parameters passed by upstream task nodes.</li>\n<li><a href=\"/en-us/docs/3.1.5/guide/parameter/local\">Local Parameter</a>: parameters belong to its no [...]
+ "__html": "<h1 id=\"parameter-priority\">Parameter Priority</h1>\n<p>DolphinScheduler has three parameter types:</p>\n<ul>\n<li><a href=\"/en-us/docs/3.1.6/guide/parameter/global\">Global Parameter</a>: parameters defined at the workflow define page.</li>\n<li><a href=\"/en-us/docs/3.1.6/guide/parameter/context\">Parameter Context</a>: parameters passed by upstream task nodes.</li>\n<li><a href=\"/en-us/docs/3.1.6/guide/parameter/local\">Local Parameter</a>: parameters belong to its no [...]
"location": [
"Introduction to Functions",
"Parameter",
"Parameter Priority"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Example",
diff --git a/pages/doc/en-us/3.1.5/guide/project/project-list.json b/pages/doc/en-us/3.1.6/guide/project/project-list.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/project/project-list.json
copy to pages/doc/en-us/3.1.6/guide/project/project-list.json
index 04d4f238a2..c476d625f3 100644
--- a/pages/doc/en-us/3.1.5/guide/project/project-list.json
+++ b/pages/doc/en-us/3.1.6/guide/project/project-list.json
@@ -5,7 +5,7 @@
"Project",
"Project List"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Project List",
diff --git a/pages/doc/en-us/3.1.5/guide/project/task-definition.json b/pages/doc/en-us/3.1.6/guide/project/task-definition.json
similarity index 95%
copy from pages/doc/en-us/3.1.5/guide/project/task-definition.json
copy to pages/doc/en-us/3.1.6/guide/project/task-definition.json
index bee9a5f9d1..3241081282 100644
--- a/pages/doc/en-us/3.1.5/guide/project/task-definition.json
+++ b/pages/doc/en-us/3.1.6/guide/project/task-definition.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"task-definition\">Task Definition</h1>\n<h2 id=\"batch-task-definition\">Batch Task Definition</h2>\n<p>Task definition allows to modify or operate tasks at the task level rather than modifying them in the workflow definition.\nWe already have workflow level task editor in <a href=\"/en-us/docs/3.1.5/guide/project/workflow-definition\">workflow definition</a> which you can click the specific\nworkflow and then edit its task definition. It is depressing when you want [...]
+ "__html": "<h1 id=\"task-definition\">Task Definition</h1>\n<h2 id=\"batch-task-definition\">Batch Task Definition</h2>\n<p>Task definition allows to modify or operate tasks at the task level rather than modifying them in the workflow definition.\nWe already have workflow level task editor in <a href=\"/en-us/docs/3.1.6/guide/project/workflow-definition\">workflow definition</a> which you can click the specific\nworkflow and then edit its task definition. It is depressing when you want [...]
"location": [
"Introduction to Functions",
"Project",
"Task Definition"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Batch Task Definition",
diff --git a/pages/doc/en-us/3.1.5/guide/project/task-instance.json b/pages/doc/en-us/3.1.6/guide/project/task-instance.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/project/task-instance.json
copy to pages/doc/en-us/3.1.6/guide/project/task-instance.json
index 7c644b115f..cc7dfb2f1f 100644
--- a/pages/doc/en-us/3.1.5/guide/project/task-instance.json
+++ b/pages/doc/en-us/3.1.6/guide/project/task-instance.json
@@ -5,7 +5,7 @@
"Project",
"Task Instance"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Batch Task Instance",
diff --git a/pages/doc/en-us/3.1.5/guide/project/workflow-definition.json b/pages/doc/en-us/3.1.6/guide/project/workflow-definition.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/project/workflow-definition.json
copy to pages/doc/en-us/3.1.6/guide/project/workflow-definition.json
index 806f6abdeb..460c80ed97 100644
--- a/pages/doc/en-us/3.1.5/guide/project/workflow-definition.json
+++ b/pages/doc/en-us/3.1.6/guide/project/workflow-definition.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"workflow-definition\">Workflow Definition</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Work Definition screen shows list of existing workflows and utility to create or import workflows.</p>\n<p><img src=\"/img/new_ui/dev/project/workflow-overview.png\" alt=\"workflow-dag\"></p>\n<h2 id=\"create-workflow-definition\">Create workflow definition</h2>\n<p>Click <code>Project Management -> Workflow -> Workflow Definition</code>, enter the <code>Workflow Definition</ [...]
+ "__html": "<h1 id=\"workflow-definition\">Workflow Definition</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Work Definition screen shows list of existing workflows and utility to create or import workflows.</p>\n<p><img src=\"/img/new_ui/dev/project/workflow-overview.png\" alt=\"workflow-dag\"></p>\n<h2 id=\"create-workflow-definition\">Create workflow definition</h2>\n<p>Click <code>Project Management -> Workflow -> Workflow Definition</code>, enter the <code>Workflow Definition</ [...]
"location": [
"Introduction to Functions",
"Project",
"Workflow Definition"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/project/workflow-instance.json b/pages/doc/en-us/3.1.6/guide/project/workflow-instance.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/project/workflow-instance.json
copy to pages/doc/en-us/3.1.6/guide/project/workflow-instance.json
index c8268564da..995a1e2712 100644
--- a/pages/doc/en-us/3.1.5/guide/project/workflow-instance.json
+++ b/pages/doc/en-us/3.1.6/guide/project/workflow-instance.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"workflow-instance\">Workflow Instance</h1>\n<h2 id=\"view-workflow-instance\">View Workflow Instance</h2>\n<p>Click <code>Project Management -> Workflow -> Workflow Instance</code>, enter the Workflow Instance page, as shown in the following figure:</p>\n<p><img src=\"/img/new_ui/dev/project/workflow-instance.png\" alt=\"workflow-instance\"></p>\n<p>Click the workflow name to enter the DAG view page, and check the task execution status, as shown in the followi [...]
+ "__html": "<h1 id=\"workflow-instance\">Workflow Instance</h1>\n<h2 id=\"view-workflow-instance\">View Workflow Instance</h2>\n<p>Click <code>Project Management -> Workflow -> Workflow Instance</code>, enter the Workflow Instance page, as shown in the following figure:</p>\n<p><img src=\"/img/new_ui/dev/project/workflow-instance.png\" alt=\"workflow-instance\"></p>\n<p>Click the workflow name to enter the DAG view page, and check the task execution status, as shown in the followi [...]
"location": [
"Introduction to Functions",
"Project",
"Workflow Instance"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "View Workflow Instance",
diff --git a/pages/doc/en-us/3.1.6/guide/resource/configuration.json b/pages/doc/en-us/3.1.6/guide/resource/configuration.json
new file mode 100644
index 0000000000..7dbe6cba04
--- /dev/null
+++ b/pages/doc/en-us/3.1.6/guide/resource/configuration.json
@@ -0,0 +1,35 @@
+{
+ "__html": "<h1 id=\"resource-center-configuration\">Resource Center Configuration</h1>\n<ul>\n<li>You could use <code>Resource Center</code> to upload text files, UDFs and other task-related files.</li>\n<li>You could configure <code>Resource Center</code> to use distributed file system like <a href=\"https://hadoop.apache.org/docs/r2.7.0/\">Hadoop</a> (2.6+), <a href=\"https://github.com/minio/minio\">MinIO</a> cluster or remote storage products like <a href=\"https://aws.amazon.com/s [...]
+ "location": [
+ "Introduction to Functions",
+ "Resource",
+ "Configuration"
+ ],
+ "time": "2023-05-15",
+ "structure": [
+ {
+ "title": "Use Local File System",
+ "children": [
+ {
+ "title": "Configure common.properties",
+ "children": [],
+ "anchor": "configure-common.properties"
+ }
+ ],
+ "anchor": "use-local-file-system"
+ },
+ {
+ "title": "Use HDFS or Remote Object Storage",
+ "children": [
+ {
+ "title": "Configure common.properties",
+ "children": [],
+ "anchor": "configure-common.properties"
+ }
+ ],
+ "anchor": "use-hdfs-or-remote-object-storage"
+ }
+ ],
+ "title": "Resource Center Configuration",
+ "link": "/guide/resource/configuration"
+}
\ No newline at end of file
diff --git a/pages/doc/en-us/3.1.5/guide/resource/file-manage.json b/pages/doc/en-us/3.1.6/guide/resource/file-manage.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/resource/file-manage.json
copy to pages/doc/en-us/3.1.6/guide/resource/file-manage.json
index db5b61a486..05e63eff28 100644
--- a/pages/doc/en-us/3.1.5/guide/resource/file-manage.json
+++ b/pages/doc/en-us/3.1.6/guide/resource/file-manage.json
@@ -5,7 +5,7 @@
"Resource",
"File Manage"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Basic Operations",
diff --git a/pages/doc/en-us/3.1.5/guide/resource/intro.json b/pages/doc/en-us/3.1.6/guide/resource/intro.json
similarity index 96%
copy from pages/doc/en-us/3.1.5/guide/resource/intro.json
copy to pages/doc/en-us/3.1.6/guide/resource/intro.json
index 751d9a961d..9964f5f45a 100644
--- a/pages/doc/en-us/3.1.5/guide/resource/intro.json
+++ b/pages/doc/en-us/3.1.6/guide/resource/intro.json
@@ -5,7 +5,7 @@
"Resource",
"Introduction"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [],
"title": "Resource Center Introduction",
"link": "/guide/resource/intro"
diff --git a/pages/doc/en-us/3.1.5/guide/resource/task-group.json b/pages/doc/en-us/3.1.6/guide/resource/task-group.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/resource/task-group.json
copy to pages/doc/en-us/3.1.6/guide/resource/task-group.json
index f7fe9c81fd..232aa3bbba 100644
--- a/pages/doc/en-us/3.1.5/guide/resource/task-group.json
+++ b/pages/doc/en-us/3.1.6/guide/resource/task-group.json
@@ -5,7 +5,7 @@
"Resource",
"Task Group Manage"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Task Group Configuration",
diff --git a/pages/doc/en-us/3.1.5/guide/resource/udf-manage.json b/pages/doc/en-us/3.1.6/guide/resource/udf-manage.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/resource/udf-manage.json
copy to pages/doc/en-us/3.1.6/guide/resource/udf-manage.json
index cd4644334e..824777e37a 100644
--- a/pages/doc/en-us/3.1.5/guide/resource/udf-manage.json
+++ b/pages/doc/en-us/3.1.6/guide/resource/udf-manage.json
@@ -5,7 +5,7 @@
"Resource",
"UDF Manage"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Resource Management",
diff --git a/pages/doc/en-us/3.1.5/guide/security.json b/pages/doc/en-us/3.1.6/guide/security.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/security.json
copy to pages/doc/en-us/3.1.6/guide/security.json
index 06241cb3ad..516fb34784 100644
--- a/pages/doc/en-us/3.1.5/guide/security.json
+++ b/pages/doc/en-us/3.1.6/guide/security.json
@@ -4,7 +4,7 @@
"Introduction to Functions",
"Security"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Create Queue",
diff --git a/pages/doc/en-us/3.1.6/guide/start/docker.json b/pages/doc/en-us/3.1.6/guide/start/docker.json
new file mode 100644
index 0000000000..4604c66f90
--- /dev/null
+++ b/pages/doc/en-us/3.1.6/guide/start/docker.json
@@ -0,0 +1,96 @@
+{
+ "__html": "<h1 id=\"docker-quick-start\">Docker Quick Start</h1>\n<p>There are three ways to start DolphinScheduler with Docker</p>\n<ul>\n<li><a href=\"#using-standalone-server-docker-image\">Standalone-server</a> is the way you find if you just want to start and try DolphinScheduler as a beginner.</li>\n<li><a href=\"#using-docker-compose-to-start-server\">docker-compose</a> is for some who want to deploy DolphinScheduler in small or event middle scale workflows in their daily work.< [...]
+ "location": [
+ "Quick Start",
+ "Docker Deployment"
+ ],
+ "time": "2023-05-15",
+ "structure": [
+ {
+ "title": "Prepare",
+ "children": [
+ {
+ "title": "Using standalone-server Docker Image",
+ "children": [],
+ "anchor": "using-standalone-server-docker-image"
+ },
+ {
+ "title": "Using docker-compose to Start Server",
+ "children": [],
+ "anchor": "using-docker-compose-to-start-server"
+ },
+ {
+ "title": "Using Exists PostgreSQL ZooKeeper",
+ "children": [],
+ "anchor": "using-exists-postgresql-zookeeper"
+ }
+ ],
+ "anchor": "prepare"
+ },
+ {
+ "title": "Start Server",
+ "children": [
+ {
+ "title": "Using standalone-server Docker Image",
+ "children": [],
+ "anchor": "using-standalone-server-docker-image"
+ },
+ {
+ "title": "Using docker-compose to Start Server",
+ "children": [],
+ "anchor": "using-docker-compose-to-start-server"
+ },
+ {
+ "title": "Using Exists PostgreSQL ZooKeeper",
+ "children": [],
+ "anchor": "using-exists-postgresql-zookeeper"
+ }
+ ],
+ "anchor": "start-server"
+ },
+ {
+ "title": "Login DolphinScheduler",
+ "children": [
+ {
+ "title": "Using standalone-server Docker Image",
+ "children": [],
+ "anchor": "using-standalone-server-docker-image"
+ },
+ {
+ "title": "Using docker-compose to Start Server",
+ "children": [],
+ "anchor": "using-docker-compose-to-start-server"
+ },
+ {
+ "title": "Using Exists PostgreSQL ZooKeeper",
+ "children": [],
+ "anchor": "using-exists-postgresql-zookeeper"
+ }
+ ],
+ "anchor": "login-dolphinscheduler"
+ },
+ {
+ "title": "Change Environment Variable",
+ "children": [
+ {
+ "title": "Using standalone-server Docker Image",
+ "children": [],
+ "anchor": "using-standalone-server-docker-image"
+ },
+ {
+ "title": "Using docker-compose to Start Server",
+ "children": [],
+ "anchor": "using-docker-compose-to-start-server"
+ },
+ {
+ "title": "Using Exists PostgreSQL ZooKeeper",
+ "children": [],
+ "anchor": "using-exists-postgresql-zookeeper"
+ }
+ ],
+ "anchor": "change-environment-variable"
+ }
+ ],
+ "title": "Docker Quick Start",
+ "link": "/guide/start/docker"
+}
\ No newline at end of file
diff --git a/pages/doc/en-us/3.1.5/guide/start/quick-start.json b/pages/doc/en-us/3.1.6/guide/start/quick-start.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/start/quick-start.json
copy to pages/doc/en-us/3.1.6/guide/start/quick-start.json
index cf999da0e7..d49ddd1271 100644
--- a/pages/doc/en-us/3.1.5/guide/start/quick-start.json
+++ b/pages/doc/en-us/3.1.6/guide/start/quick-start.json
@@ -4,7 +4,7 @@
"Quick Start",
"Quick Start"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Administrator User Login",
diff --git a/pages/doc/en-us/3.1.5/guide/task/appendix.json b/pages/doc/en-us/3.1.6/guide/task/appendix.json
similarity index 95%
copy from pages/doc/en-us/3.1.5/guide/task/appendix.json
copy to pages/doc/en-us/3.1.6/guide/task/appendix.json
index 865b715a49..cb3c733f72 100644
--- a/pages/doc/en-us/3.1.5/guide/task/appendix.json
+++ b/pages/doc/en-us/3.1.6/guide/task/appendix.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"dolphinscheduler-task-parameters-appendix\">DolphinScheduler Task Parameters Appendix</h1>\n<p>DolphinScheduler task plugins share some common default parameters. Each type of task contains all or <strong>some</strong> default parameters as follows:</p>\n<h2 id=\"default-task-parameters\">Default Task Parameters</h2>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Node Name</td> [...]
+ "__html": "<h1 id=\"dolphinscheduler-task-parameters-appendix\">DolphinScheduler Task Parameters Appendix</h1>\n<p>DolphinScheduler task plugins share some common default parameters. Each type of task contains all or <strong>some</strong> default parameters as follows:</p>\n<h2 id=\"default-task-parameters\">Default Task Parameters</h2>\n<table>\n<thead>\n<tr>\n<th><strong>Parameter</strong></th>\n<th><strong>Description</strong></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Node Name</td> [...]
"location": [
"Introduction to Functions",
"Task",
"Appendix"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Default Task Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/task/chunjun.json b/pages/doc/en-us/3.1.6/guide/task/chunjun.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/task/chunjun.json
copy to pages/doc/en-us/3.1.6/guide/task/chunjun.json
index 2f62f553db..dbc9777874 100644
--- a/pages/doc/en-us/3.1.5/guide/task/chunjun.json
+++ b/pages/doc/en-us/3.1.6/guide/task/chunjun.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"chunjun\">ChunJun</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>ChunJun task type for executing ChunJun programs. For ChunJun nodes, the worker will execute <code>${CHUNJUN_HOME}/bin/start-chunjun</code> to analyze the input json file.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Drag [...]
+ "__html": "<h1 id=\"chunjun\">ChunJun</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>ChunJun task type for executing ChunJun programs. For ChunJun nodes, the worker will execute <code>${CHUNJUN_HOME}/bin/start-chunjun</code> to analyze the input json file.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Drag [...]
"location": [
"Introduction to Functions",
"Task",
"ChunJun"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/conditions.json b/pages/doc/en-us/3.1.6/guide/task/conditions.json
similarity index 94%
copy from pages/doc/en-us/3.1.5/guide/task/conditions.json
copy to pages/doc/en-us/3.1.6/guide/task/conditions.json
index cb5ffe8baa..bea1c266d3 100644
--- a/pages/doc/en-us/3.1.5/guide/task/conditions.json
+++ b/pages/doc/en-us/3.1.6/guide/task/conditions.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"conditions\">Conditions</h1>\n<p>Condition is a conditional node, that determines which downstream task should run based on the condition of the upstream task. Currently, the Conditions support multiple upstream tasks, but only two downstream tasks. When the number of upstream tasks exceeds one, achieve complex upstream dependencies by through <code>and</code> and <code>or</code> operators.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project [...]
+ "__html": "<h1 id=\"conditions\">Conditions</h1>\n<p>Condition is a conditional node, that determines which downstream task should run based on the condition of the upstream task. Currently, the Conditions support multiple upstream tasks, but only two downstream tasks. When the number of upstream tasks exceeds one, achieve complex upstream dependencies by through <code>and</code> and <code>or</code> operators.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project [...]
"location": [
"Introduction to Functions",
"Task",
"Conditions"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Create Task",
diff --git a/pages/doc/en-us/3.1.5/guide/task/datax.json b/pages/doc/en-us/3.1.6/guide/task/datax.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/task/datax.json
copy to pages/doc/en-us/3.1.6/guide/task/datax.json
index 7d3506085c..795e58ab18 100644
--- a/pages/doc/en-us/3.1.5/guide/task/datax.json
+++ b/pages/doc/en-us/3.1.6/guide/task/datax.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"datax\">DataX</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>DataX task type for executing DataX programs. For DataX nodes, the worker will execute <code>${DATAX_HOME}/bin/datax.py</code> to analyze the input json file.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Drag the <img src=\"/i [...]
+ "__html": "<h1 id=\"datax\">DataX</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>DataX task type for executing DataX programs. For DataX nodes, the worker will execute <code>${DATAX_HOME}/bin/datax.py</code> to analyze the input json file.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Drag the <img src=\"/i [...]
"location": [
"Introduction to Functions",
"Task",
"DataX"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/dependent.json b/pages/doc/en-us/3.1.6/guide/task/dependent.json
similarity index 96%
copy from pages/doc/en-us/3.1.5/guide/task/dependent.json
copy to pages/doc/en-us/3.1.6/guide/task/dependent.json
index 3600a1b96f..58363a741a 100644
--- a/pages/doc/en-us/3.1.5/guide/task/dependent.json
+++ b/pages/doc/en-us/3.1.6/guide/task/dependent.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"dependent\">Dependent</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Dependent nodes are <strong>dependency check nodes</strong>. For example, process A depends on the successful execution of process B from yesterday, and the dependent node will check whether process B run successful yesterday.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</ [...]
+ "__html": "<h1 id=\"dependent\">Dependent</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Dependent nodes are <strong>dependency check nodes</strong>. For example, process A depends on the successful execution of process B from yesterday, and the dependent node will check whether process B run successful yesterday.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</ [...]
"location": [
"Introduction to Functions",
"Task",
"Dependent"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/dinky.json b/pages/doc/en-us/3.1.6/guide/task/dinky.json
similarity index 96%
copy from pages/doc/en-us/3.1.5/guide/task/dinky.json
copy to pages/doc/en-us/3.1.6/guide/task/dinky.json
index f9a65431a8..0748832833 100644
--- a/pages/doc/en-us/3.1.5/guide/task/dinky.json
+++ b/pages/doc/en-us/3.1.6/guide/task/dinky.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"dinky\">Dinky</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Use <code>Dinky Task</code> to create a dinky-type task and support one-stop development, debugging, operation and maintenance of FlinkSql, Flink jar and SQL. When the worker executes <code>Dinky Task</code>,\nit will call <code>Dinky API</code> to trigger dinky task. Click <a href=\"http://www.dlink.top/\">here</a> for details about <code>Dinky</code>.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li> [...]
+ "__html": "<h1 id=\"dinky\">Dinky</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Use <code>Dinky Task</code> to create a dinky-type task and support one-stop development, debugging, operation and maintenance of FlinkSql, Flink jar and SQL. When the worker executes <code>Dinky Task</code>,\nit will call <code>Dinky API</code> to trigger dinky task. Click <a href=\"http://www.dlink.top/\">here</a> for details about <code>Dinky</code>.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li> [...]
"location": [
"Introduction to Functions",
"Task",
"Dinky"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/dvc.json b/pages/doc/en-us/3.1.6/guide/task/dvc.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/task/dvc.json
copy to pages/doc/en-us/3.1.6/guide/task/dvc.json
index 3fc089a86f..858184b59c 100644
--- a/pages/doc/en-us/3.1.5/guide/task/dvc.json
+++ b/pages/doc/en-us/3.1.6/guide/task/dvc.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"dvc-node\">DVC Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><a href=\"https://dvc.org\">DVC (Data Version Control)</a> is an excellent open-source version control system for machine learning projects.</p>\n<p>The DVC plugin is used to use the data version management function of DVC on DolphinScheduler, helping users to carry out data version management easily.</p>\n<p>The plugin provides the following three functions:</p>\n<ul>\n<li>Init DVC: Initialize the Git [...]
+ "__html": "<h1 id=\"dvc-node\">DVC Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><a href=\"https://dvc.org\">DVC (Data Version Control)</a> is an excellent open-source version control system for machine learning projects.</p>\n<p>The DVC plugin is used to use the data version management function of DVC on DolphinScheduler, helping users to carry out data version management easily.</p>\n<p>The plugin provides the following three functions:</p>\n<ul>\n<li>Init DVC: Initialize the Git [...]
"location": [
"Introduction to Functions",
"Task",
"DVC"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/emr.json b/pages/doc/en-us/3.1.6/guide/task/emr.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/task/emr.json
copy to pages/doc/en-us/3.1.6/guide/task/emr.json
index b75365124c..884e719150 100644
--- a/pages/doc/en-us/3.1.5/guide/task/emr.json
+++ b/pages/doc/en-us/3.1.6/guide/task/emr.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"amazon-emr\">Amazon EMR</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Amazon EMR task type, for operation EMR clusters on AWS and running computing tasks.\nUsing <a href=\"https://aws.amazon.com/cn/sdk-for-java/\">aws-java-sdk</a> in the background code, to transfer JSON parameters to task object and submit to AWS, Two program types are currently supported:</p>\n<ul>\n<li><code>RUN_JOB_FLOW</code> Using <a href=\"https://docs.aws.amazon.com/emr/latest/APIReference/API [...]
+ "__html": "<h1 id=\"amazon-emr\">Amazon EMR</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Amazon EMR task type, for operation EMR clusters on AWS and running computing tasks.\nUsing <a href=\"https://aws.amazon.com/cn/sdk-for-java/\">aws-java-sdk</a> in the background code, to transfer JSON parameters to task object and submit to AWS, Two program types are currently supported:</p>\n<ul>\n<li><code>RUN_JOB_FLOW</code> Using <a href=\"https://docs.aws.amazon.com/emr/latest/APIReference/API [...]
"location": [
"Introduction to Functions",
"Task",
"Amazon EMR"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/flink.json b/pages/doc/en-us/3.1.6/guide/task/flink.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/task/flink.json
copy to pages/doc/en-us/3.1.6/guide/task/flink.json
index d99ae187a5..d3db6534d1 100644
--- a/pages/doc/en-us/3.1.5/guide/task/flink.json
+++ b/pages/doc/en-us/3.1.6/guide/task/flink.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"flink-node\">Flink Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Flink task type, used to execute Flink programs. For Flink nodes:</p>\n<ol>\n<li>\n<p>When the program type is Java, Scala or Python, the worker submits the task <code>flink run</code> using the Flink command. See <a href=\"https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/cli/\">flink cli</a> for more details.</p>\n</li>\n<li>\n<p>When the program type is SQL, the worker su [...]
+ "__html": "<h1 id=\"flink-node\">Flink Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Flink task type, used to execute Flink programs. For Flink nodes:</p>\n<ol>\n<li>\n<p>When the program type is Java, Scala or Python, the worker submits the task <code>flink run</code> using the Flink command. See <a href=\"https://nightlies.apache.org/flink/flink-docs-release-1.14/docs/deployment/cli/\">flink cli</a> for more details.</p>\n</li>\n<li>\n<p>When the program type is SQL, the worker su [...]
"location": [
"Introduction to Functions",
"Task",
"Flink"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/hive-cli.json b/pages/doc/en-us/3.1.6/guide/task/hive-cli.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/task/hive-cli.json
copy to pages/doc/en-us/3.1.6/guide/task/hive-cli.json
index f0b371112d..388be373f1 100644
--- a/pages/doc/en-us/3.1.5/guide/task/hive-cli.json
+++ b/pages/doc/en-us/3.1.6/guide/task/hive-cli.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"hive-cli\">Hive CLI</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Use <code>Hive Cli Task</code> to create a <code>Hive Cli</code> type task and execute hive SQL from scripts or files.\nThe workers run <code>hive -e</code> to execute hive sql from scripts or <code>hive -f</code> to execute from files in <code>Resource Center</code>.</p>\n<h2 id=\"hive-cli-task-vs-sql-task-with-hive-datasource\">Hive CLI Task vs SQL Task With Hive Datasource</h2>\n<p>In DolphinSchedule [...]
+ "__html": "<h1 id=\"hive-cli\">Hive CLI</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Use <code>Hive Cli Task</code> to create a <code>Hive Cli</code> type task and execute hive SQL from scripts or files.\nThe workers run <code>hive -e</code> to execute hive sql from scripts or <code>hive -f</code> to execute from files in <code>Resource Center</code>.</p>\n<h2 id=\"hive-cli-task-vs-sql-task-with-hive-datasource\">Hive CLI Task vs SQL Task With Hive Datasource</h2>\n<p>In DolphinSchedule [...]
"location": [
"Introduction to Functions",
"Task",
"Hive CLI"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/http.json b/pages/doc/en-us/3.1.6/guide/task/http.json
similarity index 97%
copy from pages/doc/en-us/3.1.5/guide/task/http.json
copy to pages/doc/en-us/3.1.6/guide/task/http.json
index d693b91308..6710012aec 100644
--- a/pages/doc/en-us/3.1.5/guide/task/http.json
+++ b/pages/doc/en-us/3.1.6/guide/task/http.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"http-node\">HTTP Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>This node is used to perform http type tasks such as the common POST and GET request types, and also supports http request validation and other functions.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Drag the <img src= [...]
+ "__html": "<h1 id=\"http-node\">HTTP Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>This node is used to perform http type tasks such as the common POST and GET request types, and also supports http request validation and other functions.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Drag the <img src= [...]
"location": [
"Introduction to Functions",
"Task",
"HTTP"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/jupyter.json b/pages/doc/en-us/3.1.6/guide/task/jupyter.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/task/jupyter.json
copy to pages/doc/en-us/3.1.6/guide/task/jupyter.json
index 476547cd7d..13bc03d61b 100644
--- a/pages/doc/en-us/3.1.5/guide/task/jupyter.json
+++ b/pages/doc/en-us/3.1.6/guide/task/jupyter.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"jupyter\">Jupyter</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Use <code>Jupyter Task</code> to create a jupyter-type task and execute jupyter notes. When the worker executes <code>Jupyter Task</code>,\nit will use <code>papermill</code> to evaluate jupyter notes. Click <a href=\"https://papermill.readthedocs.io/en/latest/\">here</a> for details about <code>papermill</code>.</p>\n<h2 id=\"conda-configuration\">Conda Configuration</h2>\n<ul>\n<li>Config <code>conda.pa [...]
+ "__html": "<h1 id=\"jupyter\">Jupyter</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Use <code>Jupyter Task</code> to create a jupyter-type task and execute jupyter notes. When the worker executes <code>Jupyter Task</code>,\nit will use <code>papermill</code> to evaluate jupyter notes. Click <a href=\"https://papermill.readthedocs.io/en/latest/\">here</a> for details about <code>papermill</code>.</p>\n<h2 id=\"conda-configuration\">Conda Configuration</h2>\n<ul>\n<li>Config <code>conda.pa [...]
"location": [
"Introduction to Functions",
"Task",
"Jupyter"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/kubernetes.json b/pages/doc/en-us/3.1.6/guide/task/kubernetes.json
similarity index 97%
copy from pages/doc/en-us/3.1.5/guide/task/kubernetes.json
copy to pages/doc/en-us/3.1.6/guide/task/kubernetes.json
index 0cfa574f14..1d19a9afd4 100644
--- a/pages/doc/en-us/3.1.5/guide/task/kubernetes.json
+++ b/pages/doc/en-us/3.1.6/guide/task/kubernetes.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"k8s-node\">K8S Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>K8S task type used to execute a batch task. In this task, the worker submits the task by using a k8s client.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Drag from the toolbar <img src=\"/img/tasks/icons/kubernetes.png\" [...]
+ "__html": "<h1 id=\"k8s-node\">K8S Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>K8S task type used to execute a batch task. In this task, the worker submits the task by using a k8s client.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Drag from the toolbar <img src=\"/img/tasks/icons/kubernetes.png\" [...]
"location": [
"Introduction to Functions",
"Task",
"Kubernetes"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/map-reduce.json b/pages/doc/en-us/3.1.6/guide/task/map-reduce.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/task/map-reduce.json
copy to pages/doc/en-us/3.1.6/guide/task/map-reduce.json
index 393094ec4b..a6d8c258ff 100644
--- a/pages/doc/en-us/3.1.5/guide/task/map-reduce.json
+++ b/pages/doc/en-us/3.1.6/guide/task/map-reduce.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"mapreduce-node\">MapReduce Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>MapReduce(MR) task type used for executing MapReduce programs. For MapReduce nodes, the worker submits the task by using the Hadoop command <code>hadoop jar</code>. See <a href=\"https://hadoop.apache.org/docs/r3.2.4/hadoop-project-dist/hadoop-common/CommandsManual.html#jar\">Hadoop Command Manual</a> for more details.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Proje [...]
+ "__html": "<h1 id=\"mapreduce-node\">MapReduce Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>MapReduce(MR) task type used for executing MapReduce programs. For MapReduce nodes, the worker submits the task by using the Hadoop command <code>hadoop jar</code>. See <a href=\"https://hadoop.apache.org/docs/r3.2.4/hadoop-project-dist/hadoop-common/CommandsManual.html#jar\">Hadoop Command Manual</a> for more details.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Proje [...]
"location": [
"Introduction to Functions",
"Task",
"MapReduce"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/mlflow.json b/pages/doc/en-us/3.1.6/guide/task/mlflow.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/task/mlflow.json
copy to pages/doc/en-us/3.1.6/guide/task/mlflow.json
index d60f23c5eb..8b5200419f 100644
--- a/pages/doc/en-us/3.1.5/guide/task/mlflow.json
+++ b/pages/doc/en-us/3.1.6/guide/task/mlflow.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"mlflow-node\">MLflow Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><a href=\"https://mlflow.org\">MLflow</a> is an excellent open source platform to manage the ML lifecycle, including experimentation,\nreproducibility, deployment, and a central model registry.</p>\n<p>MLflow task plugin used to execute MLflow tasks，Currently contains MLflow Projects and MLflow Models. (Model Registry will soon be rewarded for support)</p>\n<ul>\n<li>MLflow Projects: Package data [...]
+ "__html": "<h1 id=\"mlflow-node\">MLflow Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><a href=\"https://mlflow.org\">MLflow</a> is an excellent open source platform to manage the ML lifecycle, including experimentation,\nreproducibility, deployment, and a central model registry.</p>\n<p>MLflow task plugin used to execute MLflow tasks，Currently contains MLflow Projects and MLflow Models. (Model Registry will soon be rewarded for support)</p>\n<ul>\n<li>MLflow Projects: Package data [...]
"location": [
"Introduction to Functions",
"Task",
"MLflow"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/openmldb.json b/pages/doc/en-us/3.1.6/guide/task/openmldb.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/task/openmldb.json
copy to pages/doc/en-us/3.1.6/guide/task/openmldb.json
index 0e78a5041d..ccad6d51f4 100644
--- a/pages/doc/en-us/3.1.5/guide/task/openmldb.json
+++ b/pages/doc/en-us/3.1.6/guide/task/openmldb.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"openmldb-node\">OpenMLDB Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><a href=\"https://openmldb.ai/\">OpenMLDB</a> is an excellent open source machine learning database, providing a full-stack\nFeatureOps solution for production.</p>\n<p>OpenMLDB task plugin used to execute tasks on OpenMLDB cluster.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Cre [...]
+ "__html": "<h1 id=\"openmldb-node\">OpenMLDB Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><a href=\"https://openmldb.ai/\">OpenMLDB</a> is an excellent open source machine learning database, providing a full-stack\nFeatureOps solution for production.</p>\n<p>OpenMLDB task plugin used to execute tasks on OpenMLDB cluster.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Cre [...]
"location": [
"Introduction to Functions",
"Task",
"Openmldb"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/pigeon.json b/pages/doc/en-us/3.1.6/guide/task/pigeon.json
similarity index 94%
copy from pages/doc/en-us/3.1.5/guide/task/pigeon.json
copy to pages/doc/en-us/3.1.6/guide/task/pigeon.json
index e2d1c52fb5..891866143b 100644
--- a/pages/doc/en-us/3.1.5/guide/task/pigeon.json
+++ b/pages/doc/en-us/3.1.6/guide/task/pigeon.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"pigeon\">Pigeon</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Pigeon is a task used to trigger remote tasks, acquire logs or status by calling remote WebSocket service. It is DolphinScheduler uses a remote WebSocket service to call tasks.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Dr [...]
+ "__html": "<h1 id=\"pigeon\">Pigeon</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Pigeon is a task used to trigger remote tasks, acquire logs or status by calling remote WebSocket service. It is DolphinScheduler uses a remote WebSocket service to call tasks.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Dr [...]
"location": [
"Introduction to Functions",
"Task",
"Pigeon"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/python.json b/pages/doc/en-us/3.1.6/guide/task/python.json
similarity index 97%
copy from pages/doc/en-us/3.1.5/guide/task/python.json
copy to pages/doc/en-us/3.1.6/guide/task/python.json
index 39b79f302b..0d6c8388c6 100644
--- a/pages/doc/en-us/3.1.5/guide/task/python.json
+++ b/pages/doc/en-us/3.1.6/guide/task/python.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"python-node\">Python Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Use <code>Python Task</code> to create a python-type task and execute python scripts. When the worker executes <code>Python Task</code>,\nit will generate a temporary python script, and executes the script by the Linux user with the same name as the tenant.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, an [...]
+ "__html": "<h1 id=\"python-node\">Python Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Use <code>Python Task</code> to create a python-type task and execute python scripts. When the worker executes <code>Python Task</code>,\nit will generate a temporary python script, and executes the script by the Linux user with the same name as the tenant.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, an [...]
"location": [
"Introduction to Functions",
"Task",
"Python"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/pytorch.json b/pages/doc/en-us/3.1.6/guide/task/pytorch.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/task/pytorch.json
copy to pages/doc/en-us/3.1.6/guide/task/pytorch.json
index b9681ba582..d18bd4cc4e 100644
--- a/pages/doc/en-us/3.1.5/guide/task/pytorch.json
+++ b/pages/doc/en-us/3.1.6/guide/task/pytorch.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"pytorch-node-(experimental)\">Pytorch Node (experimental)</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><a href=\"https://pytorch.org\">Pytorch</a> is a mainstream Python machine learning library.</p>\n<p><code>Pytorch</code> task plugin enables users to run <code>Pytorch</code> projects in DolphinScheduler more conveniently. In addition, it supports handy Python environment management.</p>\n<p><code>Pytorch task plugin</code> is more than <code>Python task plugin</co [...]
+ "__html": "<h1 id=\"pytorch-node-(experimental)\">Pytorch Node (experimental)</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><a href=\"https://pytorch.org\">Pytorch</a> is a mainstream Python machine learning library.</p>\n<p><code>Pytorch</code> task plugin enables users to run <code>Pytorch</code> projects in DolphinScheduler more conveniently. In addition, it supports handy Python environment management.</p>\n<p><code>Pytorch task plugin</code> is more than <code>Python task plugin</co [...]
"location": [
"Introduction to Functions",
"Task",
"Pytorch"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/sagemaker.json b/pages/doc/en-us/3.1.6/guide/task/sagemaker.json
similarity index 97%
copy from pages/doc/en-us/3.1.5/guide/task/sagemaker.json
copy to pages/doc/en-us/3.1.6/guide/task/sagemaker.json
index 0f860bf2e6..2a5e6d8a81 100644
--- a/pages/doc/en-us/3.1.5/guide/task/sagemaker.json
+++ b/pages/doc/en-us/3.1.6/guide/task/sagemaker.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"sagemaker-node\">SageMaker Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><a href=\"https://docs.aws.amazon.com/sagemaker/index.html\">Amazon SageMaker</a> is a fully managed machine learning service. With Amazon SageMaker, data scientists and developers can quickly build and train machine learning models, and then deploy them into a production-ready hosted environment.</p>\n<p><a href=\"https://docs.aws.amazon.com/sagemaker/latest/dg/pipelines.html\">Amazon SageM [...]
+ "__html": "<h1 id=\"sagemaker-node\">SageMaker Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><a href=\"https://docs.aws.amazon.com/sagemaker/index.html\">Amazon SageMaker</a> is a fully managed machine learning service. With Amazon SageMaker, data scientists and developers can quickly build and train machine learning models, and then deploy them into a production-ready hosted environment.</p>\n<p><a href=\"https://docs.aws.amazon.com/sagemaker/latest/dg/pipelines.html\">Amazon SageM [...]
"location": [
"Introduction to Functions",
"Task",
"SageMaker"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.6/guide/task/seatunnel.json b/pages/doc/en-us/3.1.6/guide/task/seatunnel.json
new file mode 100644
index 0000000000..db091c8c34
--- /dev/null
+++ b/pages/doc/en-us/3.1.6/guide/task/seatunnel.json
@@ -0,0 +1,97 @@
+{
+ "__html": "<h1 id=\"apache-seatunnel\">Apache SeaTunnel</h1>\n<h2 id=\"overview\">Overview</h2>\n<p><code>SeaTunnel</code> task type for creating and executing <code>SeaTunnel</code> tasks. When the worker executes this task, it will parse the config file through the <code>start-seatunnel-spark.sh</code> , <code>start-seatunnel-flink.sh</code> or <code>seatunnel.sh</code> command.\nClick <a href=\"https://seatunnel.apache.org/\">here</a> for more information about <code>Apache SeaTunne [...]
+ "location": [
+ "Introduction to Functions",
+ "Task",
+ "SeaTunnel"
+ ],
+ "time": "2023-05-15",
+ "structure": [
+ {
+ "title": "Overview",
+ "children": [
+ {
+ "title": "Configuring the SeaTunnel environment in DolphinScheduler",
+ "children": [],
+ "anchor": "configuring-the-seatunnel-environment-in-dolphinscheduler"
+ },
+ {
+ "title": "Configuring SeaTunnel Task Node",
+ "children": [],
+ "anchor": "configuring-seatunnel-task-node"
+ },
+ {
+ "title": "Config example",
+ "children": [],
+ "anchor": "config-example"
+ }
+ ],
+ "anchor": "overview"
+ },
+ {
+ "title": "Create Task",
+ "children": [
+ {
+ "title": "Configuring the SeaTunnel environment in DolphinScheduler",
+ "children": [],
+ "anchor": "configuring-the-seatunnel-environment-in-dolphinscheduler"
+ },
+ {
+ "title": "Configuring SeaTunnel Task Node",
+ "children": [],
+ "anchor": "configuring-seatunnel-task-node"
+ },
+ {
+ "title": "Config example",
+ "children": [],
+ "anchor": "config-example"
+ }
+ ],
+ "anchor": "create-task"
+ },
+ {
+ "title": "Task Parameter",
+ "children": [
+ {
+ "title": "Configuring the SeaTunnel environment in DolphinScheduler",
+ "children": [],
+ "anchor": "configuring-the-seatunnel-environment-in-dolphinscheduler"
+ },
+ {
+ "title": "Configuring SeaTunnel Task Node",
+ "children": [],
+ "anchor": "configuring-seatunnel-task-node"
+ },
+ {
+ "title": "Config example",
+ "children": [],
+ "anchor": "config-example"
+ }
+ ],
+ "anchor": "task-parameter"
+ },
+ {
+ "title": "Task Example",
+ "children": [
+ {
+ "title": "Configuring the SeaTunnel environment in DolphinScheduler",
+ "children": [],
+ "anchor": "configuring-the-seatunnel-environment-in-dolphinscheduler"
+ },
+ {
+ "title": "Configuring SeaTunnel Task Node",
+ "children": [],
+ "anchor": "configuring-seatunnel-task-node"
+ },
+ {
+ "title": "Config example",
+ "children": [],
+ "anchor": "config-example"
+ }
+ ],
+ "anchor": "task-example"
+ }
+ ],
+ "title": "Apache SeaTunnel",
+ "link": "/guide/task/seatunnel"
+}
\ No newline at end of file
diff --git a/pages/doc/en-us/3.1.5/guide/task/shell.json b/pages/doc/en-us/3.1.6/guide/task/shell.json
similarity index 96%
copy from pages/doc/en-us/3.1.5/guide/task/shell.json
copy to pages/doc/en-us/3.1.6/guide/task/shell.json
index 55dc1888b1..1a01aae248 100644
--- a/pages/doc/en-us/3.1.5/guide/task/shell.json
+++ b/pages/doc/en-us/3.1.6/guide/task/shell.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"shell\">Shell</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Shell task type, used to create a shell type task and execute a series of shell scripts. When the worker executes this task, a temporary shell script is generated and executed using the linux user with the same name as the tenant.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code [...]
+ "__html": "<h1 id=\"shell\">Shell</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Shell task type, used to create a shell type task and execute a series of shell scripts. When the worker executes this task, a temporary shell script is generated and executed using the linux user with the same name as the tenant.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code [...]
"location": [
"Introduction to Functions",
"Task",
"Shell"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/spark.json b/pages/doc/en-us/3.1.6/guide/task/spark.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/task/spark.json
copy to pages/doc/en-us/3.1.6/guide/task/spark.json
index 4bf650a4ad..873ae30d39 100644
--- a/pages/doc/en-us/3.1.5/guide/task/spark.json
+++ b/pages/doc/en-us/3.1.6/guide/task/spark.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"spark-node\">Spark Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Spark task type for executing Spark application. When executing the Spark task, the worker will submits a job to the Spark cluster by following commands:</p>\n<p>(1) <code>spark submit</code> method to submit tasks. See <a href=\"https://spark.apache.org/docs/3.2.1/submitting-applications.html#launching-applications-with-spark-submit\">spark-submit</a> for more details.</p>\n<p>(2) <code>spark sql</ [...]
+ "__html": "<h1 id=\"spark-node\">Spark Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Spark task type for executing Spark application. When executing the Spark task, the worker will submits a job to the Spark cluster by following commands:</p>\n<p>(1) <code>spark submit</code> method to submit tasks. See <a href=\"https://spark.apache.org/docs/3.2.1/submitting-applications.html#launching-applications-with-spark-submit\">spark-submit</a> for more details.</p>\n<p>(2) <code>spark sql</ [...]
"location": [
"Introduction to Functions",
"Task",
"Spark"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/sql.json b/pages/doc/en-us/3.1.6/guide/task/sql.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/task/sql.json
copy to pages/doc/en-us/3.1.6/guide/task/sql.json
index 9d4c306c94..54fe315ece 100644
--- a/pages/doc/en-us/3.1.5/guide/task/sql.json
+++ b/pages/doc/en-us/3.1.6/guide/task/sql.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"sql\">SQL</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>SQL task type used to connect to databases and execute SQL.</p>\n<h2 id=\"create-datasource\">Create DataSource</h2>\n<p>Refer to <a href=\"https://github.com/apache/dolphinscheduler/blob/3.1.5-release/docs/docs/en/guide/howto/datasource-setting.md\">datasource-setting</a> <code>DataSource Center</code> section</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Na [...]
+ "__html": "<h1 id=\"sql\">SQL</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>SQL task type used to connect to databases and execute SQL.</p>\n<h2 id=\"create-datasource\">Create DataSource</h2>\n<p>Refer to <a href=\"https://github.com/apache/dolphinscheduler/blob/3.1.6-release/docs/docs/en/guide/howto/datasource-setting.md\">datasource-setting</a> <code>DataSource Center</code> section</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Na [...]
"location": [
"Introduction to Functions",
"Task",
"SQL"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/stored-procedure.json b/pages/doc/en-us/3.1.6/guide/task/stored-procedure.json
similarity index 95%
copy from pages/doc/en-us/3.1.5/guide/task/stored-procedure.json
copy to pages/doc/en-us/3.1.6/guide/task/stored-procedure.json
index d71b0a2546..7728378fb5 100644
--- a/pages/doc/en-us/3.1.5/guide/task/stored-procedure.json
+++ b/pages/doc/en-us/3.1.6/guide/task/stored-procedure.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"stored-procedure\">Stored Procedure</h1>\n<ul>\n<li>Execute the stored procedure according to the selected DataSource.</li>\n</ul>\n<blockquote>\n<p>Drag from the <code>PROCEDURE</code> task node into the canvas, as shown in the figure below:</p>\n</blockquote>\n<p align=\"center\">\n <img src=\"/img/procedure_edit.png\" width=\"80%\" />\n </p>\n<h2 id=\"task-parameters\">Task Parameters</h2>\n<ul>\n<li>Please refer to <a href=\"/en-us/docs/3.1.5/guide/task/append [...]
+ "__html": "<h1 id=\"stored-procedure\">Stored Procedure</h1>\n<ul>\n<li>Execute the stored procedure according to the selected DataSource.</li>\n</ul>\n<blockquote>\n<p>Drag from the <code>PROCEDURE</code> task node into the canvas, as shown in the figure below:</p>\n</blockquote>\n<p align=\"center\">\n <img src=\"/img/procedure_edit.png\" width=\"80%\" />\n </p>\n<h2 id=\"task-parameters\">Task Parameters</h2>\n<ul>\n<li>Please refer to <a href=\"/en-us/docs/3.1.6/guide/task/append [...]
"location": [
"Introduction to Functions",
"Task",
"Stored Procedure"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Task Parameters",
diff --git a/pages/doc/en-us/3.1.5/guide/task/sub-process.json b/pages/doc/en-us/3.1.6/guide/task/sub-process.json
similarity index 96%
copy from pages/doc/en-us/3.1.5/guide/task/sub-process.json
copy to pages/doc/en-us/3.1.6/guide/task/sub-process.json
index dfb9cf337f..b6a83b4af9 100644
--- a/pages/doc/en-us/3.1.5/guide/task/sub-process.json
+++ b/pages/doc/en-us/3.1.6/guide/task/sub-process.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"subprocess-node\">SubProcess Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>The sub-process node is to execute an external workflow definition as a task node.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Drag from the toolbar <img src=\"/img/tasks/icons/sub_process.png\" width=\"15 [...]
+ "__html": "<h1 id=\"subprocess-node\">SubProcess Node</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>The sub-process node is to execute an external workflow definition as a task node.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> Project Name -> Workflow Definition</code>, and click the <code>Create Workflow</code> button to enter the DAG editing page.</li>\n<li>Drag from the toolbar <img src=\"/img/tasks/icons/sub_process.png\" width=\"15 [...]
"location": [
"Introduction to Functions",
"Task",
"SubProcess"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/switch.json b/pages/doc/en-us/3.1.6/guide/task/switch.json
similarity index 95%
copy from pages/doc/en-us/3.1.5/guide/task/switch.json
copy to pages/doc/en-us/3.1.6/guide/task/switch.json
index daa9287f2b..9bdec57218 100644
--- a/pages/doc/en-us/3.1.5/guide/task/switch.json
+++ b/pages/doc/en-us/3.1.6/guide/task/switch.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"switch\">Switch</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>The switch is a conditional judgment node, decide the branch executes according to the value of <a href=\"../parameter//en-us/docs/3.1.5/guide/parameter/global\">global variable</a> and the expression result written by the user.</p>\n<p><strong>Note</strong>: Execute expressions using javax.script.ScriptEngine.eval.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> [...]
+ "__html": "<h1 id=\"switch\">Switch</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>The switch is a conditional judgment node, decide the branch executes according to the value of <a href=\"../parameter//en-us/docs/3.1.6/guide/parameter/global\">global variable</a> and the expression result written by the user.</p>\n<p><strong>Note</strong>: Execute expressions using javax.script.ScriptEngine.eval.</p>\n<h2 id=\"create-task\">Create Task</h2>\n<ul>\n<li>Click <code>Project Management -> [...]
"location": [
"Introduction to Functions",
"Task",
"Switch"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/task/zeppelin.json b/pages/doc/en-us/3.1.6/guide/task/zeppelin.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/task/zeppelin.json
copy to pages/doc/en-us/3.1.6/guide/task/zeppelin.json
index a3f27f6ec1..6736d0ce5d 100644
--- a/pages/doc/en-us/3.1.5/guide/task/zeppelin.json
+++ b/pages/doc/en-us/3.1.6/guide/task/zeppelin.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"apache-zeppelin\">Apache Zeppelin</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Use <code>Zeppelin Task</code> to create a zeppelin-type task and execute zeppelin notebook paragraphs. When the worker executes <code>Zeppelin Task</code>,\nit will call <code>Zeppelin Client API</code> to trigger zeppelin notebook paragraph. Click <a href=\"https://zeppelin.apache.org/\">here</a> for details about <code>Apache Zeppelin Notebook</code>.</p>\n<h2 id=\"create-task\">Create [...]
+ "__html": "<h1 id=\"apache-zeppelin\">Apache Zeppelin</h1>\n<h2 id=\"overview\">Overview</h2>\n<p>Use <code>Zeppelin Task</code> to create a zeppelin-type task and execute zeppelin notebook paragraphs. When the worker executes <code>Zeppelin Task</code>,\nit will call <code>Zeppelin Client API</code> to trigger zeppelin notebook paragraph. Click <a href=\"https://zeppelin.apache.org/\">here</a> for details about <code>Apache Zeppelin Notebook</code>.</p>\n<h2 id=\"create-task\">Create [...]
"location": [
"Introduction to Functions",
"Task",
"Apache Zeppelin"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Overview",
diff --git a/pages/doc/en-us/3.1.5/guide/upgrade/incompatible.json b/pages/doc/en-us/3.1.6/guide/upgrade/incompatible.json
similarity index 98%
copy from pages/doc/en-us/3.1.5/guide/upgrade/incompatible.json
copy to pages/doc/en-us/3.1.6/guide/upgrade/incompatible.json
index d863832edb..0c707e991b 100644
--- a/pages/doc/en-us/3.1.5/guide/upgrade/incompatible.json
+++ b/pages/doc/en-us/3.1.6/guide/upgrade/incompatible.json
@@ -5,7 +5,7 @@
"Upgrade",
"Incompatible"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "dev",
diff --git a/pages/doc/en-us/3.1.5/guide/upgrade/upgrade.json b/pages/doc/en-us/3.1.6/guide/upgrade/upgrade.json
similarity index 99%
copy from pages/doc/en-us/3.1.5/guide/upgrade/upgrade.json
copy to pages/doc/en-us/3.1.6/guide/upgrade/upgrade.json
index b39c8e69c0..d9c5e561d2 100644
--- a/pages/doc/en-us/3.1.5/guide/upgrade/upgrade.json
+++ b/pages/doc/en-us/3.1.6/guide/upgrade/upgrade.json
@@ -1,11 +1,11 @@
{
- "__html": "<h1 id=\"dolphinscheduler-upgrade\">DolphinScheduler Upgrade</h1>\n<h2 id=\"prepare\">Prepare</h2>\n<h3 id=\"check-incompatible-change\">Check Incompatible Change</h3>\n<p>You should check <a href=\"/en-us/docs/3.1.5/guide/upgrade/incompatible\">incompatible change</a> before you upgrade, because some incompatible change may break your current function.</p>\n<h3 id=\"backup-previous-version's-files-and-database\">Backup Previous Version's Files and Database</h3>\n<p>To preve [...]
+ "__html": "<h1 id=\"dolphinscheduler-upgrade\">DolphinScheduler Upgrade</h1>\n<h2 id=\"prepare\">Prepare</h2>\n<h3 id=\"check-incompatible-change\">Check Incompatible Change</h3>\n<p>You should check <a href=\"/en-us/docs/3.1.6/guide/upgrade/incompatible\">incompatible change</a> before you upgrade, because some incompatible change may break your current function.</p>\n<h3 id=\"backup-previous-version's-files-and-database\">Backup Previous Version's Files and Database</h3>\n<p>To preve [...]
"location": [
"Introduction to Functions",
"Upgrade",
"Upgrade"
],
- "time": "2023-4-6",
+ "time": "2023-05-15",
"structure": [
{
"title": "Prepare",
diff --git a/pages/doc/zh-cn/3.1.5/DSIP.json b/pages/doc/zh-cn/3.1.5/DSIP.json
index 4bab353d0a..21da34cf6c 100644
--- a/pages/doc/zh-cn/3.1.5/DSIP.json
+++ b/pages/doc/zh-cn/3.1.5/DSIP.json
@@ -4,7 +4,7 @@
"DSIP",
"DSIP"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "怎样的修改应该被认定为 DSIP",
diff --git a/pages/doc/zh-cn/3.1.5/about/features.json b/pages/doc/zh-cn/3.1.5/about/features.json
index 456db5d5d5..b4d9adef3b 100644
--- a/pages/doc/zh-cn/3.1.5/about/features.json
+++ b/pages/doc/zh-cn/3.1.5/about/features.json
@@ -4,7 +4,7 @@
"关于Apache DolphinScheduler",
"特性"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "简单易用",
diff --git a/pages/doc/zh-cn/3.1.5/about/glossary.json b/pages/doc/zh-cn/3.1.5/about/glossary.json
index f830bcb8eb..b42b7ad75c 100644
--- a/pages/doc/zh-cn/3.1.5/about/glossary.json
+++ b/pages/doc/zh-cn/3.1.5/about/glossary.json
@@ -4,7 +4,7 @@
"关于Apache DolphinScheduler",
"名词解释"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "名词解释",
diff --git a/pages/doc/zh-cn/3.1.5/about/hardware.json b/pages/doc/zh-cn/3.1.5/about/hardware.json
index 060c3b4b57..dc7cb4cd85 100644
--- a/pages/doc/zh-cn/3.1.5/about/hardware.json
+++ b/pages/doc/zh-cn/3.1.5/about/hardware.json
@@ -4,7 +4,7 @@
"关于Apache DolphinScheduler",
"建议配置"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "1. Linux 操作系统版本要求",
diff --git a/pages/doc/zh-cn/3.1.5/about/introduction.json b/pages/doc/zh-cn/3.1.5/about/introduction.json
index dddf670a2d..c9fde4dbcb 100644
--- a/pages/doc/zh-cn/3.1.5/about/introduction.json
+++ b/pages/doc/zh-cn/3.1.5/about/introduction.json
@@ -4,7 +4,7 @@
"关于Apache DolphinScheduler",
"简介"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "关于DolphinScheduler",
"link": "/about/introduction"
diff --git a/pages/doc/zh-cn/3.1.5/architecture/cache.json b/pages/doc/zh-cn/3.1.5/architecture/cache.json
index 8e7d226340..9b4294e2c5 100644
--- a/pages/doc/zh-cn/3.1.5/architecture/cache.json
+++ b/pages/doc/zh-cn/3.1.5/architecture/cache.json
@@ -4,7 +4,7 @@
"架构设计",
"缓存"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "缓存",
diff --git a/pages/doc/zh-cn/3.1.5/architecture/configuration.json b/pages/doc/zh-cn/3.1.5/architecture/configuration.json
index 9ff9251657..69750950f2 100644
--- a/pages/doc/zh-cn/3.1.5/architecture/configuration.json
+++ b/pages/doc/zh-cn/3.1.5/architecture/configuration.json
@@ -4,7 +4,7 @@
"架构设计",
"配置文件"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "dolphinscheduler-daemon.sh [启动/关闭DolphinScheduler服务脚本]",
diff --git a/pages/doc/zh-cn/3.1.5/architecture/design.json b/pages/doc/zh-cn/3.1.5/architecture/design.json
index f47f882e76..83f01b78e6 100644
--- a/pages/doc/zh-cn/3.1.5/architecture/design.json
+++ b/pages/doc/zh-cn/3.1.5/architecture/design.json
@@ -4,7 +4,7 @@
"架构设计",
"架构设计"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "系统架构",
diff --git a/pages/doc/zh-cn/3.1.5/architecture/load-balance.json b/pages/doc/zh-cn/3.1.5/architecture/load-balance.json
index 2d406e6e13..cd59379df2 100644
--- a/pages/doc/zh-cn/3.1.5/architecture/load-balance.json
+++ b/pages/doc/zh-cn/3.1.5/architecture/load-balance.json
@@ -4,7 +4,7 @@
"架构设计",
"负载均衡"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "负载均衡",
diff --git a/pages/doc/zh-cn/3.1.5/architecture/metadata.json b/pages/doc/zh-cn/3.1.5/architecture/metadata.json
index f20f35ce12..8ec3075c94 100644
--- a/pages/doc/zh-cn/3.1.5/architecture/metadata.json
+++ b/pages/doc/zh-cn/3.1.5/architecture/metadata.json
@@ -4,7 +4,7 @@
"架构设计",
"元数据文档"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "表Schema",
diff --git a/pages/doc/zh-cn/3.1.5/architecture/task-structure.json b/pages/doc/zh-cn/3.1.5/architecture/task-structure.json
index b527ea5c5d..fcd713e18d 100644
--- a/pages/doc/zh-cn/3.1.5/architecture/task-structure.json
+++ b/pages/doc/zh-cn/3.1.5/architecture/task-structure.json
@@ -4,7 +4,7 @@
"架构设计",
"任务结构"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "Shell节点",
diff --git a/pages/doc/zh-cn/3.1.5/contribute/backend/spi/alert.json b/pages/doc/zh-cn/3.1.5/contribute/backend/spi/alert.json
index c917edbd16..fd8a81f611 100644
--- a/pages/doc/zh-cn/3.1.5/contribute/backend/spi/alert.json
+++ b/pages/doc/zh-cn/3.1.5/contribute/backend/spi/alert.json
@@ -5,7 +5,7 @@
"SPI",
"Alert SPI"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "DolphinScheduler Alert SPI 主要设计",
diff --git a/pages/doc/zh-cn/3.1.5/contribute/backend/spi/datasource.json b/pages/doc/zh-cn/3.1.5/contribute/backend/spi/datasource.json
index 97d2a03d01..d5d6786e19 100644
--- a/pages/doc/zh-cn/3.1.5/contribute/backend/spi/datasource.json
+++ b/pages/doc/zh-cn/3.1.5/contribute/backend/spi/datasource.json
@@ -5,7 +5,7 @@
"SPI",
"Datasource SPI"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "DolphinScheduler Datasource SPI 主要设计",
diff --git a/pages/doc/zh-cn/3.1.5/contribute/backend/spi/registry.json b/pages/doc/zh-cn/3.1.5/contribute/backend/spi/registry.json
index a1fc6d16ca..9045bf04f6 100644
--- a/pages/doc/zh-cn/3.1.5/contribute/backend/spi/registry.json
+++ b/pages/doc/zh-cn/3.1.5/contribute/backend/spi/registry.json
@@ -5,7 +5,7 @@
"SPI",
"Registry SPI"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "DolphinScheduler Registry SPI 扩展",
diff --git a/pages/doc/zh-cn/3.1.5/contribute/backend/spi/task.json b/pages/doc/zh-cn/3.1.5/contribute/backend/spi/task.json
index 6db7447f08..d733f4dbd1 100644
--- a/pages/doc/zh-cn/3.1.5/contribute/backend/spi/task.json
+++ b/pages/doc/zh-cn/3.1.5/contribute/backend/spi/task.json
@@ -5,7 +5,7 @@
"SPI",
"Task SPI"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "DolphinScheduler Task SPI 扩展",
diff --git a/pages/doc/zh-cn/3.1.5/contribute/development-environment-setup.json b/pages/doc/zh-cn/3.1.5/contribute/development-environment-setup.json
index 31012c8a2d..01c911ab7d 100644
--- a/pages/doc/zh-cn/3.1.5/contribute/development-environment-setup.json
+++ b/pages/doc/zh-cn/3.1.5/contribute/development-environment-setup.json
@@ -4,7 +4,7 @@
"贡献指南",
"环境搭建"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "软件要求",
diff --git a/pages/doc/zh-cn/3.1.5/contribute/frontend-development.json b/pages/doc/zh-cn/3.1.5/contribute/frontend-development.json
index 6920eff4da..fe9522f248 100644
--- a/pages/doc/zh-cn/3.1.5/contribute/frontend-development.json
+++ b/pages/doc/zh-cn/3.1.5/contribute/frontend-development.json
@@ -4,7 +4,7 @@
"贡献指南",
"前端开发"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "路由和状态管理",
diff --git a/pages/doc/zh-cn/3.1.5/guide/alert/alert_plugin_user_guide.json b/pages/doc/zh-cn/3.1.5/guide/alert/alert_plugin_user_guide.json
index 412f54edbc..afe457f0ce 100644
--- a/pages/doc/zh-cn/3.1.5/guide/alert/alert_plugin_user_guide.json
+++ b/pages/doc/zh-cn/3.1.5/guide/alert/alert_plugin_user_guide.json
@@ -5,7 +5,7 @@
"告警",
"告警组件向导"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "如何创建告警插件以及告警组",
diff --git a/pages/doc/zh-cn/3.1.5/guide/alert/dingtalk.json b/pages/doc/zh-cn/3.1.5/guide/alert/dingtalk.json
index c032dda27e..5596b81333 100644
--- a/pages/doc/zh-cn/3.1.5/guide/alert/dingtalk.json
+++ b/pages/doc/zh-cn/3.1.5/guide/alert/dingtalk.json
@@ -5,7 +5,7 @@
"告警",
"钉钉告警"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "钉钉",
"link": "/guide/alert/dingtalk"
diff --git a/pages/doc/zh-cn/3.1.5/guide/alert/email.json b/pages/doc/zh-cn/3.1.5/guide/alert/email.json
index 067deb9fdf..b6c57c09b5 100644
--- a/pages/doc/zh-cn/3.1.5/guide/alert/email.json
+++ b/pages/doc/zh-cn/3.1.5/guide/alert/email.json
@@ -5,7 +5,7 @@
"告警",
"Email"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "Email",
"link": "/guide/alert/email"
diff --git a/pages/doc/zh-cn/3.1.5/guide/alert/enterprise-webexteams.json b/pages/doc/zh-cn/3.1.5/guide/alert/enterprise-webexteams.json
index 0d6344136f..0bbab295c2 100644
--- a/pages/doc/zh-cn/3.1.5/guide/alert/enterprise-webexteams.json
+++ b/pages/doc/zh-cn/3.1.5/guide/alert/enterprise-webexteams.json
@@ -5,7 +5,7 @@
"告警",
"Webexteams"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "参数配置",
diff --git a/pages/doc/zh-cn/3.1.5/guide/alert/enterprise-wechat.json b/pages/doc/zh-cn/3.1.5/guide/alert/enterprise-wechat.json
index b8abb4cdc7..35e9d09bed 100644
--- a/pages/doc/zh-cn/3.1.5/guide/alert/enterprise-wechat.json
+++ b/pages/doc/zh-cn/3.1.5/guide/alert/enterprise-wechat.json
@@ -5,7 +5,7 @@
"告警",
"企业微信"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "发送类型",
diff --git a/pages/doc/zh-cn/3.1.5/guide/alert/feishu.json b/pages/doc/zh-cn/3.1.5/guide/alert/feishu.json
index 2687c69a1d..02e856371e 100644
--- a/pages/doc/zh-cn/3.1.5/guide/alert/feishu.json
+++ b/pages/doc/zh-cn/3.1.5/guide/alert/feishu.json
@@ -5,7 +5,7 @@
"告警",
"飞书告警"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "飞书",
"link": "/guide/alert/feishu"
diff --git a/pages/doc/zh-cn/3.1.5/guide/alert/http.json b/pages/doc/zh-cn/3.1.5/guide/alert/http.json
index 451f7aea38..0bd01fb26a 100644
--- a/pages/doc/zh-cn/3.1.5/guide/alert/http.json
+++ b/pages/doc/zh-cn/3.1.5/guide/alert/http.json
@@ -5,7 +5,7 @@
"告警",
"Http告警"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "参数配置",
diff --git a/pages/doc/zh-cn/3.1.5/guide/alert/script.json b/pages/doc/zh-cn/3.1.5/guide/alert/script.json
index 1c66e65a9b..1f1b96b29c 100644
--- a/pages/doc/zh-cn/3.1.5/guide/alert/script.json
+++ b/pages/doc/zh-cn/3.1.5/guide/alert/script.json
@@ -5,7 +5,7 @@
"告警",
"脚本告警"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "Script脚本",
"link": "/guide/alert/script"
diff --git a/pages/doc/zh-cn/3.1.5/guide/alert/telegram.json b/pages/doc/zh-cn/3.1.5/guide/alert/telegram.json
index 40631323e0..68530d9769 100644
--- a/pages/doc/zh-cn/3.1.5/guide/alert/telegram.json
+++ b/pages/doc/zh-cn/3.1.5/guide/alert/telegram.json
@@ -5,7 +5,7 @@
"告警",
"Telegram"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "Telegram",
"link": "/guide/alert/telegram"
diff --git a/pages/doc/zh-cn/3.1.5/guide/api/healthcheck.json b/pages/doc/zh-cn/3.1.5/guide/api/healthcheck.json
index 92da2d86bd..81f527dc9c 100644
--- a/pages/doc/zh-cn/3.1.5/guide/api/healthcheck.json
+++ b/pages/doc/zh-cn/3.1.5/guide/api/healthcheck.json
@@ -4,7 +4,7 @@
"API",
"健康检查"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "背景",
diff --git a/pages/doc/zh-cn/3.1.5/guide/api/open-api.json b/pages/doc/zh-cn/3.1.5/guide/api/open-api.json
index 36eda2428d..63bcc8e0bd 100644
--- a/pages/doc/zh-cn/3.1.5/guide/api/open-api.json
+++ b/pages/doc/zh-cn/3.1.5/guide/api/open-api.json
@@ -4,7 +4,7 @@
"API",
"API调用"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "背景",
diff --git a/pages/doc/zh-cn/3.1.5/guide/api/pydolphinscheduler.json b/pages/doc/zh-cn/3.1.5/guide/api/pydolphinscheduler.json
index b6c080cfa3..74c40117bc 100644
--- a/pages/doc/zh-cn/3.1.5/guide/api/pydolphinscheduler.json
+++ b/pages/doc/zh-cn/3.1.5/guide/api/pydolphinscheduler.json
@@ -4,7 +4,7 @@
"API",
"PyDolphinScheduler"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "PyDolphinScheduler",
"link": "/guide/api/pydolphinscheduler"
diff --git a/pages/doc/zh-cn/3.1.5/guide/data-quality.json b/pages/doc/zh-cn/3.1.5/guide/data-quality.json
index 024407c045..61649a7cfe 100644
--- a/pages/doc/zh-cn/3.1.5/guide/data-quality.json
+++ b/pages/doc/zh-cn/3.1.5/guide/data-quality.json
@@ -4,7 +4,7 @@
"功能介绍",
"数据质量"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "任务类型介绍",
diff --git a/pages/doc/zh-cn/3.1.5/guide/datasource/athena.json b/pages/doc/zh-cn/3.1.5/guide/datasource/athena.json
index 26887144d7..50b6b4e1c4 100644
--- a/pages/doc/zh-cn/3.1.5/guide/datasource/athena.json
+++ b/pages/doc/zh-cn/3.1.5/guide/datasource/athena.json
@@ -5,7 +5,7 @@
"数据源中心",
"Amazon Athena"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "是否原生支持",
diff --git a/pages/doc/zh-cn/3.1.5/guide/datasource/hive.json b/pages/doc/zh-cn/3.1.5/guide/datasource/hive.json
index 6a0e668bdc..a5ec2614d6 100644
--- a/pages/doc/zh-cn/3.1.5/guide/datasource/hive.json
+++ b/pages/doc/zh-cn/3.1.5/guide/datasource/hive.json
@@ -5,7 +5,7 @@
"数据源中心",
"HIVE"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "使用HiveServer2",
diff --git a/pages/doc/zh-cn/3.1.5/guide/datasource/mysql.json b/pages/doc/zh-cn/3.1.5/guide/datasource/mysql.json
index fc4985dd8f..a046109f13 100644
--- a/pages/doc/zh-cn/3.1.5/guide/datasource/mysql.json
+++ b/pages/doc/zh-cn/3.1.5/guide/datasource/mysql.json
@@ -5,7 +5,7 @@
"数据源中心",
"MySQL"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "是否原生支持",
diff --git a/pages/doc/zh-cn/3.1.5/guide/datasource/postgresql.json b/pages/doc/zh-cn/3.1.5/guide/datasource/postgresql.json
index c3bec105cd..0d62749017 100644
--- a/pages/doc/zh-cn/3.1.5/guide/datasource/postgresql.json
+++ b/pages/doc/zh-cn/3.1.5/guide/datasource/postgresql.json
@@ -5,7 +5,7 @@
"数据源中心",
"PostgreSQL"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "是否原生支持",
diff --git a/pages/doc/zh-cn/3.1.5/guide/datasource/spark.json b/pages/doc/zh-cn/3.1.5/guide/datasource/spark.json
index b4e1e954a7..906bbe83e4 100644
--- a/pages/doc/zh-cn/3.1.5/guide/datasource/spark.json
+++ b/pages/doc/zh-cn/3.1.5/guide/datasource/spark.json
@@ -5,7 +5,7 @@
"数据源中心",
"Spark"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "是否原生支持",
diff --git a/pages/doc/zh-cn/3.1.5/guide/expansion-reduction.json b/pages/doc/zh-cn/3.1.5/guide/expansion-reduction.json
index 990ad813fb..9a56398850 100644
--- a/pages/doc/zh-cn/3.1.5/guide/expansion-reduction.json
+++ b/pages/doc/zh-cn/3.1.5/guide/expansion-reduction.json
@@ -4,7 +4,7 @@
"功能介绍",
"扩/缩容"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "1. DolphinScheduler扩容文档",
diff --git a/pages/doc/zh-cn/3.1.5/guide/homepage.json b/pages/doc/zh-cn/3.1.5/guide/homepage.json
index 03a8bcc15f..8b7d3d4f4e 100644
--- a/pages/doc/zh-cn/3.1.5/guide/homepage.json
+++ b/pages/doc/zh-cn/3.1.5/guide/homepage.json
@@ -4,7 +4,7 @@
"功能介绍",
"应用首页"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [],
"title": "首页",
"link": "/guide/homepage"
diff --git a/pages/doc/zh-cn/3.1.5/guide/installation/cluster.json b/pages/doc/zh-cn/3.1.5/guide/installation/cluster.json
index a1cc21c101..b959ba733a 100644
--- a/pages/doc/zh-cn/3.1.5/guide/installation/cluster.json
+++ b/pages/doc/zh-cn/3.1.5/guide/installation/cluster.json
@@ -4,7 +4,7 @@
"部署指南",
"集群部署(Cluster)"
],
- "time": "2023-4-6",
+ "time": "2023-04-06",
"structure": [
{
"title": "部署步骤",
diff --git a/pages/doc/zh-cn/3.1.5/guide/installation/kubernetes.json b/pages/doc/zh-cn/3.1.5/guide/installation/kubernetes.json
index 72716d69cf..cf3d00df0d 100644
--- a/pages/doc/zh-cn/3.1.5/guide/installation/kubernetes.json
+++ b/pages/doc/zh-cn/3.1.5/guide/installation/kubernetes.json
@@ -4,7 +4,7 @@
"部署指南",
... 2756 lines suppressed ...