You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@linkis.apache.org by ca...@apache.org on 2022/07/28 13:37:45 UTC
[incubator-linkis-website] branch dev updated: Fix some irregular doc names (#460)
This is an automated email from the ASF dual-hosted git repository.
casion pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/incubator-linkis-website.git
The following commit(s) were added to refs/heads/dev by this push:
new 6beecd0991 Fix some irregular doc names (#460)
6beecd0991 is described below
commit 6beecd0991da241c5a332bff960f770194f54239
Author: Beacontownfc <89...@users.noreply.github.com>
AuthorDate: Thu Jul 28 21:37:40 2022 +0800
Fix some irregular doc names (#460)
* fix markdown name
---
blog/2022-02-21-linkis-deploy.md | 6 +-
...2022-04-15-how-to-download-engineconn-plugin.md | 2 +-
.../{exception_catch.md => exception-catch.md} | 0
community/development_specification/overview.md | 10 +-
.../{path_usage.md => path-usage.md} | 0
...ecification.md => programming-specification.md} | 0
.../{unit_test.md => unit-test.md} | 0
...ations.md => version-feature-specifications.md} | 2 +-
community/how-to-contribute-to-website.md | 2 +-
community/how-to-contribute.md | 2 +-
docs/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
docs/api/{login_api.md => login-api.md} | 0
docs/api/overview.md | 6 +-
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
...gine_conn_history.md => engine-conn-history.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...gine_conn_metrics.md => engine-conn-metrics.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
.../{proxy_user.md => proxy-user.md} | 0
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
docs/architecture/overview.md | 2 +-
...engine_bml_dissect.md => engine-bml-dissect.md} | 0
...rvice_cleanup.md => content-service-cleanup.md} | 0
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
...datasource_manager.md => datasource-manager.md} | 0
.../{metadata_manager.md => metadata-manager.md} | 0
.../{public_service.md => public-service.md} | 0
...cluster_deployment.md => cluster-deployment.md} | 0
...thout_hdfs.md => deploy-linkis-without-hdfs.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
...to_linkis.md => involve-knife4j-into-linkis.md} | 0
...linkis.md => involve-prometheus-into-linkis.md} | 0
...linkis.md => involve-skywalking-into-linkis.md} | 0
...iptis_install.md => linkis-scriptis-install.md} | 2 +-
.../{quick_deploy.md => quick-deploy.md} | 2 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
...t_metadatasource.md => start-metadatasource.md} | 0
...ructure.md => unpack-hierarchical-structure.md} | 0
.../deployment/web-install.md | 2 +-
.../development/linkis-compile-and-package.md | 2 +-
.../{linkis_config.md => linkis-config.md} | 0
...nkis_debug_in_mac.md => linkis-debug-in-mac.md} | 0
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
...ger_instructions.md => swwager-instructions.md} | 0
docs/development/{web_build.md => web-build.md} | 0
docs/engine_usage/flink.md | 6 +-
docs/engine_usage/hive.md | 8 +-
docs/engine_usage/jdbc.md | 4 +-
docs/engine_usage/openlookeng.md | 6 +-
docs/engine_usage/pipeline.md | 4 +-
docs/engine_usage/python.md | 4 +-
docs/engine_usage/shell.md | 4 +-
docs/engine_usage/spark.md | 8 +-
docs/engine_usage/sqoop.md | 2 +-
docs/introduction.md | 4 +-
docs/release.md | 8 +-
.../_category_.json | 0
.../configuration.md | 0
.../overview.md | 2 +-
.../tuning.md | 0
...0_guide.md => upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../upgrade/{upgrade_guide.md => upgrade-guide.md} | 2 +-
.../{console_manual.md => console-manual.md} | 0
docs/user_guide/{how_to_use.md => how-to-use.md} | 6 +-
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
docs/user_guide/overview.md | 8 +-
docs/user_guide/{sdk_manual.md => sdk-manual.md} | 0
download/main.md | 2 +-
.../2022-02-08-how-to-user-blog.md | 2 +-
.../2022-02-21-linkis-deploy.md | 6 +-
...2022-04-15-how-to-download-engineconn-plugin.md | 2 +-
.../2022-05-12-release-1.1.1.md | 4 +-
.../{exception_catch.md => exception-catch.md} | 0
.../current/development_specification/overview.md | 10 +-
.../{path_usage.md => path-usage.md} | 0
...ecification.md => programming-specification.md} | 0
.../{unit_test.md => unit-test.md} | 0
...ations.md => version-feature-specifications.md} | 0
.../current/how-to-contribute-to-website.md | 2 +-
.../current/main.md | 2 +-
.../current/main.md | 4 +-
.../current/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../current/api/{login_api.md => login-api.md} | 0
.../current/api/overview.md | 6 +-
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
...gine_conn_history.md => engine-conn-history.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...gine_conn_metrics.md => engine-conn-metrics.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
.../{proxy_user.md => proxy-user.md} | 0
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
.../current/architecture/overview.md | 2 +-
...engine_bml_dissect.md => engine-bml-dissect.md} | 0
...rvice_cleanup.md => content-service-cleanup.md} | 0
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
...datasource_manager.md => datasource-manager.md} | 0
.../{metadata_manager.md => metadata-manager.md} | 0
.../{public_service.md => public-service.md} | 0
.../deployment/cluster-deployment.md} | 2 +-
...thout_hdfs.md => deploy-linkis-without-hdfs.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
...to_linkis.md => involve-knife4j-into-linkis.md} | 0
...linkis.md => involve-prometheus-into-linkis.md} | 0
...linkis.md => involve-skywalking-into-linkis.md} | 0
.../deployment/linkis-scriptis-install.md} | 2 +-
.../{quick_deploy.md => quick-deploy.md} | 12 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
...t_metadatasource.md => start-metadatasource.md} | 0
...ructure.md => unpack-hierarchical-structure.md} | 0
.../deployment/web-install.md} | 4 +-
.../development/linkis-compile-and-package.md} | 2 +-
.../{linkis_config.md => linkis-config.md} | 0
...nkis_debug_in_mac.md => linkis-debug-in-mac.md} | 0
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
...ger_instructions.md => swwager-instructions.md} | 0
.../development/{web_build.md => web-build.md} | 2 +-
.../current/engine_usage/elasticsearch.md | 2 +-
.../current/engine_usage/flink.md | 6 +-
.../current/engine_usage/hive.md | 8 +-
.../current/engine_usage/jdbc.md | 6 +-
.../current/engine_usage/openlookeng.md | 6 +-
.../current/engine_usage/pipeline.md | 4 +-
.../current/engine_usage/presto.md | 2 +-
.../current/engine_usage/python.md | 4 +-
.../current/engine_usage/shell.md | 4 +-
.../current/engine_usage/spark.md | 8 +-
.../current/engine_usage/sqoop.md | 2 +-
.../current/introduction.md | 2 +-
.../current/release.md | 8 +-
.../current/tuning_and_troubleshooting/overview.md | 2 +-
.../upgrade/upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../upgrade/upgrade-guide.md} | 2 +-
.../{console_manual.md => console-manual.md} | 0
.../user_guide/how-to-use.md} | 6 +-
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../current/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
.../api/{login_api.md => login-api.md} | 0
.../api/{rest_api.md => rest-api.md} | 0
.../api/{web_socket.md => web-socket.md} | 0
...real-time_log_push.md => real-time-log-push.md} | 0
.../version-0.11.0/architecture/overview.md | 4 +-
.../storage/{file_system.md => file-system.md} | 0
...d => remote-file-system-architecture-design.md} | 2 +-
.../{resultset_file.md => resultset-file.md} | 0
..._thread_pool.md => asynchronous-thread-pool.md} | 0
...ture.md => file-import-and-export-structure.md} | 0
.../ujes/{ujes_design.md => ujes-design.md} | 2 +-
...ation.md => engine-conn-plugin-installation.md} | 0
...t _guide.md => production-deployment -guide.md} | 0
.../{quick_deploy.md => quick-deploy.md} | 0
.../deployment/{quick_start.md => quick-start.md} | 2 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
...mpile_and_package.md => compile-and-package.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../version-0.11.0/engine_usage/python.md | 2 +-
.../version-0.11.0/engine_usage/spark.md | 2 +-
...ide.md => upgrade-from-0.9.0-to-0.9.1-guide.md} | 0
.../{0.X_sdk_manual.md => 0.X-sdk-manual.md} | 0
.../{1.0_sdk_manual.md => 1.0-sdk-manual.md} | 0
.../version-1.0.2/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../api/{login_api.md => login-api.md} | 0
.../version-1.0.2/api/overview.md | 6 +-
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
.../{message_scheduler.md => message-scheduler.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../version-1.0.2/architecture/overview.md | 2 +-
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
.../{public_service.md => public-service.md} | 0
...cluster_deployment.md => cluster-deployment.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
.../{quick_deploy.md => quick-deploy.md} | 14 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
.../deployment/{web_install.md => web-install.md} | 2 +-
...nd_package.md => linkis-compile-and-package.md} | 2 +-
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../development/{web_build.md => web-build.md} | 0
.../version-1.0.2/engine_usage/hive.md | 8 +-
.../version-1.0.2/engine_usage/jdbc.md | 4 +-
.../version-1.0.2/engine_usage/python.md | 4 +-
.../version-1.0.2/engine_usage/shell.md | 4 +-
.../version-1.0.2/engine_usage/spark.md | 8 +-
.../version-1.0.2/introduction.md | 4 +-
.../tuning_and_troubleshooting/overview.md | 2 +-
.../version-1.0.2/upgrade/overview.md | 2 +-
...0_guide.md => upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../{console_manual.md => console-manual.md} | 0
.../user_guide/how-to-use.md} | 6 +-
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../version-1.0.2/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
.../version-1.0.3/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../api/{login_api.md => login-api.md} | 0
.../version-1.0.3/api/overview.md | 6 +-
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
.../{message_scheduler.md => message-scheduler.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../version-1.0.3/architecture/overview.md | 2 +-
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
.../{public_service.md => public-service.md} | 0
...cluster_deployment.md => cluster-deployment.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
.../{quick_deploy.md => quick-deploy.md} | 14 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
.../deployment/{web_install.md => web-install.md} | 2 +-
...nd_package.md => linkis-compile-and-package.md} | 2 +-
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../development/{web_build.md => web-build.md} | 0
.../version-1.0.3/engine_usage/flink.md | 4 +-
.../version-1.0.3/engine_usage/hive.md | 8 +-
.../version-1.0.3/engine_usage/jdbc.md | 4 +-
.../version-1.0.3/engine_usage/python.md | 4 +-
.../version-1.0.3/engine_usage/shell.md | 4 +-
.../version-1.0.3/engine_usage/spark.md | 8 +-
.../version-1.0.3/introduction.md | 4 +-
.../tuning_and_troubleshooting/overview.md | 2 +-
.../version-1.0.3/upgrade/overview.md | 2 +-
...0_guide.md => upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../{console_manual.md => console-manual.md} | 0
.../user_guide/how-to-use.md} | 6 +-
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../version-1.0.3/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
.../version-1.1.0/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../api/{login_api.md => login-api.md} | 0
.../version-1.1.0/api/overview.md | 6 +-
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
.../{message_scheduler.md => message-scheduler.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../version-1.1.0/architecture/overview.md | 2 +-
...engine_bml_dissect.md => engine-bml-dissect.md} | 0
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
...datasource_manager.md => datasource-manager.md} | 0
.../{metadata_manager.md => metadata-manager.md} | 0
.../{public_service.md => public-service.md} | 0
...cluster_deployment.md => cluster-deployment.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
...linkis.md => involve-skywalking-into-linkis.md} | 0
.../{quick_deploy.md => quick-deploy.md} | 14 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
...t_metadatasource.md => start-metadatasource.md} | 0
.../deployment/{web_install.md => web-install.md} | 2 +-
...nd_package.md => linkis-compile-and-package.md} | 2 +-
.../{linkis_config.md => linkis-config.md} | 0
...nkis_debug_in_mac.md => linkis-debug-in-mac.md} | 0
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../development/{web_build.md => web-build.md} | 0
.../version-1.1.0/engine_usage/flink.md | 4 +-
.../version-1.1.0/engine_usage/hive.md | 8 +-
.../version-1.1.0/engine_usage/jdbc.md | 4 +-
.../version-1.1.0/engine_usage/python.md | 4 +-
.../version-1.1.0/engine_usage/shell.md | 4 +-
.../version-1.1.0/engine_usage/spark.md | 8 +-
.../version-1.1.0/introduction.md | 4 +-
.../version-1.1.0/release.md | 8 +-
.../tuning_and_troubleshooting/overview.md | 2 +-
.../upgrade/upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../upgrade/{upgrade_guide.md => upgrade-guide.md} | 2 +-
.../{console_manual.md => console-manual.md} | 0
.../user_guide/how-to-use.md} | 6 +-
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../version-1.1.0/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
.../version-1.1.1/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../api/{login_api.md => login-api.md} | 0
.../version-1.1.1/api/overview.md | 6 +-
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
.../{message_scheduler.md => message-scheduler.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../version-1.1.1/architecture/overview.md | 2 +-
.../architecture/{proxy_user.md => proxy-user.md} | 0
...engine_bml_dissect.md => engine-bml-dissect.md} | 0
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
...datasource_manager.md => datasource-manager.md} | 0
.../{metadata_manager.md => metadata-manager.md} | 0
.../{public_service.md => public-service.md} | 0
.../deployment/cluster-deployment.md} | 2 +-
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
...linkis.md => involve-skywalking-into-linkis.md} | 0
.../deployment/linkis-scriptis-install.md} | 2 +-
.../{quick_deploy.md => quick-deploy.md} | 12 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
...t_metadatasource.md => start-metadatasource.md} | 0
...ructure.md => unpack-hierarchical-structure.md} | 0
.../deployment/web-install.md} | 4 +-
.../development/linkis-compile-and-package.md} | 2 +-
.../{linkis_config.md => linkis-config.md} | 0
...nkis_debug_in_mac.md => linkis-debug-in-mac.md} | 0
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../development/{web_build.md => web-build.md} | 2 +-
.../version-1.1.1/engine_usage/flink.md | 6 +-
.../version-1.1.1/engine_usage/hive.md | 8 +-
.../version-1.1.1/engine_usage/jdbc.md | 6 +-
.../version-1.1.1/engine_usage/openlookeng.md | 6 +-
.../version-1.1.1/engine_usage/pipeline.md | 4 +-
.../version-1.1.1/engine_usage/python.md | 4 +-
.../version-1.1.1/engine_usage/shell.md | 4 +-
.../version-1.1.1/engine_usage/spark.md | 8 +-
.../version-1.1.1/introduction.md | 2 +-
.../version-1.1.1/release.md | 2 +-
.../error_guide/{error_code.md => error-code.md} | 0
.../tuning_and_troubleshooting/overview.md | 2 +-
.../upgrade/upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../upgrade/{upgrade_guide.md => upgrade-guide.md} | 2 +-
.../{console_manual.md => console-manual.md} | 0
.../user_guide/how-to-use.md} | 6 +-
.../version-1.1.1/user_guide/how_to_use.md | 24 ---
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../version-1.1.1/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
.../version-1.1.2/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../api/{login_api.md => login-api.md} | 0
.../version-1.1.2/api/overview.md | 6 +-
.../{message_scheduler.md => message-scheduler.md} | 0
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
.../engine/{proxy_user.md => proxy-user.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
.../version-1.1.2/architecture/overview.md | 2 +-
...engine_bml_dissect.md => engine-bml-dissect.md} | 0
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
...datasource_manager.md => datasource-manager.md} | 0
.../{metadata_manager.md => metadata-manager.md} | 0
.../{public_service.md => public-service.md} | 0
...cluster_deployment.md => cluster-deployment.md} | 2 +-
...thout_hdfs.md => deploy-linkis-without-hdfs.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
...linkis.md => involve-skywalking-into-linkis.md} | 0
.../deployment/linkis-scriptis-install.md} | 2 +-
.../{quick_deploy.md => quick-deploy.md} | 12 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
...t_metadatasource.md => start-metadatasource.md} | 0
...ructure.md => unpack-hierarchical-structure.md} | 0
.../deployment/{web_install.md => web-install.md} | 4 +-
.../development/linkis-compile-and-package.md} | 2 +-
.../{linkis_config.md => linkis-config.md} | 0
...nkis_debug_in_mac.md => linkis-debug-in-mac.md} | 0
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../development/{web_build.md => web-build.md} | 2 +-
.../version-1.1.2/engine_usage/flink.md | 6 +-
.../version-1.1.2/engine_usage/hive.md | 8 +-
.../version-1.1.2/engine_usage/jdbc.md | 6 +-
.../version-1.1.2/engine_usage/openlookeng.md | 6 +-
.../version-1.1.2/engine_usage/pipeline.md | 4 +-
.../version-1.1.2/engine_usage/python.md | 4 +-
.../version-1.1.2/engine_usage/shell.md | 4 +-
.../version-1.1.2/engine_usage/spark.md | 8 +-
.../version-1.1.2/engine_usage/sqoop.md | 2 +-
.../version-1.1.2/introduction.md | 2 +-
.../version-1.1.2/release.md | 4 +-
.../tuning_and_troubleshooting/overview.md | 2 +-
.../upgrade/upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../upgrade/upgrade-guide.md} | 2 +-
.../{console_manual.md => console-manual.md} | 0
.../user_guide/how-to-use.md} | 6 +-
.../version-1.1.2/user_guide/how_to_use.md | 24 ---
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../version-1.1.2/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
src/pages/home/index.js | 4 +-
.../api/{login_api.md => login-api.md} | 0
.../api/{rest_api.md => rest-api.md} | 0
.../api/{web_socket.md => web-socket.md} | 0
...real-time_log_push.md => real-time-log-push.md} | 0
.../version-0.11.0/architecture/overview.md | 4 +-
.../storage/{file_system.md => file-system.md} | 0
...d => remote-file-system-architecture-design.md} | 2 +-
.../{resultset_file.md => resultset-file.md} | 0
..._thread_pool.md => asynchronous-thread-pool.md} | 0
...ture.md => file-import-and-export-structure.md} | 0
.../ujes/{ujes_design.md => ujes-design.md} | 2 +-
...ation.md => engine-conn-plugin-installation.md} | 0
...t _guide.md => production-deployment -guide.md} | 0
.../{quick_deploy.md => quick-deploy.md} | 2 +-
.../deployment/{quick_start.md => quick-start.md} | 2 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
...mpile_and_package.md => compile-and-package.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../version-0.11.0/engine_usage/python.md | 2 +-
.../version-0.11.0/engine_usage/spark.md | 2 +-
...ide.md => upgrade-from-0.9.0-to-0.9.1-guide.md} | 0
.../{0.X_sdk_manual.md => 0.X-sdk-manual.md} | 0
.../{1.0_sdk_manual.md => 1.0-sdk-manual.md} | 0
.../version-1.0.2/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../api/{login_api.md => login-api.md} | 0
versioned_docs/version-1.0.2/api/overview.md | 6 +-
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
.../{message_scheduler.md => message-scheduler.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../version-1.0.2/architecture/overview.md | 2 +-
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
.../{public_service.md => public-service.md} | 0
...cluster_deployment.md => cluster-deployment.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
.../{quick_deploy.md => quick-deploy.md} | 2 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
.../deployment/{web_install.md => web-install.md} | 2 +-
...nd_package.md => linkis-compile-and-package.md} | 2 +-
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../development/{web_build.md => web-build.md} | 0
versioned_docs/version-1.0.2/engine_usage/hive.md | 8 +-
versioned_docs/version-1.0.2/engine_usage/jdbc.md | 4 +-
.../version-1.0.2/engine_usage/python.md | 4 +-
versioned_docs/version-1.0.2/engine_usage/shell.md | 4 +-
versioned_docs/version-1.0.2/engine_usage/spark.md | 8 +-
versioned_docs/version-1.0.2/introduction.md | 4 +-
.../tuning_and_troubleshooting/overview.md | 2 +-
versioned_docs/version-1.0.2/upgrade/overview.md | 2 +-
...0_guide.md => upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../{console_manual.md => console-manual.md} | 0
.../user_guide/how-to-use.md} | 6 +-
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../version-1.0.2/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
.../version-1.0.3/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../api/{login_api.md => login-api.md} | 0
versioned_docs/version-1.0.3/api/overview.md | 6 +-
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
.../{message_scheduler.md => message-scheduler.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../version-1.0.3/architecture/overview.md | 2 +-
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
.../{public_service.md => public-service.md} | 0
...cluster_deployment.md => cluster-deployment.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
.../deployment/quick-deploy.md} | 2 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
.../version-1.0.3/deployment/web-install.md | 2 +-
.../development/linkis-compile-and-package.md} | 2 +-
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../development/{web_build.md => web-build.md} | 0
versioned_docs/version-1.0.3/engine_usage/flink.md | 6 +-
versioned_docs/version-1.0.3/engine_usage/hive.md | 8 +-
versioned_docs/version-1.0.3/engine_usage/jdbc.md | 4 +-
.../version-1.0.3/engine_usage/python.md | 4 +-
versioned_docs/version-1.0.3/engine_usage/shell.md | 4 +-
versioned_docs/version-1.0.3/engine_usage/spark.md | 8 +-
versioned_docs/version-1.0.3/introduction.md | 4 +-
.../tuning_and_troubleshooting/overview.md | 2 +-
versioned_docs/version-1.0.3/upgrade/overview.md | 2 +-
...0_guide.md => upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../{console_manual.md => console-manual.md} | 0
.../user_guide/how-to-use.md} | 6 +-
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../version-1.0.3/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
.../version-1.1.0/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../api/{login_api.md => login-api.md} | 0
versioned_docs/version-1.1.0/api/overview.md | 6 +-
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
.../{message_scheduler.md => message-scheduler.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../version-1.1.0/architecture/overview.md | 2 +-
...engine_bml_dissect.md => engine-bml-dissect.md} | 0
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
...datasource_manager.md => datasource-manager.md} | 0
.../{metadata_manager.md => metadata-manager.md} | 0
.../{public_service.md => public-service.md} | 0
...cluster_deployment.md => cluster-deployment.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
...linkis.md => involve-skywalking-into-linkis.md} | 0
.../deployment/quick-deploy.md} | 2 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
...t_metadatasource.md => start-metadatasource.md} | 0
.../deployment/{web_install.md => web-install.md} | 2 +-
.../development/linkis-compile-and-package.md} | 2 +-
.../{linkis_config.md => linkis-config.md} | 0
...nkis_debug_in_mac.md => linkis-debug-in-mac.md} | 0
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../development/{web_build.md => web-build.md} | 0
versioned_docs/version-1.1.0/engine_usage/flink.md | 6 +-
versioned_docs/version-1.1.0/engine_usage/hive.md | 8 +-
versioned_docs/version-1.1.0/engine_usage/jdbc.md | 4 +-
.../version-1.1.0/engine_usage/python.md | 4 +-
versioned_docs/version-1.1.0/engine_usage/shell.md | 4 +-
versioned_docs/version-1.1.0/engine_usage/spark.md | 8 +-
versioned_docs/version-1.1.0/introduction.md | 4 +-
versioned_docs/version-1.1.0/release.md | 10 +-
.../tuning_and_troubleshooting/overview.md | 2 +-
.../upgrade/upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../upgrade/{upgrade_guide.md => upgrade-guide.md} | 2 +-
.../{console_manual.md => console-manual.md} | 0
.../user_guide/how-to-use.md} | 6 +-
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../version-1.1.0/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
.../version-1.1.1/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../api/{login_api.md => login-api.md} | 0
versioned_docs/version-1.1.1/api/overview.md | 6 +-
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
.../{message_scheduler.md => message-scheduler.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../version-1.1.1/architecture/overview.md | 2 +-
.../architecture/{proxy_user.md => proxy-user.md} | 0
...engine_bml_dissect.md => engine-bml-dissect.md} | 0
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
...datasource_manager.md => datasource-manager.md} | 0
.../{metadata_manager.md => metadata-manager.md} | 0
.../{public_service.md => public-service.md} | 0
...cluster_deployment.md => cluster-deployment.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
...linkis.md => involve-skywalking-into-linkis.md} | 0
.../deployment/linkis-scriptis-install.md} | 2 +-
.../{quick_deploy.md => quick-deploy.md} | 2 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
...t_metadatasource.md => start-metadatasource.md} | 0
...ructure.md => unpack-hierarchical-structure.md} | 0
.../deployment/{web_install.md => web-install.md} | 2 +-
.../development/linkis-compile-and-package.md | 2 +-
.../{linkis_config.md => linkis-config.md} | 0
...nkis_debug_in_mac.md => linkis-debug-in-mac.md} | 0
.../{linkis_debug.md => linkis-debug.md} | 0
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../development/{web_build.md => web-build.md} | 0
versioned_docs/version-1.1.1/engine_usage/flink.md | 6 +-
versioned_docs/version-1.1.1/engine_usage/hive.md | 8 +-
versioned_docs/version-1.1.1/engine_usage/jdbc.md | 4 +-
.../version-1.1.1/engine_usage/openlookeng.md | 6 +-
.../version-1.1.1/engine_usage/pipeline.md | 4 +-
.../version-1.1.1/engine_usage/python.md | 4 +-
versioned_docs/version-1.1.1/engine_usage/shell.md | 4 +-
versioned_docs/version-1.1.1/engine_usage/spark.md | 8 +-
versioned_docs/version-1.1.1/introduction.md | 4 +-
versioned_docs/version-1.1.1/release.md | 2 +-
.../error_guide/{error_code.md => error-code.md} | 0
.../tuning_and_troubleshooting/overview.md | 2 +-
...0_guide.md => upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../upgrade/{upgrade_guide.md => upgrade-guide.md} | 2 +-
.../{console_manual.md => console-manual.md} | 0
.../version-1.1.1/user_guide/how-to-use.md | 6 +-
.../version-1.1.1/user_guide/how_to_use.md | 34 ----
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../version-1.1.1/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
.../version-1.1.2/api/{jdbc_api.md => jdbc-api.md} | 0
...is_task_operator.md => linkis-task-operator.md} | 0
.../api/{login_api.md => login-api.md} | 0
versioned_docs/version-1.1.2/api/overview.md | 6 +-
.../{message_scheduler.md => message-scheduler.md} | 0
...add_an_engine_conn.md => add-an-engine-conn.md} | 0
...gine_conn_manager.md => engine-conn-manager.md} | 0
...engine_conn_plugin.md => engine-conn-plugin.md} | 0
.../engine/{engine_conn.md => engine-conn.md} | 0
...ubmission-preparation-and-execution-process.md} | 4 +-
.../{app_manager.md => app-manager.md} | 0
.../{label_manager.md => label-manager.md} | 0
.../{resource_manager.md => resource-manager.md} | 0
.../computation_governance_services/overview.md | 4 +-
.../{proxy_user.md => proxy-user.md} | 0
...nd_0.x.md => difference-between-1.0-and-0.x.md} | 0
.../version-1.1.2/architecture/overview.md | 2 +-
...engine_bml_dissect.md => engine-bml-dissect.md} | 0
...t_service_cache.md => context-service-cache.md} | 0
...service_client.md => context-service-client.md} | 0
...ailable.md => context-service-highavailable.md} | 0
...ice_listener.md => context-service-listener.md} | 0
...rsistence.md => context-service-persistence.md} | 0
...service_search.md => context-service-search.md} | 0
.../{context_service.md => context-service.md} | 0
.../context_service/overview.md | 14 +-
...datasource_manager.md => datasource-manager.md} | 0
.../{metadata_manager.md => metadata-manager.md} | 0
.../{public_service.md => public-service.md} | 0
...cluster_deployment.md => cluster-deployment.md} | 0
...thout_hdfs.md => deploy-linkis-without-hdfs.md} | 0
...ation.md => engine-conn-plugin-installation.md} | 0
...e.md => installation-hierarchical-structure.md} | 0
...linkis.md => involve-skywalking-into-linkis.md} | 0
.../deployment/linkis-scriptis-install.md} | 2 +-
.../{quick_deploy.md => quick-deploy.md} | 2 +-
...ure.md => sourcecode-hierarchical-structure.md} | 0
...t_metadatasource.md => start-metadatasource.md} | 0
...ructure.md => unpack-hierarchical-structure.md} | 0
.../deployment/web-install.md} | 2 +-
.../version-1.1.2/deployment/web_install.md | 115 -------------
.../development/linkis-compile-and-package.md} | 2 +-
.../{linkis_config.md => linkis-config.md} | 0
...nkis_debug_in_mac.md => linkis-debug-in-mac.md} | 0
.../{linkis_debug.md => linkis-debug.md} | 0
.../development/linkis_compile_and_package.md | 177 ---------------------
.../{new_engine_conn.md => new-engine-conn.md} | 0
.../development/{web_build.md => web-build.md} | 0
versioned_docs/version-1.1.2/engine_usage/flink.md | 6 +-
versioned_docs/version-1.1.2/engine_usage/hive.md | 8 +-
versioned_docs/version-1.1.2/engine_usage/jdbc.md | 4 +-
.../version-1.1.2/engine_usage/openlookeng.md | 6 +-
.../version-1.1.2/engine_usage/pipeline.md | 4 +-
.../version-1.1.2/engine_usage/python.md | 4 +-
versioned_docs/version-1.1.2/engine_usage/shell.md | 4 +-
versioned_docs/version-1.1.2/engine_usage/spark.md | 8 +-
versioned_docs/version-1.1.2/engine_usage/sqoop.md | 2 +-
versioned_docs/version-1.1.2/introduction.md | 4 +-
versioned_docs/version-1.1.2/release.md | 4 +-
.../tuning_and_troubleshooting/overview.md | 2 +-
.../upgrade/upgrade-from-0.X-to-1.0-guide.md} | 6 +-
.../upgrade/{upgrade_guide.md => upgrade-guide.md} | 2 +-
.../{console_manual.md => console-manual.md} | 0
.../version-1.1.2/user_guide/how-to-use.md | 6 +-
.../version-1.1.2/user_guide/how_to_use.md | 34 ----
.../{linkiscli_manual.md => linkiscli-manual.md} | 0
.../version-1.1.2/user_guide/overview.md | 8 +-
.../user_guide/{sdk_manual.md => sdk-manual.md} | 0
794 files changed, 733 insertions(+), 1141 deletions(-)
diff --git a/blog/2022-02-21-linkis-deploy.md b/blog/2022-02-21-linkis-deploy.md
index 5d06ebc6ad..e522fbf06d 100644
--- a/blog/2022-02-21-linkis-deploy.md
+++ b/blog/2022-02-21-linkis-deploy.md
@@ -268,7 +268,7 @@ After the installation is complete, if you need to modify the configuration, you
### 3.4 Add mysql driver (>=1.0.3) version
Because of the license, mysql-connector-java is removed from the release package of linkis itself (the family bucket integrated by dss will be included, no need to manually add it), which needs to be added manually.
-For details, see [Add mysql driver package](docs/1.0.3/deployment/quick_deploy#-44-Add mysql driver package)
+For details, see [Add mysql driver package](docs/1.0.3/deployment/quick-deploy#-44-Add mysql driver package)
### 3.5 Start the service
```shell script
@@ -420,7 +420,7 @@ normal as follows
Check whether the material record of the engine exists (if there is an update, check whether the update time is correct).
-If it does not exist or is not updated, first try to manually refresh the material resource (for details, see [Engine Material Resource Refresh](docs/latest/deployment/engine_conn_plugin_installation#23-Engine Refresh)). Check the `log/linkis-cg-engineplugin.log` log to check the specific reasons for the failure of the material. In many cases, it may be caused by the lack of permissions in the hdfs directory. Check whether the gateway address configuration is correct `conf/linkis.propert [...]
+If it does not exist or is not updated, first try to manually refresh the material resource (for details, see [Engine Material Resource Refresh](docs/latest/deployment/engine-conn-plugin-installation#23-Engine Refresh)). Check the `log/linkis-cg-engineplugin.log` log to check the specific reasons for the failure of the material. In many cases, it may be caused by the lack of permissions in the hdfs directory. Check whether the gateway address configuration is correct `conf/linkis.propert [...]
The material resources of the engine are uploaded to the hdfs directory by default as `/apps-data/${deployUser}/bml`
```shell script
@@ -517,7 +517,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
### 6.6 Debugging of Http interface
- Method 1 can open the [Login-Free Mode Guide] (docs/latest/api/login_api#2 Login-Free Configuration)
+ Method 1 can open the [Login-Free Mode Guide] (docs/latest/api/login-api#2 Login-Free Configuration)
Method 2: Add a static Token to the http request header
```shell script
Token-User:hadoop
diff --git a/blog/2022-04-15-how-to-download-engineconn-plugin.md b/blog/2022-04-15-how-to-download-engineconn-plugin.md
index 52d5dacfbc..5de14d8913 100644
--- a/blog/2022-04-15-how-to-download-engineconn-plugin.md
+++ b/blog/2022-04-15-how-to-download-engineconn-plugin.md
@@ -82,4 +82,4 @@ cd 1.0.3-engineconn-plugin
Copy the engine material package to be used to the engine plug-in directory of linkis, and then refresh the engine material.
-Detailed process reference[Installing EngineConnPlugin engine](https://linkis.apache.org/zh-CN/docs/latest/deployment/engine_conn_plugin_installation).
\ No newline at end of file
+Detailed process reference[Installing EngineConnPlugin engine](https://linkis.apache.org/zh-CN/docs/latest/deployment/engine-conn-plugin-installation).
\ No newline at end of file
diff --git a/community/development_specification/exception_catch.md b/community/development_specification/exception-catch.md
similarity index 100%
rename from community/development_specification/exception_catch.md
rename to community/development_specification/exception-catch.md
diff --git a/community/development_specification/overview.md b/community/development_specification/overview.md
index c524ec5e3d..908252021a 100644
--- a/community/development_specification/overview.md
+++ b/community/development_specification/overview.md
@@ -5,13 +5,13 @@ sidebar_position: 0
In order to standardize Linkis's community development environment, improve the output quality of subsequent development iterations of Linkis, and standardize the entire development and design process of Linkis, it is strongly recommended that Contributors follow the following development specifications:
- [License Notes](license.md)
-- [Programming Specification](programming_specification.md)
+- [Programming Specification](programming-specification.md)
- [Log Specification](log.md)
-- [Exception Handling Specification](exception_catch.md)
+- [Exception Handling Specification](exception-catch.md)
- [API Specification](api.md)
- [Concurrency Specification](concurrent.md)
-- [Path Specification](path_usage.md)
-- [Test Specification](unit_test.md)
-- [version and new feature specification](version_feature_specifications.md)
+- [Path Specification](path-usage.md)
+- [Test Specification](unit-test.md)
+- [version and new feature specification](version-feature-specifications.md)
**Note**: The development specifications of the initial version of Linkis1.0 are relatively brief, and will continue to be supplemented and improved with the iteration of Linkis. Contributors are welcome to provide their own opinions and comments.
diff --git a/community/development_specification/path_usage.md b/community/development_specification/path-usage.md
similarity index 100%
rename from community/development_specification/path_usage.md
rename to community/development_specification/path-usage.md
diff --git a/community/development_specification/programming_specification.md b/community/development_specification/programming-specification.md
similarity index 100%
rename from community/development_specification/programming_specification.md
rename to community/development_specification/programming-specification.md
diff --git a/community/development_specification/unit_test.md b/community/development_specification/unit-test.md
similarity index 100%
rename from community/development_specification/unit_test.md
rename to community/development_specification/unit-test.md
diff --git a/community/development_specification/version_feature_specifications.md b/community/development_specification/version-feature-specifications.md
similarity index 97%
rename from community/development_specification/version_feature_specifications.md
rename to community/development_specification/version-feature-specifications.md
index 7c187cb5af..c926429fd9 100644
--- a/community/development_specification/version_feature_specifications.md
+++ b/community/development_specification/version-feature-specifications.md
@@ -21,5 +21,5 @@ When you add new features, you need to follow the steps below:
2. [Mandatory] New features need to be added to the version corresponding to GitHub [Project](https://github.com/apache/incubator-linkis/projects)
3. [Mandatory] The mailing list needs to be sent to installation, database, configuration modification
4. [Mandatory] New features must add new documents
-5. [Mandatory] New features need to add corresponding unit tests, [Unit Test Specification](https://linkis.apache.org/community/development_specification/unit_test)
+5. [Mandatory] New features need to add corresponding unit tests, [Unit Test Specification](https://linkis.apache.org/community/development_specification/unit-test)
6. [Recommended] One feature corresponds to one issue corresponds to one PR
\ No newline at end of file
diff --git a/community/how-to-contribute-to-website.md b/community/how-to-contribute-to-website.md
index ae4b91b805..b0480075b1 100644
--- a/community/how-to-contribute-to-website.md
+++ b/community/how-to-contribute-to-website.md
@@ -158,7 +158,7 @@ Visit the page https://linkis.apache.org/user
Company logo Located in `static/home/user`, and the picture size must be 176 × 88.
### 3.10 Path specification
-If you want to link from a markdown document to another, it is best to use absolute path. For example, if you want to link to `quick_deploy.md`, the path should be `/docs/deployment/quick_deploy.md`.
+If you want to link from a markdown document to another, it is best to use absolute path. For example, if you want to link to `quick-deploy.md`, the path should be `/docs/deployment/quick-deploy.md`.
### English document title specification
English siderbar titles should be capitalized except for prepositions, and only the first word of the title in the markdwon document should be capitalized.
diff --git a/community/how-to-contribute.md b/community/how-to-contribute.md
index 48393dbc58..3b7b1680e7 100644
--- a/community/how-to-contribute.md
+++ b/community/how-to-contribute.md
@@ -151,7 +151,7 @@ The user configuration is in the project root directory /config/, the project st
3. Code directory structure
- For details, see [Linkis Code Directory Structure](https://linkis.apache.org/docs/latest/deployment/sourcecode_hierarchical_structure)
+ For details, see [Linkis Code Directory Structure](https://linkis.apache.org/docs/latest/deployment/sourcecode-hierarchical-structure)
4. Log directory
diff --git a/docs/api/jdbc_api.md b/docs/api/jdbc-api.md
similarity index 100%
rename from docs/api/jdbc_api.md
rename to docs/api/jdbc-api.md
diff --git a/docs/api/linkis_task_operator.md b/docs/api/linkis-task-operator.md
similarity index 100%
rename from docs/api/linkis_task_operator.md
rename to docs/api/linkis-task-operator.md
diff --git a/docs/api/login_api.md b/docs/api/login-api.md
similarity index 100%
rename from docs/api/login_api.md
rename to docs/api/login-api.md
diff --git a/docs/api/overview.md b/docs/api/overview.md
index 60a92418bb..3f08075bde 100644
--- a/docs/api/overview.md
+++ b/docs/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 0
## 1. Document description
Linkis1.0 has been refactored and optimized on the basis of Linkix0.x, and it is also compatible with the 0.x interface. However, in order to prevent compatibility problems when using version 1.0, you need to read the following documents carefully:
-1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login_api.md) carefully.
+1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login-api.md) carefully.
-2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc_api.md).
+2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc-api.md).
-3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis_task_operator.md).
\ No newline at end of file
+3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis-task-operator.md).
\ No newline at end of file
diff --git a/docs/architecture/computation_governance_services/engine/add_an_engine_conn.md b/docs/architecture/computation_governance_services/engine/add-an-engine-conn.md
similarity index 100%
rename from docs/architecture/computation_governance_services/engine/add_an_engine_conn.md
rename to docs/architecture/computation_governance_services/engine/add-an-engine-conn.md
diff --git a/docs/architecture/computation_governance_services/engine/engine_conn_history.md b/docs/architecture/computation_governance_services/engine/engine-conn-history.md
similarity index 100%
rename from docs/architecture/computation_governance_services/engine/engine_conn_history.md
rename to docs/architecture/computation_governance_services/engine/engine-conn-history.md
diff --git a/docs/architecture/computation_governance_services/engine/engine_conn_manager.md b/docs/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from docs/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to docs/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/docs/architecture/computation_governance_services/engine/engine_conn_metrics.md b/docs/architecture/computation_governance_services/engine/engine-conn-metrics.md
similarity index 100%
rename from docs/architecture/computation_governance_services/engine/engine_conn_metrics.md
rename to docs/architecture/computation_governance_services/engine/engine-conn-metrics.md
diff --git a/docs/architecture/computation_governance_services/engine/engine_conn_plugin.md b/docs/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from docs/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to docs/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/docs/architecture/computation_governance_services/engine/engine_conn.md b/docs/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from docs/architecture/computation_governance_services/engine/engine_conn.md
rename to docs/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/docs/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md b/docs/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from docs/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md
rename to docs/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
index 1eab642967..abff385e2a 100644
--- a/docs/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md
+++ b/docs/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
@@ -30,7 +30,7 @@ The submission phase is mainly the interaction of Client -> Linkis Gateway -> En
-1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](user_guide/how_to_use.md)):
+1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](../../user_guide/how-to-use.md)):
```
POST /api/rest_j/v1/entrance/submit
```
@@ -62,7 +62,7 @@ If the user has a reusable EngineConn in LinkisManager, the EngineConn is direct
How to define a reusable EngineConn? It refers to those that can match all the label requirements of the computing task, and the EngineConn's own health status is Healthy (the load is low and the actual status is Idle). Then, all the EngineConn that meets the conditions are sorted and selected according to the rules, and finally the best one is locked.
-If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](engine/add_an_engine_conn.md).
+If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](engine/add-an-engine-conn.md).
#### 2.2 Orchestrate a computing task
diff --git a/docs/architecture/computation_governance_services/linkis_manager/app_manager.md b/docs/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from docs/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to docs/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/docs/architecture/computation_governance_services/linkis_manager/label_manager.md b/docs/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from docs/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to docs/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/docs/architecture/computation_governance_services/linkis_manager/resource_manager.md b/docs/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from docs/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to docs/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/docs/architecture/computation_governance_services/overview.md b/docs/architecture/computation_governance_services/overview.md
index 80c421ad74..9446468701 100644
--- a/docs/architecture/computation_governance_services/overview.md
+++ b/docs/architecture/computation_governance_services/overview.md
@@ -44,7 +44,7 @@ Perform three stages to fully upgrade Linkis's Job execution architecture, as sh
[Enter LinkisManager Architecture Design](linkis_manager/overview.md)
### 4. Engine Manager
Engine conn Manager (ECM) is a simplified and upgraded version of linkis0. X engine manager. The ECM under linkis1.0 removes the application ability of the engine, and the whole microservice is completely stateless. It will focus on supporting the startup and destruction of all kinds of enginecon.
-[Enter EngineConnManager Architecture Design](engine/engine_conn_manager.md)
+[Enter EngineConnManager Architecture Design](engine/engine-conn-manager.md)
### 5. EngineConn
EngineConn is an optimized and upgraded version of Linkis0.X Engine. It will provide EngineConn and Executor two modules. EngineConn is used to connect the underlying computing storage engine and provide a session session that connects the underlying computing storage engines; Executor is based on this Session session , Provide full-stack computing support for interactive computing, streaming computing, offline computing, and data storage.
- [Enter EngineConn Architecture Design](engine/engine_conn.md)
+ [Enter EngineConn Architecture Design](engine/engine-conn.md)
diff --git a/docs/architecture/computation_governance_services/proxy_user.md b/docs/architecture/computation_governance_services/proxy-user.md
similarity index 100%
rename from docs/architecture/computation_governance_services/proxy_user.md
rename to docs/architecture/computation_governance_services/proxy-user.md
diff --git a/docs/architecture/difference_between_1.0_and_0.x.md b/docs/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from docs/architecture/difference_between_1.0_and_0.x.md
rename to docs/architecture/difference-between-1.0-and-0.x.md
diff --git a/docs/architecture/overview.md b/docs/architecture/overview.md
index 3a45df32c6..e3efc03e13 100644
--- a/docs/architecture/overview.md
+++ b/docs/architecture/overview.md
@@ -15,7 +15,7 @@ The specific responsibilities of each category are as follows:
The following is a directory listing of Linkis1.0 architecture documents:
-1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference_between_1.0_and_0.x.md).
+1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference-between-1.0-and-0.x.md).
2. Linkis 1.0 public enhancement service related documents, please read [Public Enhancement Service](public_enhancement_services/overview.md).
3. Linkis 1.0 microservice governance related documents, please read [Microservice Governance](microservice_governance_services/overview.md).
4. Linkis 1.0 computing governance service related documents, please read [Computation Governance Service](computation_governance_services/overview.md).
\ No newline at end of file
diff --git a/docs/architecture/public_enhancement_services/bml/engine_bml_dissect.md b/docs/architecture/public_enhancement_services/bml/engine-bml-dissect.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/bml/engine_bml_dissect.md
rename to docs/architecture/public_enhancement_services/bml/engine-bml-dissect.md
diff --git a/docs/architecture/public_enhancement_services/context_service/content_service_cleanup.md b/docs/architecture/public_enhancement_services/context_service/content-service-cleanup.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/context_service/content_service_cleanup.md
rename to docs/architecture/public_enhancement_services/context_service/content-service-cleanup.md
diff --git a/docs/architecture/public_enhancement_services/context_service/context_service_cache.md b/docs/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to docs/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/docs/architecture/public_enhancement_services/context_service/context_service_client.md b/docs/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/context_service/context_service_client.md
rename to docs/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/docs/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/docs/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to docs/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/docs/architecture/public_enhancement_services/context_service/context_service_listener.md b/docs/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to docs/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/docs/architecture/public_enhancement_services/context_service/context_service_persistence.md b/docs/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to docs/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/docs/architecture/public_enhancement_services/context_service/context_service_search.md b/docs/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/context_service/context_service_search.md
rename to docs/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/docs/architecture/public_enhancement_services/context_service/context_service.md b/docs/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/context_service/context_service.md
rename to docs/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/docs/architecture/public_enhancement_services/context_service/overview.md b/docs/architecture/public_enhancement_services/context_service/overview.md
index 4fae9dfbab..d44f182f29 100644
--- a/docs/architecture/public_enhancement_services/context_service/overview.md
+++ b/docs/architecture/public_enhancement_services/context_service/overview.md
@@ -101,28 +101,28 @@ The runtime workflow is mainly used by Linkis.
### 1. Client
The entrance of external access to CS, Client module provides HA function;
-[Enter Client Architecture Design](context_service_client.md)
+[Enter Client Architecture Design](context-service-client.md)
### 2. Service Module
Provide a Restful interface to encapsulate and process CS requests submitted by the client;
-[Enter Service Architecture Design](context_service.md)
+[Enter Service Architecture Design](context-service.md)
### 3. ContextSearch
The context query module provides rich and powerful query capabilities for the client to find the key-value key-value pairs of the context;
-[Enter ContextSearch architecture design](context_service_search.md)
+[Enter ContextSearch architecture design](context-service-search.md)
### 4. Listener
The CS listener module provides synchronous and asynchronous event consumption capabilities, and has the ability to notify the Client in real time once the Zookeeper-like Key-Value is updated;
-[Enter Listener architecture design](context_service_listener.md)
+[Enter Listener architecture design](context-service-listener.md)
### 5. ContextCache
The context memory cache module provides the ability to quickly retrieve the context and the ability to monitor and clean up JVM memory usage;
-[Enter ContextCache architecture design](context_service_cache.md)
+[Enter ContextCache architecture design](context-service-cache.md)
### 6. HighAvailable
Provide CS high availability capability;
-[Enter HighAvailable architecture design](context_service_highavailable.md)
+[Enter HighAvailable architecture design](context-service-highavailable.md)
### 7. Persistence
The persistence function of CS;
-[Enter Persistence architecture design](context_service_persistence.md)
\ No newline at end of file
+[Enter Persistence architecture design](context-service-persistence.md)
\ No newline at end of file
diff --git a/docs/architecture/public_enhancement_services/datasource_manager.md b/docs/architecture/public_enhancement_services/datasource-manager.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/datasource_manager.md
rename to docs/architecture/public_enhancement_services/datasource-manager.md
diff --git a/docs/architecture/public_enhancement_services/metadata_manager.md b/docs/architecture/public_enhancement_services/metadata-manager.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/metadata_manager.md
rename to docs/architecture/public_enhancement_services/metadata-manager.md
diff --git a/docs/architecture/public_enhancement_services/public_service.md b/docs/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from docs/architecture/public_enhancement_services/public_service.md
rename to docs/architecture/public_enhancement_services/public-service.md
diff --git a/docs/deployment/cluster_deployment.md b/docs/deployment/cluster-deployment.md
similarity index 100%
rename from docs/deployment/cluster_deployment.md
rename to docs/deployment/cluster-deployment.md
diff --git a/docs/deployment/deploy_linkis_without_hdfs.md b/docs/deployment/deploy-linkis-without-hdfs.md
similarity index 100%
rename from docs/deployment/deploy_linkis_without_hdfs.md
rename to docs/deployment/deploy-linkis-without-hdfs.md
diff --git a/docs/deployment/engine_conn_plugin_installation.md b/docs/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from docs/deployment/engine_conn_plugin_installation.md
rename to docs/deployment/engine-conn-plugin-installation.md
diff --git a/docs/deployment/installation_hierarchical_structure.md b/docs/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from docs/deployment/installation_hierarchical_structure.md
rename to docs/deployment/installation-hierarchical-structure.md
diff --git a/docs/deployment/involve_knife4j_into_linkis.md b/docs/deployment/involve-knife4j-into-linkis.md
similarity index 100%
rename from docs/deployment/involve_knife4j_into_linkis.md
rename to docs/deployment/involve-knife4j-into-linkis.md
diff --git a/docs/deployment/involve_prometheus_into_linkis.md b/docs/deployment/involve-prometheus-into-linkis.md
similarity index 100%
rename from docs/deployment/involve_prometheus_into_linkis.md
rename to docs/deployment/involve-prometheus-into-linkis.md
diff --git a/docs/deployment/involve_skywalking_into_linkis.md b/docs/deployment/involve-skywalking-into-linkis.md
similarity index 100%
rename from docs/deployment/involve_skywalking_into_linkis.md
rename to docs/deployment/involve-skywalking-into-linkis.md
diff --git a/docs/deployment/linkis_scriptis_install.md b/docs/deployment/linkis-scriptis-install.md
similarity index 98%
rename from docs/deployment/linkis_scriptis_install.md
rename to docs/deployment/linkis-scriptis-install.md
index 4884cbfa95..f5fa8e1bd0 100644
--- a/docs/deployment/linkis_scriptis_install.md
+++ b/docs/deployment/linkis-scriptis-install.md
@@ -8,7 +8,7 @@ sidebar_position: 10
> After Apache Linkis >= 1.1.1 and DSS >= 1.1.0, scriptis can be deployed separately and used in conjunction with Linkis. Using the interactive analysis function of scriptis, you can write SQL, Pyspark, HiveQL, etc. online on web pages Scripts are submitted to Linkis for execution and support features such as UDFs, functions, resource management and custom variables. This article will introduce how to deploy the web component-scriptis separately, and use Apache Linkis through the script [...]
-Prerequisite: The Linkis service (backend and management desk service) has been successfully installed and can be used normally. The deployment process of Linkis can be found in [Quick Deployment of Apache Linkis](quick_deploy.md)
+Prerequisite: The Linkis service (backend and management desk service) has been successfully installed and can be used normally. The deployment process of Linkis can be found in [Quick Deployment of Apache Linkis](quick-deploy.md)
Example description:
diff --git a/docs/deployment/quick_deploy.md b/docs/deployment/quick-deploy.md
similarity index 99%
rename from docs/deployment/quick_deploy.md
rename to docs/deployment/quick-deploy.md
index d6d39c25b3..cbe0b15760 100644
--- a/docs/deployment/quick_deploy.md
+++ b/docs/deployment/quick-deploy.md
@@ -8,7 +8,7 @@ sidebar_position: 1
Because the mysql-connector-java driver is under the GPL2.0 agreement and does not meet the license policy of the Apache open source agreement, starting from version 1.0.3, the official deployment package of the Apache version is provided. The default is no mysql-connector-java-x.x.x.jar dependency package. You need to add dependencies to the corresponding lib package during installation and deployment.
</font>
-If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md).
+If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md).
Please note: Apart from the four EngineConnPlugins included in the Linkis 1.0 installation package by default: Python/Shell/Hive/Spark. You can manually install other types of engines such as JDBC depending on your own needs. For details, please refer to EngineConnPlugin installation documents.
diff --git a/docs/deployment/sourcecode_hierarchical_structure.md b/docs/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from docs/deployment/sourcecode_hierarchical_structure.md
rename to docs/deployment/sourcecode-hierarchical-structure.md
diff --git a/docs/deployment/start_metadatasource.md b/docs/deployment/start-metadatasource.md
similarity index 100%
rename from docs/deployment/start_metadatasource.md
rename to docs/deployment/start-metadatasource.md
diff --git a/docs/deployment/unpack_hierarchical_structure.md b/docs/deployment/unpack-hierarchical-structure.md
similarity index 100%
rename from docs/deployment/unpack_hierarchical_structure.md
rename to docs/deployment/unpack-hierarchical-structure.md
diff --git a/versioned_docs/version-1.0.3/deployment/web_install.md b/docs/deployment/web-install.md
similarity index 99%
copy from versioned_docs/version-1.0.3/deployment/web_install.md
copy to docs/deployment/web-install.md
index 38f9e471be..6e91d7ef11 100644
--- a/versioned_docs/version-1.0.3/deployment/web_install.md
+++ b/docs/deployment/web-install.md
@@ -3,7 +3,7 @@ title: Linkis Console Deployment
sidebar_position: 6
---
-Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick_deploy.md)
+Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick-deploy.md)
## 1. Preparation
diff --git a/versioned_docs/version-1.0.3/development/linkis_compile_and_package.md b/docs/development/linkis-compile-and-package.md
similarity index 98%
copy from versioned_docs/version-1.0.3/development/linkis_compile_and_package.md
copy to docs/development/linkis-compile-and-package.md
index f90db5fd2f..50c1a4a279 100644
--- a/versioned_docs/version-1.0.3/development/linkis_compile_and_package.md
+++ b/docs/development/linkis-compile-and-package.md
@@ -108,7 +108,7 @@ Get the installation package, there will be a compiled package in the ->target d
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/linkis-engineplugin-spark-x.x.x.jar
```
-How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine_conn_plugin_installation)
+How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine-conn-plugin-installation)
## 5. How to modify the Hadoop, Hive, and Spark versions that Linkis depends on
diff --git a/docs/development/linkis_config.md b/docs/development/linkis-config.md
similarity index 100%
rename from docs/development/linkis_config.md
rename to docs/development/linkis-config.md
diff --git a/docs/development/linkis_debug_in_mac.md b/docs/development/linkis-debug-in-mac.md
similarity index 100%
rename from docs/development/linkis_debug_in_mac.md
rename to docs/development/linkis-debug-in-mac.md
diff --git a/docs/development/linkis_debug.md b/docs/development/linkis-debug.md
similarity index 100%
rename from docs/development/linkis_debug.md
rename to docs/development/linkis-debug.md
diff --git a/docs/development/new_engine_conn.md b/docs/development/new-engine-conn.md
similarity index 100%
rename from docs/development/new_engine_conn.md
rename to docs/development/new-engine-conn.md
diff --git a/docs/development/swwager_instructions.md b/docs/development/swwager-instructions.md
similarity index 100%
rename from docs/development/swwager_instructions.md
rename to docs/development/swwager-instructions.md
diff --git a/docs/development/web_build.md b/docs/development/web-build.md
similarity index 100%
rename from docs/development/web_build.md
rename to docs/development/web-build.md
diff --git a/docs/engine_usage/flink.md b/docs/engine_usage/flink.md
index 2e61249144..535264d7ba 100644
--- a/docs/engine_usage/flink.md
+++ b/docs/engine_usage/flink.md
@@ -56,13 +56,13 @@ cd ${LINKIS_HOME}/sbin
sh linkis-daemon restart cg-engineplugin
```
A more detailed introduction to engineplugin can be found in the following article.
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Flink engine tags
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. The use of Flink engine
@@ -115,7 +115,7 @@ After Linkis 1.0, a cli method is provided to submit tasks. We only need to spec
sh ./bin/linkis-cli -engineType flink-1.12.2 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-For specific usage, please refer to: [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+For specific usage, please refer to: [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 OnceEngineConn method
diff --git a/docs/engine_usage/hive.md b/docs/engine_usage/hive.md
index bc52ab4846..b685701af7 100644
--- a/docs/engine_usage/hive.md
+++ b/docs/engine_usage/hive.md
@@ -32,13 +32,13 @@ Other hive operating modes are similar, just copy the corresponding dependencies
If you have already compiled your hive engineConn plug-in has been compiled, then you need to put the new plug-in in the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Linkis adds Hive console parameters(optional)
Linkis can configure the corresponding EngineConn parameters on the management console. If your newly added EngineConn needs this feature, you can refer to the following documents:
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of hive engineConn
@@ -54,7 +54,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -69,7 +69,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/docs/engine_usage/jdbc.md b/docs/engine_usage/jdbc.md
index 1db1d63951..47d84a6aab 100644
--- a/docs/engine_usage/jdbc.md
+++ b/docs/engine_usage/jdbc.md
@@ -43,7 +43,7 @@ wds.linkis.jdbc.password
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -58,7 +58,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/docs/engine_usage/openlookeng.md b/docs/engine_usage/openlookeng.md
index 80586220b8..c6f0898347 100644
--- a/docs/engine_usage/openlookeng.md
+++ b/docs/engine_usage/openlookeng.md
@@ -47,7 +47,7 @@ sh linkis-daemon restart cg-engineplugin
Linkis1.X is done through tags, so we need to insert data into our database, and the insertion method is as follows.
-[EngineConnPlugin engine plugin installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin engine plugin installation](../deployment/engine-conn-plugin-installation)
## 3 The use of the engine
@@ -84,7 +84,7 @@ Example of http request parameters
### 3.1 Using Linkis SDK
-Linkis provides Java and Scala SDKs to submit tasks to the Linkis server. For details, please refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides Java and Scala SDKs to submit tasks to the Linkis server. For details, please refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
For the openlookeng task, you only need to modify the EngineConnType and CodeType parameters in the Demo:
````java
@@ -100,4 +100,4 @@ After Linkis 1.0, the cli method is provided to submit tasks. We only need to sp
```shell
sh ./bin/linkis-cli -engineType openlookeng-1.5.0 -codeType sql -code 'show databases;' -submitUser hadoop -proxyUser hadoop
````
-For specific usage, please refer to: [Linkis CLI Manual](user_guide/linkiscli_manual.md).
\ No newline at end of file
+For specific usage, please refer to: [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
\ No newline at end of file
diff --git a/docs/engine_usage/pipeline.md b/docs/engine_usage/pipeline.md
index 441af1d6d9..f3b7d69a9d 100644
--- a/docs/engine_usage/pipeline.md
+++ b/docs/engine_usage/pipeline.md
@@ -62,7 +62,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
Linkis1.XIt is carried out through labels, so it is necessary to insert data into our database. The insertion method is shown below.
-[EngineConnPlugin Engine plug-in installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Engine plug-in installation](../deployment/engine-conn-plugin-installation)
## 2 Use of engine
@@ -76,7 +76,7 @@ sh bin/linkis-cli -submitUser hadoop -engineType pipeline-1 -codeType pipelin
```
from hdfs:///000/000/000/A.dolphin to file:///000/000/000/B.csv 3.3 Explained
-For specific use, please refer to： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+For specific use, please refer to： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
because`pipeline`The engine is mainly used to import and export files. Now let's assume that importing files from a to B is the most introduced case
diff --git a/docs/engine_usage/python.md b/docs/engine_usage/python.md
index ebd05857e6..4e512306ed 100644
--- a/docs/engine_usage/python.md
+++ b/docs/engine_usage/python.md
@@ -50,7 +50,7 @@ Before submitting python on linkis, you only need to make sure that there is pyt
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -65,7 +65,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/docs/engine_usage/shell.md b/docs/engine_usage/shell.md
index d99a4ca96e..3296981943 100644
--- a/docs/engine_usage/shell.md
+++ b/docs/engine_usage/shell.md
@@ -37,7 +37,7 @@ Before submitting the shell on linkis, you only need to ensure that there is the
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -52,7 +52,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/docs/engine_usage/spark.md b/docs/engine_usage/spark.md
index 7dc53b328e..656bae26d2 100644
--- a/docs/engine_usage/spark.md
+++ b/docs/engine_usage/spark.md
@@ -34,13 +34,13 @@ In theory, Linkis1.0 supports all versions of spark2.x and above. Spark 2.4.3 is
If you have already compiled your spark EngineConn plug-in has been compiled, then you need to put the new plug-in to the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 tags of spark EngineConn
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of spark EngineConn
@@ -56,7 +56,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -77,7 +77,7 @@ sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -s
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -confMap wds.linkis.yarnqueue=dws -code "show tables" -submitUser hadoop -proxyUser hadoop
````
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/docs/engine_usage/sqoop.md b/docs/engine_usage/sqoop.md
index ece1612c76..f8b062d363 100644
--- a/docs/engine_usage/sqoop.md
+++ b/docs/engine_usage/sqoop.md
@@ -60,7 +60,7 @@ cd ${LINKIS_HOME}/sbin
sh linkis-daemon.sh restart cg-engineplugin
```
More engineplugin details can be found in the following article.
-https://linkis.apache.org/zh-CN/docs/1.1.1/deployment/engine_conn_plugin_installation
+https://linkis.apache.org/zh-CN/docs/1.1.1/deployment/engine-conn-plugin-installation
## 3.Sqoop Engine Usage
diff --git a/docs/introduction.md b/docs/introduction.md
index d8b8060588..4bb0169ba9 100644
--- a/docs/introduction.md
+++ b/docs/introduction.md
@@ -51,8 +51,8 @@ Since the first release of Linkis in 2019, it has accumulated more than **700**
Please go to the [Linkis releases page](https://github.com/apache/incubator-linkis/releases) to download a compiled distribution or a source code package of Linkis.
## Compile and deploy
-Please follow [Compile Guide](development/linkis_compile_and_package.md) to compile Linkis from source code.
-Please refer to [Deployment_Documents](deployment/quick_deploy.md) to do the deployment.
+Please follow [Compile Guide](development/linkis-compile-and-package.md) to compile Linkis from source code.
+Please refer to [Deployment_Documents](deployment/quick-deploy.md) to do the deployment.
## Examples and Guidance
You can find examples and guidance for how to use and manage Linkis in [User_Manual](user_guide/overview.md), [Engine_Usage_Documents](engine_usage/overview.md) and [API_Documents](../docs/api/overview.md).
diff --git a/docs/release.md b/docs/release.md
index ee80b8455d..6c14d5f9df 100644
--- a/docs/release.md
+++ b/docs/release.md
@@ -3,11 +3,11 @@ title: Version overview
sidebar_position: 0.1
---
-- [Enable Prometheus monitoring](/deployment/involve_prometheus_into_linkis.md)
+- [Enable Prometheus monitoring](/deployment/involve-prometheus-into-linkis.md)
- [Custom Variable Design & Built-in Variables](/architecture/commons/variable.md)
-- [EngineConn History Information Recording Features](/architecture/computation_governance_services/engine/engine_conn_history.md)
-- [EngineConn Metrics reporting feature](/architecture/computation_governance_services/engine/engine_conn_metrics.md)
-- [ContextService cleanup interface features](/architecture/public_enhancement_services/context_service/content_service_cleanup.md)
+- [EngineConn History Information Recording Features](/architecture/computation_governance_services/engine/engine-conn-history.md)
+- [EngineConn Metrics reporting feature](/architecture/computation_governance_services/engine/engine-conn-metrics.md)
+- [ContextService cleanup interface features](/architecture/public_enhancement_services/context_service/content-service-cleanup.md)
- [Release-Notes](release-notes-1.1.3)
## Configuration Item
diff --git a/docs/tuning_and_troubleshooting/_category_.json b/docs/tuning-and-troubleshooting/_category_.json
similarity index 100%
rename from docs/tuning_and_troubleshooting/_category_.json
rename to docs/tuning-and-troubleshooting/_category_.json
diff --git a/docs/tuning_and_troubleshooting/configuration.md b/docs/tuning-and-troubleshooting/configuration.md
similarity index 100%
rename from docs/tuning_and_troubleshooting/configuration.md
rename to docs/tuning-and-troubleshooting/configuration.md
diff --git a/docs/tuning_and_troubleshooting/overview.md b/docs/tuning-and-troubleshooting/overview.md
similarity index 98%
rename from docs/tuning_and_troubleshooting/overview.md
rename to docs/tuning-and-troubleshooting/overview.md
index 1211422047..3d2ba065a5 100644
--- a/docs/tuning_and_troubleshooting/overview.md
+++ b/docs/tuning-and-troubleshooting/overview.md
@@ -100,4 +100,4 @@ For problems that cannot be resolved according to the above process positioning
### Ⅵ. locate the source code by remote debug
-Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode_hierarchical_structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
+Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode-hierarchical-structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
diff --git a/docs/tuning_and_troubleshooting/tuning.md b/docs/tuning-and-troubleshooting/tuning.md
similarity index 100%
rename from docs/tuning_and_troubleshooting/tuning.md
rename to docs/tuning-and-troubleshooting/tuning.md
diff --git a/docs/upgrade/upgrade_from_0.X_to_1.0_guide.md b/docs/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 95%
rename from docs/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to docs/upgrade/upgrade-from-0.X-to-1.0-guide.md
index 447bc141b1..60c1bed5a9 100644
--- a/docs/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/docs/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 1
## 1.Precautions
- **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md)**.
+ **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md)**.
## 2. Service upgrade installation
@@ -15,7 +15,7 @@ sidebar_position: 1
If you need to keep 0.X data during the upgrade, you must select 1 to skip the table building statement (see the code below).
- For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ source linkis_configuration_dml.sql
## 4. Installation and startup Linkis1.0
- Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
diff --git a/docs/upgrade/upgrade_guide.md b/docs/upgrade/upgrade-guide.md
similarity index 98%
rename from docs/upgrade/upgrade_guide.md
rename to docs/upgrade/upgrade-guide.md
index eaa72e78a3..230c516eba 100644
--- a/docs/upgrade/upgrade_guide.md
+++ b/docs/upgrade/upgrade-guide.md
@@ -18,7 +18,7 @@ sidebar_position: 2
## 2 Service upgrade installation
-Press [Deployment guide document](../deployment/quick_deploy) (the installation of the management console in the document can be skipped) to install the new version.
+Press [Deployment guide document](../deployment/quick-deploy) (the installation of the management console in the document can be skipped) to install the new version.
When installing the service, if the historical data is retained, please retain the historical data, if you do not need to retain the data, just reinstall it directly
```shell script
diff --git a/docs/user_guide/console_manual.md b/docs/user_guide/console-manual.md
similarity index 100%
rename from docs/user_guide/console_manual.md
rename to docs/user_guide/console-manual.md
diff --git a/docs/user_guide/how_to_use.md b/docs/user_guide/how-to-use.md
similarity index 94%
copy from docs/user_guide/how_to_use.md
copy to docs/user_guide/how-to-use.md
index a7654d58ce..8d84c4ec80 100644
--- a/docs/user_guide/how_to_use.md
+++ b/docs/user_guide/how-to-use.md
@@ -10,9 +10,9 @@ sidebar_position: 1
## 1. Client side usage
If you need to connect to other applications on the basis of Linkis, you need to develop the interface provided by Linkis. Linkis provides a variety of client access interfaces. For detailed usage introduction, please refer to the following:
-- [**Restful API Usage**](api/linkis_task_operator.md)
-- [**JDBC API Usage**](api/jdbc_api.md)
-- [**How to use Java SDK**](user_guide/sdk_manual.md)
+- [**Restful API Usage**](api/linkis-task-operator.md)
+- [**JDBC API Usage**](api/jdbc-api.md)
+- [**How to use Java SDK**](../user_guide/sdk-manual.md)
## 2. Scriptis uses Linkis
diff --git a/docs/user_guide/linkiscli_manual.md b/docs/user_guide/linkiscli-manual.md
similarity index 100%
rename from docs/user_guide/linkiscli_manual.md
rename to docs/user_guide/linkiscli-manual.md
diff --git a/docs/user_guide/overview.md b/docs/user_guide/overview.md
index 2a6d4b1b9b..3aa5f4450a 100644
--- a/docs/user_guide/overview.md
+++ b/docs/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis considered the scalability of the access method at the beginning of the design. For different access scenarios, Linkis provides front-end access and SDK access. HTTP and WebSocket interfaces are also provided on the basis of front-end interfaces. If you are interested in accessing and using Linkis, you can refer to the following documents:
-- [How to Use Links](how_to_use.md)
-- [Linkis Management Console Manual](console_manual.md)
-- [Linkis1.0 SDK Manual](sdk_manual.md)
-- [Linkis-Cli Manual](linkiscli_manual.md)
+- [How to Use Links](how-to-use.md)
+- [Linkis Management Console Manual](console-manual.md)
+- [Linkis1.0 SDK Manual](sdk-manual.md)
+- [Linkis-Cli Manual](linkiscli-manual.md)
diff --git a/docs/user_guide/sdk_manual.md b/docs/user_guide/sdk-manual.md
similarity index 100%
rename from docs/user_guide/sdk_manual.md
rename to docs/user_guide/sdk-manual.md
diff --git a/download/main.md b/download/main.md
index e111281632..e7085c5f08 100644
--- a/download/main.md
+++ b/download/main.md
@@ -51,4 +51,4 @@ $ ./mvnw -N install
$ ./mvnw clean install -Dmaven.javadoc.skip=true -Dmaven.test.skip=true
````
-For detailed guidelines, please refer to: [Compilation and Packaging Guidelines](/docs/latest/development/linkis_compile_and_package)
\ No newline at end of file
+For detailed guidelines, please refer to: [Compilation and Packaging Guidelines](/docs/latest/development/linkis-compile-and-package)
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-blog/2022-02-08-how-to-user-blog.md b/i18n/zh-CN/docusaurus-plugin-content-blog/2022-02-08-how-to-user-blog.md
index b293d956bb..ce08fd2942 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-blog/2022-02-08-how-to-user-blog.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-blog/2022-02-08-how-to-user-blog.md
@@ -73,7 +73,7 @@ slug: welcome-docusaurus-v2
authors:
- name: Joel Marcey
title: Co-creator of Docusaurus 1
- url: https://github.com/JoelMarceyengine_conn_plugin_installation
+ url: https://github.com/JoelMarceyengine-conn-plugin-installation
image_url: https://github.com/JoelMarcey.png
- name: Sébastien Lorber
title: Docusaurus maintainer
diff --git a/i18n/zh-CN/docusaurus-plugin-content-blog/2022-02-21-linkis-deploy.md b/i18n/zh-CN/docusaurus-plugin-content-blog/2022-02-21-linkis-deploy.md
index 76606dd570..0b9dc2046d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-blog/2022-02-21-linkis-deploy.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-blog/2022-02-21-linkis-deploy.md
@@ -269,7 +269,7 @@ Your default account password is [hadoop/5e8e312b4]`
### 3.4 添加mysql驱动(>=1.0.3)版本
因为license原因，linkis官方发布包中(dss集成的全家桶会包含，无需手动添加)移除了mysql-connector-java，需要手动添加
-具体参见[ 添加mysql驱动包](/docs/latest/deployment/quick_deploy#-44-添加mysql驱动包)
+具体参见[ 添加mysql驱动包](/docs/latest/deployment/quick-deploy#-44-添加mysql驱动包)
### 3.5 启动服务
```shell script
@@ -435,7 +435,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
查看引擎的物料记录是否存在(如果有更新,查看更新时间是否正确)。
-如果不存在或则未更新，先尝试手动刷新物料资源(详细见[引擎物料资源刷新](/docs/latest/deployment/engine_conn_plugin_installation#23-引擎刷新))。通过`log/linkis-cg-engineplugin.log`日志，查看物料失败的具体原因，很多时候可能是hdfs目录没有权限导致，检查gateway地址配置是否正确`conf/linkis.properties:wds.linkis.gateway.url`
+如果不存在或则未更新，先尝试手动刷新物料资源(详细见[引擎物料资源刷新](/docs/latest/deployment/engine-conn-plugin-installation#23-引擎刷新))。通过`log/linkis-cg-engineplugin.log`日志，查看物料失败的具体原因，很多时候可能是hdfs目录没有权限导致，检查gateway地址配置是否正确`conf/linkis.properties:wds.linkis.gateway.url`
引擎的物料资源默认上传到hdfs目录为 `/apps-data/${deployUser}/bml`
```shell script
@@ -546,7 +546,7 @@ CDH本身不是使用的官方标准的hive/spark包,进行适配时，最好修
### 9.5 Http接口的调试
-- 方式1 可以开启[免登陆模式指引](/docs/latest/api/login_api/#2免登录配置)
+- 方式1 可以开启[免登陆模式指引](/docs/latest/api/login-api/#2免登录配置)
- 方式2 postman中的，请求头带上登陆成功的cookie值
cookie值可以在浏览器端登陆成功后，获取
diff --git a/i18n/zh-CN/docusaurus-plugin-content-blog/2022-04-15-how-to-download-engineconn-plugin.md b/i18n/zh-CN/docusaurus-plugin-content-blog/2022-04-15-how-to-download-engineconn-plugin.md
index 3562a5607e..a575d66265 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-blog/2022-04-15-how-to-download-engineconn-plugin.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-blog/2022-04-15-how-to-download-engineconn-plugin.md
@@ -79,5 +79,5 @@ cd 1.0.3-engineconn-plugin
将需要要使用的引擎物料包拷贝至linkis的引擎插件目录，然后刷新引擎物料即可
-详细流程参考[安装 EngineConnPlugin 引擎](https://linkis.apache.org/zh-CN/docs/latest/deployment/engine_conn_plugin_installation)。
+详细流程参考[安装 EngineConnPlugin 引擎](https://linkis.apache.org/zh-CN/docs/latest/deployment/engine-conn-plugin-installation)。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-blog/2022-05-12-release-1.1.1.md b/i18n/zh-CN/docusaurus-plugin-content-blog/2022-05-12-release-1.1.1.md
index 09a6f5083e..a6cf43119e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-blog/2022-05-12-release-1.1.1.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-blog/2022-05-12-release-1.1.1.md
@@ -28,7 +28,7 @@ linkis在执行用户提交的任务时，linkis的主进程会通过 sudo -u ${
### 新特性2 UDF支持多版本控制
1.1.1版本之前无法支持UDF多版本的控制，无法对某个UDF函数的历史版本进行查看和回退，并且UDF函数jar包/脚本物料是存储在服务器的主机上，如果更换服务器的话，需要做UDF函数jar包/脚本物料的同步迁移。
新增linkis_ps_udf_version表 ，以支持UDF函数的多版本存储，依赖于目前linkis已有的BML物料管理功能，将udf函数的jar/脚本物料上传至BML管理的hdfs文件系统中。
-具体使用方式见：https://linkis.apache.org/zh-CN/docs/latest/user_guide/udf
+具体使用方式见：https://linkis.apache.org/zh-CN/docs/latest/../user_guide/udf
### 新特性3 新增数据虚拟化openLooKeng引擎插件
openLooKeng用于支持数据探索、即席查询和批处理，具有100+毫秒至分钟级的近实时时延，而无需移动数据。openLooKeng还支持层次化部署，使地理上远程的openLooKeng集群能够参与相同的查询。利用其跨区域查询计划优化能力，涉及远程数据的查询可以达到接近“本地”的性能。
@@ -117,6 +117,6 @@ Apache Linkis(incubating) 1.1.1的发布离不开Linkis社区的贡献者,感谢
## 详细指引
本版本总览: https://linkis.apache.org/zh-CN/docs/latest/release
-详细安装部署见指引：https://linkis.apache.org/zh-CN/docs/latest/deployment/quick_deploy
+详细安装部署见指引：https://linkis.apache.org/zh-CN/docs/latest/deployment/quick-deploy
官方下载链接：https://linkis.apache.org/zh-CN/download/main
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/exception_catch.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/exception-catch.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/exception_catch.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/exception-catch.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/overview.md
index d32266893e..ed4cde6e9c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/overview.md
@@ -5,14 +5,14 @@ sidebar_position: 0
为了规范 Linkis 的社区开发环境，提高 Linkis 后续版本开发迭代的产出质量，规范 Linkis 的整个开发设计流程，强烈建议各位 Contributor 遵守以下开发规范：
- [License 须知](license.md)
-- [编程规范](programming_specification.md)
+- [编程规范](programming-specification.md)
- [日志规范](log.md)
-- [异常规范](exception_catch.md)
+- [异常规范](exception-catch.md)
- [接口规范](api.md)
- [并发规范](concurrent.md)
-- [路径规范](path_usage.md)
-- [测试规范](unit_test.md)
-- [版本和新特性规范](version_feature_specifications.md)
+- [路径规范](path-usage.md)
+- [测试规范](unit-test.md)
+- [版本和新特性规范](version-feature-specifications.md)
**说明**：Linkis1.0 初始版本的开发规范较为精简，后续会随着 Linkis 的版本迭代不断补充和完善，欢迎各位 Contributor 提出自己的见解和意见。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/path_usage.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/path-usage.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/path_usage.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/path-usage.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/programming_specification.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/programming-specification.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/programming_specification.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/programming-specification.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/unit_test.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/unit-test.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/unit_test.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/unit-test.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/version_feature_specifications.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/version-feature-specifications.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/version_feature_specifications.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs-community/current/development_specification/version-feature-specifications.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute-to-website.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute-to-website.md
index 700aed257d..d2d46d4045 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute-to-website.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute-to-website.md
@@ -158,7 +158,7 @@ Visit the page https://linkis.apache.org/zh-CN/user
公司的logo位于 `static/home/user`, 且图片的大小必须是 176 × 88.
### 3.10 路径规范
-如果希望想从一个markdown文档链接到另外一个文档, 最好使用绝对路径. 例如, 如果希望链接到 `quick_deploy.md`这个文档, 路径应写成 `/docs/deployment/quick_deploy.md`。
+如果希望想从一个markdown文档链接到另外一个文档, 最好使用绝对路径. 例如, 如果希望链接到 `quick-deploy.md`这个文档, 路径应写成 `/docs/deployment/quick-deploy.md`。
### 英文文档标题规范
英文文档侧边栏除介词外的所有词首字母使用大写, 同时英文markdown中的标题的第一个词首字母应大写，其他词首字母小写。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-download/current/main.md b/i18n/zh-CN/docusaurus-plugin-content-docs-download/current/main.md
index 68da400ccd..652d343bb9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-download/current/main.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-download/current/main.md
@@ -50,5 +50,5 @@ $ ./mvnw -N install
$ ./mvnw clean install -Dmaven.javadoc.skip=true -Dmaven.test.skip=true
```
-详细指引可以参考：[编译打包指引](/docs/latest/development/linkis_compile_and_package)
+详细指引可以参考：[编译打包指引](/docs/latest/development/linkis-compile-and-package)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-faq/current/main.md b/i18n/zh-CN/docusaurus-plugin-content-docs-faq/current/main.md
index 8109cdea62..9829f81626 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-faq/current/main.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-faq/current/main.md
@@ -26,7 +26,7 @@ A: 这个是因为eureka的启动Java进程时没有使用nohup当会话退出
可以参考PR：https://github.com/apache/incubator-linkis/pull/837/files
#### Q4: Linkis Entrance LogWriter 缺依赖包
-A: Hadoop 3需修改linkis-hadoop-common pom文件，详见：https://linkis.apache.org/zh-CN/docs/next/development/linkis_compile_and_package/
+A: Hadoop 3需修改linkis-hadoop-common pom文件，详见：https://linkis.apache.org/zh-CN/docs/next/development/linkis-compile-and-package/
#### Q5: Linkis1.0 执行任务报： select list is not in group by clause
@@ -344,7 +344,7 @@ Failed to async get EngineNode ErrorException: errCode: 0 ,desc: operation fail
```
解决办法
-需要安装下对应的引擎插件，可以参考：[引擎安装指引](/docs/latest/deployment/engine_conn_plugin_installation)
+需要安装下对应的引擎插件，可以参考：[引擎安装指引](/docs/latest/deployment/engine-conn-plugin-installation)
#### Q37.关闭资源检查
报错现象：资源不足
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/api/jdbc_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/api/jdbc-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/api/jdbc_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/api/jdbc-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/api/linkis_task_operator.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/api/linkis-task-operator.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/api/linkis_task_operator.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/api/linkis-task-operator.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/api/login_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/api/login-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/api/login_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/api/login-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/api/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/api/overview.md
index 987616848e..a4d0d3889a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/api/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 1
## 1. 文档说明
Linkis1.0 在Linkix0.x版本的基础上进行了重构优化，同时也兼容了0.x的接口，但是为了防止在使用1.0版本时存在兼容性问题，需要您仔细阅读以下文档：
-1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login_api.md)。
+1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login-api.md)。
-2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc_api.md)。
+2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc-api.md)。
-3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis_task_operator.md)。
\ No newline at end of file
+3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis-task-operator.md)。
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/add_an_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/add-an-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/add_an_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/add-an-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine_conn_history.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine-conn-history.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine_conn_history.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine-conn-history.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine_conn_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine_conn_metrics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine-conn-metrics.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine_conn_metrics.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine-conn-metrics.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine_conn_plugin.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
index ca770ffcd1..ca0d7211e4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
@@ -38,7 +38,7 @@ sidebar_position: 1
1. 首先，Client（如前端或客户端）发起Job请求，Job请求信息精简如下
-（关于Linkis的具体使用方式，请参考 [如何使用Linkis](user_guide/how_to_use.md)）：
+（关于Linkis的具体使用方式，请参考 [如何使用Linkis](../../user_guide/how-to-use.md)）：
```
POST /api/rest_j/v1/entrance/submit
@@ -74,7 +74,7 @@ POST /api/rest_j/v1/entrance/submit
如何定义可复用EngineConn？指能匹配计算任务的所有标签要求的，且EngineConn本身健康状态为Healthy（负载低且实际EngineConn状态为Idle）的，然后再按规则对所有满足条件的EngineConn进行排序选择，最终锁定一个最佳的EngineConn。
-如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](engine/add_an_engine_conn.md) 。
+如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](engine/add-an-engine-conn.md) 。
#### 2.2 计算任务编排
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/app_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/label_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/resource_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/overview.md
index 65ea36c02d..b77e15fd3a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/overview.md
@@ -66,10 +66,10 @@ Linkis1.0将优化Job的整体执行流程，从提交 —\> 准备 —\>
EngineConnManager (简称ECM)是 Linkis0.X EngineManager 的精简升级版。Linkis1.0下的ECM去除了引擎的申请能力，整个微服务完全无状态，将聚焦于支持各类 EngineConn 的启动和销毁。
- [进入EngineConnManager架构设计](engine/engine_conn_manager.md)
+ [进入EngineConnManager架构设计](engine/engine-conn-manager.md)
### 5、EngineConn
EngineConn 是 Linkis0.X Engine 的优化升级版本，将提供 EngineConn 和 Executor 两大模块，其中 EngineConn 用于连接底层的计算存储引擎，提供一个打通了底层各计算存储引擎的 Session 会话；Executor 则基于这个 Session 会话，提供交互式计算、流式计算、离线计算、数据存储的全栈计算能力支持。
-[进入EngineConn架构设计](engine/engine_conn.md)
+[进入EngineConn架构设计](engine/engine-conn.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/proxy_user.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/proxy-user.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/proxy_user.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/computation_governance_services/proxy-user.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/difference_between_1.0_and_0.x.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/difference_between_1.0_and_0.x.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/difference-between-1.0-and-0.x.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/overview.md
index 28f24690a5..1fdb1b395d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/overview.md
@@ -18,7 +18,7 @@ Linkis 1.0 将所有微服务总体划分为三大类：公共增强服务、计
以下是 Linkis1.0 架构文档的目录列表：
-1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference_between_1.0_and_0.x)。
+1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference-between-1.0-and-0.x)。
2. Linkis1.0公共增强服务相关文档，请阅读[公共增强服务](public_enhancement_services/overview.md)。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/bml/engine_bml_dissect.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/bml/engine-bml-dissect.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/bml/engine_bml_dissect.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/bml/engine-bml-dissect.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/content_service_cleanup.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/content-service-cleanup.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/content_service_cleanup.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/content-service-cleanup.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_cache.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_client.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_client.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_listener.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_persistence.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_search.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service_search.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/overview.md
index 2992203775..68591cc538 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/context_service/overview.md
@@ -101,29 +101,29 @@ CS，用于解决一个数据应用开发流程，跨多个系统间的数据和
### 1. Client
外部访问CS的入口，Client模块提供HA功能；
-[进入Client架构设计](context_service_client.md)
+[进入Client架构设计](context-service-client.md)
### 2. Service模块
提供Restful接口，封装和处理客户端提交的CS请求；
-[进入Service架构设计](context_service.md)
+[进入Service架构设计](context-service.md)
### 3. ContextSearch
上下文查询模块，提供丰富和强大的查询能力，供客户端查找上下文的Key-Value键值对；
-[进入ContextSearch架构设计](context_service_search.md)
+[进入ContextSearch架构设计](context-service-search.md)
### 4. Listener
CS的监听器模块，提供同步和异步的事件消费能力，具备类似Zookeeper的Key-Value一旦更新，实时通知Client的能力；
-[进入Listener架构设计](context_service_listener.md)
+[进入Listener架构设计](context-service-listener.md)
### 5. ContextCache
上下文的内存缓存模块，提供快速检索上下文的能力和对JVM内存使用的监听和清理能力；
-[进入ContextCache架构设计](context_service_cache.md)
+[进入ContextCache架构设计](context-service-cache.md)
### 6. HighAvailable
提供CS高可用能力；
-[进入HighAvailable架构设计](context_service_highavailable.md)
+[进入HighAvailable架构设计](context-service-highavailable.md)
### 7. Persistence
CS的持久化功能；
-[进入Persistence架构设计](context_service_persistence.md)
+[进入Persistence架构设计](context-service-persistence.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/datasource_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/datasource-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/datasource_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/datasource-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/metadata_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/metadata-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/metadata_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/metadata-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/public_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/public_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/architecture/public_enhancement_services/public-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/cluster_deployment.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/cluster-deployment.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/cluster_deployment.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/cluster-deployment.md
index d27e6b8600..8b057e86db 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/cluster_deployment.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/cluster-deployment.md
@@ -98,7 +98,7 @@ EngineConnManager（ECM）使用总资源
模式：Eureka服务多活部署 ，部分服务部署在服务器A，部分服务部署在服务器B上
### 2.1 分布式部署的环境准备
-和服务器A一样，服务器B需要进行基础的环境准备，请参考[Linkis环境准备](quick_deploy#3-linkis%E7%8E%AF%E5%A2%83%E5%87%86%E5%A4%87)
+和服务器A一样，服务器B需要进行基础的环境准备，请参考[Linkis环境准备](quick-deploy#3-linkis%E7%8E%AF%E5%A2%83%E5%87%86%E5%A4%87)
### 2.2 Eureka多活配置调整
注册中心Eureka服务，需要部署在服务器A和服务器B上，
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/deploy_linkis_without_hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/deploy-linkis-without-hdfs.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/deploy_linkis_without_hdfs.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/deploy-linkis-without-hdfs.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/engine_conn_plugin_installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/engine_conn_plugin_installation.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/engine-conn-plugin-installation.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/installation_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/installation_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/installation-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve_knife4j_into_linkis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve-knife4j-into-linkis.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve_knife4j_into_linkis.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve-knife4j-into-linkis.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve_prometheus_into_linkis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve-prometheus-into-linkis.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve_prometheus_into_linkis.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve-prometheus-into-linkis.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve_skywalking_into_linkis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve-skywalking-into-linkis.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve_skywalking_into_linkis.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/involve-skywalking-into-linkis.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/linkis_scriptis_install.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/linkis-scriptis-install.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/linkis_scriptis_install.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/linkis-scriptis-install.md
index ec0c4be813..b4ed7a3c02 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/linkis_scriptis_install.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/linkis-scriptis-install.md
@@ -8,7 +8,7 @@ sidebar_position: 10
> 在 Apache Linkis >= 1.1.1 和 DSS >= 1.1.0 之后，支持将 scriptis 单独部署和 Linkis 进行搭配使用，使用 scriptis 的交互式分析的功能，可以在 web 页面在线写 SQL、Pyspark、HiveQL 等脚本，提交给 Linkis 执行且支持 UDF、函数、资源管控和自定义变量等特性，本文将介绍如何单独部署 Web 组件-scriptis，并通过 scriptis 这种 Web 页面来使用 Apache Linkis 。
-前提:已经成功安装并可以正常使用了 Linkis 服务（后端和管理台服务），Linkis 的部署流程可以见[Apache Linkis 的快速部署 ](quick_deploy.md)
+前提:已经成功安装并可以正常使用了 Linkis 服务（后端和管理台服务），Linkis 的部署流程可以见[Apache Linkis 的快速部署 ](quick-deploy.md)
示例说明:
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/quick_deploy.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/quick-deploy.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/quick_deploy.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/quick-deploy.md
index d46077bd12..1055271f4d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/quick_deploy.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/quick-deploy.md
@@ -43,7 +43,7 @@ hadoop ALL=(ALL) NOPASSWD: NOPASSWD: ALL
### 2.1 安装包准备
- 方式1：从官网[下载地址](https://linkis.apache.org/zh-CN/download/main):https://linkis.apache.org/zh-CN/download/main，下载对应的安装包(项目安装包和管理台安装包)
-- 方式2：根据[Linkis 编译打包](../development/linkis_compile_and_package)和[前端管理台编译](../development/web_build) 自行编译出项目安装包和管理台安装包
+- 方式2：根据[Linkis 编译打包](../development/linkis-compile-and-package)和[前端管理台编译](../development/web-build) 自行编译出项目安装包和管理台安装包
上传安装包`apache-linkis-x.x.x-incubating-bin.tar.gz`后，进行解压安装包
@@ -387,7 +387,7 @@ wds.linkis.admin.user= #用户
wds.linkis.admin.password= #密码
```
-管理台使用指引见[使用手册](user_guide/console_manual.md)
+管理台使用指引见[使用手册](../user_guide/console-manual.md)
## 5. 验证基础功能
>根据实际需求，验证对应的引擎任务
@@ -411,13 +411,13 @@ sh bin/linkis-cli -submitUser hadoop -engineType python-python2 -codeType pyth
## 6 开发工具IDE（Scriptis）的安装(可选)
>安装Scripti工具后，可以支持在web页面在线写SQL、Pyspark、HiveQL等脚本
-详细指引见[工具Scriptis的安装部署](./linkis_scriptis_install)
+详细指引见[工具Scriptis的安装部署](./linkis-scriptis-install)
## 7. 支持的引擎
### 7.1 引擎适配列表
-请注意：Linkis的单独安装包默认只包含的：Python/Shell/Hive/Spark四个引擎，如果有其他的引擎(如jdbc/flink/sqoop等引擎)使用场景，可以手动安装，具体请参考 [EngineConnPlugin引擎插件安装文档](engine_conn_plugin_installation)。
+请注意：Linkis的单独安装包默认只包含的：Python/Shell/Hive/Spark四个引擎，如果有其他的引擎(如jdbc/flink/sqoop等引擎)使用场景，可以手动安装，具体请参考 [EngineConnPlugin引擎插件安装文档](engine-conn-plugin-installation)。
本版本已适配的支持引擎列表如下：
@@ -525,7 +525,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
查看引擎的物料记录是否存在(如果有更新,查看更新时间是否正确)。
-- 如果不存在或则未更新，先尝试手动刷新物料资源(详细见[引擎物料资源刷新](engine_conn_plugin_installation#23-引擎刷新))。
+- 如果不存在或则未更新，先尝试手动刷新物料资源(详细见[引擎物料资源刷新](engine-conn-plugin-installation#23-引擎刷新))。
- 通过`log/linkis-cg-engineplugin.log`日志，查看物料失败的具体原因，很多时候可能是hdfs目录没有权限导致
- 检查gateway地址配置是否正确`conf/linkis.properties`的配置项`wds.linkis.gateway.url`
@@ -622,7 +622,7 @@ CDH本身不是使用的官方标准的hive/spark包,进行适配时，最好修
### 8.9 Http接口的调试
-- 方式1 可以开启[免登陆模式指引](/docs/latest/api/login_api/#2免登录配置)
+- 方式1 可以开启[免登陆模式指引](/docs/latest/api/login-api/#2免登录配置)
- 方式2 postman中的，请求头带上登陆成功的cookie值
cookie值可以在浏览器端登陆成功后，获取
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/sourcecode_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/sourcecode_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/sourcecode-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/start_metadatasource.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/start-metadatasource.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/start_metadatasource.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/start-metadatasource.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/unpack_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/unpack-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/unpack_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/unpack-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/web_install.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/web-install.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/web_install.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/web-install.md
index 7518e9267b..a3a9dbbce2 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/web_install.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/web-install.md
@@ -5,7 +5,7 @@ sidebar_position: 6
> web端是使用nginx作为静态资源服务器的，访问请求流程是:`Linkis管理台请求->nginx ip:port->linkis-gateway ip:port-> 其他服务`
-Linkis 提供了单独的前端管理台功能，提供了展示历史任务的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick_deploy.md)
+Linkis 提供了单独的前端管理台功能，提供了展示历史任务的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick-deploy.md)
## 1 准备工作
@@ -167,7 +167,7 @@ wds.linkis.admin.user= #用户
wds.linkis.admin.password= #密码
```
-管理台使用指引见[使用手册](user_guide/console_manual.md)
+管理台使用指引见[使用手册](../user_guide/console-manual.md)
## 4 注意事项
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis_compile_and_package.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis-compile-and-package.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis_compile_and_package.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis-compile-and-package.md
index 6679eaf944..da0b786f7f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis_compile_and_package.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis-compile-and-package.md
@@ -107,7 +107,7 @@ __编译环境要求：__ 必须 **JDK8** 以上，**Oracle/Sun** 和 **OpenJDK
#spark文件下就是编译好的引擎物料
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/out/spark
```
-如何单独安装 Spark 引擎？请参考 [Linkis 引擎插件安装文档](../deployment/engine_conn_plugin_installation)
+如何单独安装 Spark 引擎？请参考 [Linkis 引擎插件安装文档](../deployment/engine-conn-plugin-installation)
### 3.2 如何将非默认引擎打包至安装部署包中
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis_config.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis-config.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis_config.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis-config.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis_debug_in_mac.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis-debug-in-mac.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis_debug_in_mac.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis-debug-in-mac.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis_debug.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis-debug.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis_debug.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis-debug.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/new_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/new-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/development/new_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/development/new-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/swwager_instructions.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/swwager-instructions.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/development/swwager_instructions.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/development/swwager-instructions.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/web_build.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/web-build.md
similarity index 97%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/development/web_build.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/development/web-build.md
index 231301ad11..7f971bcad5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/web_build.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/web-build.md
@@ -38,7 +38,7 @@ $ npm install
```
$ npm run build
```
-上述命令执行成功后，会生成前端管理台安装包 `apache-linkis-${version}-incubating-web-bin.tar.gz`，可以直接将该文件夹放进您的静态服务器中，或者参考[安装文档](../deployment/web_install.md)，使用脚本进行部署安装。
+上述命令执行成功后，会生成前端管理台安装包 `apache-linkis-${version}-incubating-web-bin.tar.gz`，可以直接将该文件夹放进您的静态服务器中，或者参考[安装文档](../deployment/web-install.md)，使用脚本进行部署安装。
## 3 . 注意事项
### 3.1 Windows下npm install 步骤报错
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/elasticsearch.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/elasticsearch.md
index 2a4291aa3a..8fecfb9331 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/elasticsearch.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/elasticsearch.md
@@ -43,7 +43,7 @@ sh linkis-daemon.sh restart cg-engineplugin
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.2 ElasticSearch 引擎相关配置
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/flink.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/flink.md
index 12979f32cf..cfd311edf9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/flink.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/flink.md
@@ -58,12 +58,12 @@ cd ${LINKIS_HOME}/sbin
sh linkis-daemon.sh restart cg-engineplugin
```
engineplugin更详细的介绍可以参看下面的文章。
-https://linkis.apache.org/zh-CN/docs/1.1.1/deployment/engine_conn_plugin_installation
+https://linkis.apache.org/zh-CN/docs/1.1.1/deployment/engine-conn-plugin-installation
### 2.3 Flink引擎的标签
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3.Flink引擎的使用
@@ -117,7 +117,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
sh ./bin/linkis-cli -engineType flink-1.12.2 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 OnceEngineConn方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/hive.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/hive.md
index 47116ad53a..277c76d7a4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/hive.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/hive.md
@@ -35,13 +35,13 @@ on Tez，需要您按照此pr进行一下修改。
如果您已经编译完了您的hive引擎的插件已经编译完成，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 hive引擎的标签
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.hive引擎的使用
@@ -57,7 +57,7 @@ hive的MapReduce任务是需要用到yarn的资源，所以需要您在一开始
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Hive任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -73,7 +73,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType hive-2.3.3 -codeType hql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/jdbc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/jdbc.md
index fcd68a8f81..ef28f4d89f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/jdbc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/jdbc.md
@@ -44,7 +44,7 @@ sh linkis-daemon.sh restart cg-engineplugin
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3.JDBC引擎的使用
@@ -91,7 +91,7 @@ http 请求参数示例
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于JDBC任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -107,7 +107,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/openlookeng.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/openlookeng.md
index de4bb7a6a6..0ae5796613 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/openlookeng.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/openlookeng.md
@@ -47,7 +47,7 @@ sh linkis-daemon.sh restart cg-engineplugin
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3 引擎的使用
@@ -84,7 +84,7 @@ http 请求参数示例
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于openlookeng任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -100,5 +100,5 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType openlookeng-1.5.0 -codeType sql -code 'show databases;' -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/pipeline.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/pipeline.md
index 0f798f79b4..7a5c2213cf 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/pipeline.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/pipeline.md
@@ -55,7 +55,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 2 引擎的使用
@@ -73,7 +73,7 @@ sh bin/linkis-cli -submitUser hadoop -engineType pipeline-1 -codeType pipelin
```
`from hdfs:///000/000/000/A.dolphin to file:///000/000/000/B.csv` 该内容 2.3 有解释
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/presto.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/presto.md
index aa519a13e6..0569343d59 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/presto.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/presto.md
@@ -44,7 +44,7 @@ sh linkis-daemon.sh restart cg-engineplugin
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.2 Presto 引擎相关配置
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/python.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/python.md
index 48ac0e1a2e..fd94cba3db 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/python.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/python.md
@@ -46,7 +46,7 @@ sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"h
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Python任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -62,7 +62,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/shell.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/shell.md
index d40e903ad7..6a509306ac 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/shell.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/shell.md
@@ -37,7 +37,7 @@ Shell引擎不需要用户自行编译，直接使用编译好的shell引擎插
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Shell任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -53,7 +53,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/spark.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/spark.md
index 57b94b72d9..0c5eb603ef 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/spark.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/spark.md
@@ -33,13 +33,13 @@ sidebar_position: 1
如果您已经编译完了您的spark引擎的插件，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 spark引擎的标签
Linkis1.X是通过标签配置来区分引擎版本的，所以需要我们在数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.spark引擎的使用
@@ -54,7 +54,7 @@ Linkis1.X是通过标签配置来区分引擎版本的，所以需要我们在
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Spark任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -74,7 +74,7 @@ sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -
# 可以在提交参数通过-confMap wds.linkis.yarnqueue=dws 来指定yarn 队列
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -confMap wds.linkis.yarnqueue=dws -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/sqoop.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/sqoop.md
index 97258268aa..8e52c0f7d8 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/sqoop.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/engine_usage/sqoop.md
@@ -72,7 +72,7 @@ sh linkis-daemon.sh restart cg-engineplugin
```
engineplugin更详细的介绍可以参看下面的文章。
-https://linkis.apache.org/zh-CN/docs/latest/deployment/engine_conn_plugin_installation
+https://linkis.apache.org/zh-CN/docs/latest/deployment/engine-conn-plugin-installation
## 3 Sqoop引擎的使用
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/introduction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/introduction.md
index 2260bb8504..98867e7620 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/introduction.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/introduction.md
@@ -50,7 +50,7 @@ Linkis 自2019年开源发布以来，已累计积累了700多家试验企业和
## 安装部署
-请参考[安装部署文档](deployment/quick_deploy.md) 来部署Linkis
+请参考[安装部署文档](deployment/quick-deploy.md) 来部署Linkis
## 示例和使用指引
- [用户手册](user_guide/overview.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/release.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/release.md
index 9cf4553577..f6225f7c33 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/release.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/release.md
@@ -2,11 +2,11 @@
title: 版本总览
sidebar_position: 0.1
---
-- [开启Prometheus监控](/deployment/involve_prometheus_into_linkis.md)
+- [开启Prometheus监控](/deployment/involve-prometheus-into-linkis.md)
- [自定义变量设计&内置变量](/architecture/commons/variable.md)
-- [EngineConn 历史信息记录特性](/architecture/computation_governance_services/engine/engine_conn_history.md)
-- [EngineConn Metrics 上报特性](/architecture/computation_governance_services/engine/engine_conn_metrics.md)
-- [ContextService 清理接口特性](/architecture/public_enhancement_services/context_service/content_service_cleanup.md)
+- [EngineConn 历史信息记录特性](/architecture/computation_governance_services/engine/engine-conn-history.md)
+- [EngineConn Metrics 上报特性](/architecture/computation_governance_services/engine/engine-conn-metrics.md)
+- [ContextService 清理接口特性](/architecture/public_enhancement_services/context_service/content-service-cleanup.md)
- [版本的Release-Notes](release-notes-1.1.3)
## 参数变化
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/tuning_and_troubleshooting/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/tuning_and_troubleshooting/overview.md
index 337501e74f..3c575cfb57 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/tuning_and_troubleshooting/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/tuning_and_troubleshooting/overview.md
@@ -111,6 +111,6 @@ sidebar_position: 0
### 六、定位源码远程debug
-通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode_hierarchical_structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis_debug.md) 》一文调试对应微服务下的代码。
+通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode-hierarchical-structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis-debug.md) 》一文调试对应微服务下的代码。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade_from_0.X_to_1.0_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 97%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade-from-0.X-to-1.0-guide.md
index 55d8b3aa8a..1c3986b77d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 1
## 1. 注意事项
-**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference_between_1.0_and_0.x.md)**。
+**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference-between-1.0-and-0.x.md)**。
## 2. 服务升级安装
@@ -15,7 +15,7 @@ sidebar_position: 1
在安装时如果需要保留0.X的数据，一定要选择1跳过建表语句（见下面代码）。
-Linkis1.0 的安装可以参考[如何快速安装](deployment/quick_deploy.md)
+Linkis1.0 的安装可以参考[如何快速安装](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ Please input the choice: ## choice 1
## 4. 安装Linkis1.0
- 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装](deployment/quick_deploy.md)
+ 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装](deployment/quick-deploy.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade-guide.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade-guide.md
index 978d8a581a..a79c3ba2be 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade_guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade-guide.md
@@ -18,7 +18,7 @@ sidebar_position: 2
## 2 服务升级安装
-按[部署指引文档](../deployment/quick_deploy)（文档中关于管理台的安装可以跳过），进行新版本的安装。
+按[部署指引文档](../deployment/quick-deploy)（文档中关于管理台的安装可以跳过），进行新版本的安装。
安装服务时，如果历史数据保留，请保留历史数据，如果无需保留数据，直接重装即可，也无需关注升级流程
```shell script
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/console_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/console-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/console_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/console-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how_to_use.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/how-to-use.md
similarity index 94%
copy from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how_to_use.md
copy to i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/how-to-use.md
index bc3e1af344..9627ebc2b5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how_to_use.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/how-to-use.md
@@ -7,9 +7,9 @@ sidebar_position: 1
## 1. Client端使用
如果需要在Linkis的基础上，接入其它应用，需要针对Linkis提供的接口进行开发，Linkis提供了多种客户端接入接口，更详细的使用介绍可以参考以下内容：
-- [**Restful API使用方式**](api/linkis_task_operator.md)
-- [**JDBC API使用方式**](api/jdbc_api.md)
-- [**Java SDK使用方式**](user_guide/sdk_manual.md)
+- [**Restful API使用方式**](api/linkis-task-operator.md)
+- [**JDBC API使用方式**](api/jdbc-api.md)
+- [**Java SDK使用方式**](../user_guide/sdk-manual.md)
## 2. Scriptis使用Linkis
如果需要使用Linkis完成交互式在线分析处理的工作，并且不需要诸如工作流开发、工作流调度、数据服务等数据分析应用工具，可以单独安装[**Scriptis**](https://github.com/WeBankFinTech/Scriptis)，详细安装教程可参考其对应的安装部署文档。
### 2.1. 使用Scriptis执行脚本
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/linkiscli_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/linkiscli-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/linkiscli_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/linkiscli-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/overview.md
index 6f53e8b095..bf7a2e26d6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis在设计之初就考虑接入方式的拓展性问题，针对不同的接入场景，Linkis提供了前端接入和SDK接入的方式，在前端接口上又提供了HTTP和WebSocket两种方式，如果对接入并使用Linkis感兴趣，可以参考以下文档：
-- [如何使用Links](how_to_use.md)
-- [Linkis-Cli的使用](linkiscli_manual.md)
-- [Linkis JAVA SDK的使用](sdk_manual.md)
-- [Linkis管理台的使用](console_manual.md)
+- [如何使用Links](how-to-use.md)
+- [Linkis-Cli的使用](linkiscli-manual.md)
+- [Linkis JAVA SDK的使用](sdk-manual.md)
+- [Linkis管理台的使用](console-manual.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/sdk_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/sdk-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/sdk_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/sdk-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/login_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/login-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/login_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/login-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/rest_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/rest-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/rest_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/rest-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/web_socket.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/web-socket.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/web_socket.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/api/web-socket.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/commons/real-time_log_push.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/commons/real-time-log-push.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/commons/real-time_log_push.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/commons/real-time-log-push.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/overview.md
index 934bf307f6..d551d82135 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/overview.md
@@ -35,7 +35,7 @@ sidebar_position: 0
**支持的脚本语言有**：SparkSQL、Spark Scala、Pyspark、R、Python、HQL和Shell等；
- 更多关于统一作业执行服务的信息，请查看[UJES架构设计文档](ujes/ujes_design.md)
+ 更多关于统一作业执行服务的信息，请查看[UJES架构设计文档](ujes/ujes-design.md)
- **资源管理服务**： 支持实时管控每个系统和用户的资源使用情况，限制系统和用户的资源使用量和并发数，并提供实时的资源动态图表，方便查看和管理系统和用户的资源；
@@ -134,4 +134,4 @@ sidebar_position: 0
12. 一旦SQL执行成功，Engine主动将结果集推给Entrance，Entrance通知前端拿取结果。
-关于Entrance/EngineManager/Engine异常情况下的设计方案，请查看[UJES架构设计文档](ujes/ujes_design.md)
\ No newline at end of file
+关于Entrance/EngineManager/Engine异常情况下的设计方案，请查看[UJES架构设计文档](ujes/ujes-design.md)
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/file_system.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/file-system.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/file_system.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/file-system.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/remote_file_system_architecture_design.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/remote-file-system-architecture-design.md
similarity index 97%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/remote_file_system_architecture_design.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/remote-file-system-architecture-design.md
index dd1936a134..1aedbdf1d4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/remote_file_system_architecture_design.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/remote-file-system-architecture-design.md
@@ -19,7 +19,7 @@ sidebar_position: 1
## 2 思路
-通过在远程服务器上，启动该文件系统的引擎管理器(IO-EngineManager)([什么是EngineManager?](/architecture/ujes/ujes_design.md))，并提供兼容统一的客户端API，让用户访问到远程的文件系统。
+通过在远程服务器上，启动该文件系统的引擎管理器(IO-EngineManager)([什么是EngineManager?](/architecture/ujes/ujes-design.md))，并提供兼容统一的客户端API，让用户访问到远程的文件系统。
整个架构如下图所示：
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/resultset_file.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/resultset-file.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/resultset_file.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/storage/resultset-file.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/asynchronous_thread_pool.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/asynchronous-thread-pool.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/asynchronous_thread_pool.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/asynchronous-thread-pool.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/file_import_and_export_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/file-import-and-export-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/file_import_and_export_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/file-import-and-export-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/ujes_design.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/ujes-design.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/ujes_design.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/ujes-design.md
index cdf79d35fc..9068156ec9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/ujes_design.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/architecture/ujes/ujes-design.md
@@ -219,6 +219,6 @@ UJES的Entrance、EngineManager和Engine都是通过Linkis PRC进行通信。
### 5.1 传统部署方式
-请查看[快速部署文档](deployment/quick_deploy.md)。
+请查看[快速部署文档](deployment/quick-deploy.md)。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/engine_conn_plugin_installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/engine_conn_plugin_installation.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/engine-conn-plugin-installation.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/production_deployment _guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/production-deployment -guide.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/production_deployment _guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/production-deployment -guide.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/quick_deploy.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/quick-deploy.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/quick_deploy.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/quick-deploy.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/quick_start.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/quick-start.md
similarity index 92%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/quick_start.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/quick-start.md
index 9932b2dd5d..65da2fb1c7 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/quick_start.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/quick-start.md
@@ -27,4 +27,4 @@ sidebar_position: 2
## 3 快速使用Linkis
- 请参考[快速使用Linkis](quick_deploy#5-快速使用linkis)
\ No newline at end of file
+ 请参考[快速使用Linkis](quick-deploy#5-快速使用linkis)
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/sourcecode_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/sourcecode_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/deployment/sourcecode-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/development/compile_and_package.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/development/compile-and-package.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/development/compile_and_package.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/development/compile-and-package.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/development/new_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/development/new-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/development/new_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/development/new-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/engine_usage/python.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/engine_usage/python.md
index 089e14bc56..b8355e61ed 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/engine_usage/python.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/engine_usage/python.md
@@ -71,7 +71,7 @@ python.script=${真实的python解析器路径,如/usr/bin/python}
## 2 Python引擎的实现方式
- Linkis-Python执行引擎的实现，是参照[如何实现一个新引擎](/development/new_engine_conn.md)实现了Entrance、EngineManager和Engine三个模块的必要接口。
+ Linkis-Python执行引擎的实现，是参照[如何实现一个新引擎](/development/new-engine-conn.md)实现了Entrance、EngineManager和Engine三个模块的必要接口。
其中执行模块的实现是采用了py4j框架，让python执行器与JVM进行交互，当用户提交代码之后，JVM通过py4j框架将代码提交到python解释器进行执行，并从python进程中得到输出的结果或者错误信息。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/engine_usage/spark.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/engine_usage/spark.md
index 8b25e8eaf9..451884cf49 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/engine_usage/spark.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/engine_usage/spark.md
@@ -84,7 +84,7 @@ Scriptis页面为我们提供了可以设置启动参数的配置页面，其中
## 2 Spark引擎的实现方式
- Linkis-Python执行引擎的实现，是参照[如何实现一个新引擎](/development/new_engine_conn.md)实现了Entrance、EngineManager和Engine三个模块的必要接口。
+ Linkis-Python执行引擎的实现，是参照[如何实现一个新引擎](/development/new-engine-conn.md)实现了Entrance、EngineManager和Engine三个模块的必要接口。
在EngineManager模块，我们选择采用spark-submit这命令来进行启动java进程，所以Linkis采取了重写ProcessEngineBuilder的build方法，将用户配置的spark的启动参数与spark-submit命令进行整合,构成一个启动spark引擎的命令，然后执行该命令。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/upgrade/upgrade_from_0.9.0_to_0.9.1_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/upgrade/upgrade-from-0.9.0-to-0.9.1-guide.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/upgrade/upgrade_from_0.9.0_to_0.9.1_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/upgrade/upgrade-from-0.9.0-to-0.9.1-guide.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/user_guide/0.X_sdk_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/user_guide/0.X-sdk-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/user_guide/0.X_sdk_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/user_guide/0.X-sdk-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/user_guide/1.0_sdk_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/user_guide/1.0-sdk-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/user_guide/1.0_sdk_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-0.11.0/user_guide/1.0-sdk-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/jdbc_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/jdbc-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/jdbc_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/jdbc-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/linkis_task_operator.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/linkis-task-operator.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/linkis_task_operator.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/linkis-task-operator.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/login_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/login-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/login_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/login-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/overview.md
index 987616848e..a4d0d3889a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 1
## 1. 文档说明
Linkis1.0 在Linkix0.x版本的基础上进行了重构优化，同时也兼容了0.x的接口，但是为了防止在使用1.0版本时存在兼容性问题，需要您仔细阅读以下文档：
-1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login_api.md)。
+1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login-api.md)。
-2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc_api.md)。
+2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc-api.md)。
-3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis_task_operator.md)。
\ No newline at end of file
+3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis-task-operator.md)。
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/add_an_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/add-an-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/add_an_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/add-an-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/commons/message_scheduler.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/commons/message-scheduler.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/commons/message_scheduler.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/commons/message-scheduler.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn_plugin.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/app_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/label_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/resource_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/overview.md
index d6bc4d0ad5..fdf186849e 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/computation_governance_services/overview.md
@@ -66,10 +66,10 @@ Linkis1.0将优化Job的整体执行流程，从提交 —\> 准备 —\>
EngineConnManager (简称ECM)是 Linkis0.X EngineManager 的精简升级版。Linkis1.0下的ECM去除了引擎的申请能力，整个微服务完全无状态，将聚焦于支持各类 EngineConn 的启动和销毁。
- [进入EngineConnManager架构设计](engine/engine_conn_manager.md)
+ [进入EngineConnManager架构设计](engine/engine-conn-manager.md)
### 5、EngineConn
EngineConn 是 Linkis0.X Engine 的优化升级版本，将提供 EngineConn 和 Executor 两大模块，其中 EngineConn 用于连接底层的计算存储引擎，提供一个打通了底层各计算存储引擎的 Session 会话；Executor 则基于这个 Session 会话，提供交互式计算、流式计算、离线计算、数据存储的全栈计算能力支持。
-[进入EngineConn架构设计](engine/engine_conn.md)
+[进入EngineConn架构设计](engine/engine-conn.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/difference_between_1.0_and_0.x.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/difference_between_1.0_and_0.x.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/difference-between-1.0-and-0.x.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/job_submission_preparation_and_execution_process.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/job_submission_preparation_and_execution_process.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/job-submission-preparation-and-execution-process.md
index d0a8dcfc82..88fa0409a1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/job_submission_preparation_and_execution_process.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/job-submission-preparation-and-execution-process.md
@@ -38,7 +38,7 @@ sidebar_position: 1
1. 首先，Client（如前端或客户端）发起Job请求，Job请求信息精简如下
-（关于Linkis的具体使用方式，请参考 [如何使用Linkis](user_guide/how_to_use.md)）：
+（关于Linkis的具体使用方式，请参考 [如何使用Linkis](../user_guide/how-to-use.md)）：
```
POST /api/rest_j/v1/entrance/submit
@@ -74,7 +74,7 @@ POST /api/rest_j/v1/entrance/submit
如何定义可复用EngineConn？指能匹配计算任务的所有标签要求的，且EngineConn本身健康状态为Healthy（负载低且实际EngineConn状态为Idle）的，然后再按规则对所有满足条件的EngineConn进行排序选择，最终锁定一个最佳的EngineConn。
-如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](add_an_engine_conn.md) 。
+如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](add-an-engine-conn.md) 。
#### 2.2 计算任务编排
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/overview.md
index 7287a40857..3e7f4994fe 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/overview.md
@@ -18,7 +18,7 @@ Linkis 1.0 将所有微服务总体划分为三大类：公共增强服务、计
以下是 Linkis1.0 架构文档的目录列表：
-1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference_between_1.0_and_0.x)。
+1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference-between-1.0-and-0.x)。
2. Linkis1.0公共增强服务相关文档，请阅读[公共增强服务](public_enhancement_services/overview.md)。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_cache.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_client.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_client.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_listener.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_persistence.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_search.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_search.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/overview.md
index 2992203775..68591cc538 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/context_service/overview.md
@@ -101,29 +101,29 @@ CS，用于解决一个数据应用开发流程，跨多个系统间的数据和
### 1. Client
外部访问CS的入口，Client模块提供HA功能；
-[进入Client架构设计](context_service_client.md)
+[进入Client架构设计](context-service-client.md)
### 2. Service模块
提供Restful接口，封装和处理客户端提交的CS请求；
-[进入Service架构设计](context_service.md)
+[进入Service架构设计](context-service.md)
### 3. ContextSearch
上下文查询模块，提供丰富和强大的查询能力，供客户端查找上下文的Key-Value键值对；
-[进入ContextSearch架构设计](context_service_search.md)
+[进入ContextSearch架构设计](context-service-search.md)
### 4. Listener
CS的监听器模块，提供同步和异步的事件消费能力，具备类似Zookeeper的Key-Value一旦更新，实时通知Client的能力；
-[进入Listener架构设计](context_service_listener.md)
+[进入Listener架构设计](context-service-listener.md)
### 5. ContextCache
上下文的内存缓存模块，提供快速检索上下文的能力和对JVM内存使用的监听和清理能力；
-[进入ContextCache架构设计](context_service_cache.md)
+[进入ContextCache架构设计](context-service-cache.md)
### 6. HighAvailable
提供CS高可用能力；
-[进入HighAvailable架构设计](context_service_highavailable.md)
+[进入HighAvailable架构设计](context-service-highavailable.md)
### 7. Persistence
CS的持久化功能；
-[进入Persistence架构设计](context_service_persistence.md)
+[进入Persistence架构设计](context-service-persistence.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/public_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/public_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/public_enhancement_services/public-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/cluster_deployment.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/cluster-deployment.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/cluster_deployment.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/cluster-deployment.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/engine_conn_plugin_installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/engine_conn_plugin_installation.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/engine-conn-plugin-installation.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/installation_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/installation_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/installation-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/quick_deploy.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/quick-deploy.md
similarity index 96%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/quick_deploy.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/quick-deploy.md
index 10054a2e1b..694097e12a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/quick_deploy.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/quick-deploy.md
@@ -4,9 +4,9 @@ sidebar_position: 1
---
## 注意事项
- **如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference_between_1.0_and_0.x.md)**。
+ **如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference-between-1.0-and-0.x.md)**。
- 请注意：除了 Linkis1.0 安装包默认已经包含的：Python/Shell/Hive/Spark四个EngineConnPlugin以外，如果大家有需要，可以手动安装如 JDBC 引擎等类型的其他引擎，具体请参考 [EngineConnPlugin引擎插件安装文档](../deployment/engine_conn_plugin_installation)。
+ 请注意：除了 Linkis1.0 安装包默认已经包含的：Python/Shell/Hive/Spark四个EngineConnPlugin以外，如果大家有需要，可以手动安装如 JDBC 引擎等类型的其他引擎，具体请参考 [EngineConnPlugin引擎插件安装文档](../deployment/engine-conn-plugin-installation)。
**Linkis Docker镜像**
[Linkis 0.10.0 Docker](https://hub.docker.com/repository/docker/wedatasphere/linkis)
@@ -217,11 +217,11 @@ Linkis1.0 默认已适配的引擎列表如下：
**第一次安装**必须选是。
- **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade_from_0.X_to_1.0_guide.md)**。
+ **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade-from-0.X-to-1.0-guide.md)**。
- **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade_from_0.X_to_1.0_guide.md)**。
+ **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade-from-0.X-to-1.0-guide.md)**。
- **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade_from_0.X_to_1.0_guide.md)**。
+ **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade-from-0.X-to-1.0-guide.md)**。
### 3. 是否安装成功：
@@ -256,5 +256,5 @@ Linkis1.0 默认已适配的引擎列表如下：
#### (3)、查看服务是否正常
-1. 服务启动成功后您可以通过，安装前端管理台，来检验服务的正常性，[点击跳转管理台安装文档](web_install.md)
-2. 您也可以通过Linkis用户手册来测试Linis是否能正常运行任务，[点击跳转用户手册](user_guide/overview.md)
+1. 服务启动成功后您可以通过，安装前端管理台，来检验服务的正常性，[点击跳转管理台安装文档](web-install.md)
+2. 您也可以通过Linkis用户手册来测试Linis是否能正常运行任务，[点击跳转用户手册](../user_guide/overview.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/sourcecode_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/sourcecode_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/sourcecode-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/web_install.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/web-install.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/web_install.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/web-install.md
index a07dcbae20..5b9bb0a911 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/web_install.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/deployment/web-install.md
@@ -3,7 +3,7 @@ title: 前端管理台部署
sidebar_position: 6
---
-Linkis在1.0提供了单独的前端管理台功能，提供了展示Linis的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick_deploy.md)
+Linkis在1.0提供了单独的前端管理台功能，提供了展示Linis的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick-deploy.md)
## 1、准备工作
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/linkis_compile_and_package.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/linkis-compile-and-package.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/linkis_compile_and_package.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/linkis-compile-and-package.md
index f42a7c107b..6852d846b7 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/linkis_compile_and_package.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/linkis-compile-and-package.md
@@ -94,7 +94,7 @@ __编译环境要求：__ 必须 **JDK8** 以上，**Oracle/Sun** 和 **OpenJDK
wedatasphere-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/linkis-engineplugin-spark-x.x.x.jar
```
-如何单独安装 Spark 引擎？ 请参考 [Linkis 引擎插件安装文档](../deployment/engine_conn_plugin_installation)
+如何单独安装 Spark 引擎？ 请参考 [Linkis 引擎插件安装文档](../deployment/engine-conn-plugin-installation)
## 5. 如何修改Linkis的依赖的Hadoop、Hive、Spark版本
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/linkis_debug.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/linkis-debug.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/linkis_debug.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/linkis-debug.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/new_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/new-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/new_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/new-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/web_build.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/web-build.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/web_build.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/development/web-build.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/hive.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/hive.md
index 0303af0383..d51ef395bb 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/hive.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/hive.md
@@ -35,13 +35,13 @@ on Tez，需要您按照此pr进行一下修改。
如果您已经编译完了您的hive引擎的插件已经编译完成，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 hive引擎的标签
Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.hive引擎的使用
@@ -57,7 +57,7 @@ hive的MapReduce任务是需要用到yarn的资源，所以需要您在一开始
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Hive任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -73,7 +73,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType hive-2.3.3 -codeType hql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/jdbc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/jdbc.md
index 010ef2ca24..1b1c1c2913 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/jdbc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/jdbc.md
@@ -42,7 +42,7 @@ wds.linkis.jdbc.password
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于JDBC任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -58,7 +58,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/python.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/python.md
index b72b7ce9d0..58678ea243 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/python.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/python.md
@@ -38,7 +38,7 @@ python3的，您可以简单更改配置就可以完成Python版本的切换，
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Python任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -54,7 +54,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/shell.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/shell.md
index 84bdc26630..98412d292f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/shell.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/shell.md
@@ -37,7 +37,7 @@ Shell引擎不需要用户自行编译，直接使用编译好的shell引擎插
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Shell任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -53,7 +53,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/spark.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/spark.md
index e9d183551c..d16dbacca8 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/spark.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/engine_usage/spark.md
@@ -33,13 +33,13 @@ sidebar_position: 1
如果您已经编译完了您的spark引擎的插件已经编译完成，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 spark引擎的标签
Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.spark引擎的使用
@@ -54,7 +54,7 @@ Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Spark任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -74,7 +74,7 @@ sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -
# 可以在提交参数通过-confMap wds.linkis.yarnqueue=dws 来指定yarn 队列
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -confMap wds.linkis.yarnqueue=dws -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/introduction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/introduction.md
index a9eb69b006..80a1593afb 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/introduction.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/introduction.md
@@ -42,8 +42,8 @@ Linkis 自2019年开源发布以来，已累计积累了700多家试验企业和
请前往[Linkis releases 页面](https://github.com/apache/incubator-linkis/releases) 下载Linkis 已编译的部署安装包或源码包。
## 编译和安装部署
-请参照[编译指引](development/linkis_compile_and_package.md) 来编译Linkis 源码。
-请参考[安装部署文档](deployment/quick_deploy.md) 来部署Linkis。
+请参照[编译指引](development/linkis-compile-and-package.md) 来编译Linkis 源码。
+请参考[安装部署文档](deployment/quick-deploy.md) 来部署Linkis。
## 示例和使用指引
请到[用户手册](user_guide/overview.md), [各引擎使用指引](engine_usage/overview.md) 和[API 文档](api/overview.md) 中，查看如何使用和管理Linkis 的示例和指引。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/tuning_and_troubleshooting/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/tuning_and_troubleshooting/overview.md
index 337501e74f..3c575cfb57 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/tuning_and_troubleshooting/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/tuning_and_troubleshooting/overview.md
@@ -111,6 +111,6 @@ sidebar_position: 0
### 六、定位源码远程debug
-通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode_hierarchical_structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis_debug.md) 》一文调试对应微服务下的代码。
+通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode-hierarchical-structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis-debug.md) 》一文调试对应微服务下的代码。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/upgrade/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/upgrade/overview.md
index 6b78e03140..beaa8f7fc4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/upgrade/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/upgrade/overview.md
@@ -6,4 +6,4 @@ Linkis1.0 与 Linkis0.X的架构差异巨大，且安装部署包和数据库表
1. 如果您是第一次安装使用 Linkis，或重装 Linkis，您无需关注 Linkis 升级指南。
-2. 如果您是从Linkis0.X 升级到 Linkis1.0，请一定要仔细阅读 [Linkis从0.X升级到1.0指南](upgrade_from_0.X_to_1.0_guide)
\ No newline at end of file
+2. 如果您是从Linkis0.X 升级到 Linkis1.0，请一定要仔细阅读 [Linkis从0.X升级到1.0指南](upgrade-from-0.X-to-1.0-guide)
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/upgrade/upgrade_from_0.X_to_1.0_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 95%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
index a9f0be74ca..880fcd1782 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 1
## 1. 注意事项
- **如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference_between_1.0_and_0.x.md)**。
+ **如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference-between-1.0-and-0.x.md)**。
## 2. 服务升级安装
@@ -15,7 +15,7 @@ sidebar_position: 1
在安装时如果需要保留0.X的数据，一定要选择1跳过建表语句（见下面代码）。
- Linkis1.0 的安装可以参考[如何快速安装使用Linkis-1.0](deployment/quick_deploy.md)
+ Linkis1.0 的安装可以参考[如何快速安装使用Linkis-1.0](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ Please input the choice: ## choice 1
## 4. 安装Linkis1.0
- 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装使用Linkis-1.0](deployment/quick_deploy.md)
+ 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装使用Linkis-1.0](deployment/quick-deploy.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/console_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/console-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/console_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/console-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/how_to_use.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how-to-use.md
similarity index 94%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/how_to_use.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how-to-use.md
index bc3e1af344..9627ebc2b5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/how_to_use.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how-to-use.md
@@ -7,9 +7,9 @@ sidebar_position: 1
## 1. Client端使用
如果需要在Linkis的基础上，接入其它应用，需要针对Linkis提供的接口进行开发，Linkis提供了多种客户端接入接口，更详细的使用介绍可以参考以下内容：
-- [**Restful API使用方式**](api/linkis_task_operator.md)
-- [**JDBC API使用方式**](api/jdbc_api.md)
-- [**Java SDK使用方式**](user_guide/sdk_manual.md)
+- [**Restful API使用方式**](api/linkis-task-operator.md)
+- [**JDBC API使用方式**](api/jdbc-api.md)
+- [**Java SDK使用方式**](../user_guide/sdk-manual.md)
## 2. Scriptis使用Linkis
如果需要使用Linkis完成交互式在线分析处理的工作，并且不需要诸如工作流开发、工作流调度、数据服务等数据分析应用工具，可以单独安装[**Scriptis**](https://github.com/WeBankFinTech/Scriptis)，详细安装教程可参考其对应的安装部署文档。
### 2.1. 使用Scriptis执行脚本
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/linkiscli_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/linkiscli-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/linkiscli_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/linkiscli-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/overview.md
index c1f4a720e6..270a4ca227 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis在设计之初就考虑接入方式的拓展性问题，针对不同的接入场景，Linkis提供了前端接入和SDK接入的方式，在前端接口上又提供了HTTP和WebSocket两种方式，如果对接入并使用Linkis感兴趣，可以参考以下文档：
-- [如何使用Links](how_to_use.md)
-- [Linkis-Cli使用文档](linkiscli_manual.md)
-- [Linkis JAVA SDK 方式使用](sdk_manual.md)
-- [Linkis管理台的使用](console_manual.md)
+- [如何使用Links](how-to-use.md)
+- [Linkis-Cli使用文档](linkiscli-manual.md)
+- [Linkis JAVA SDK 方式使用](sdk-manual.md)
+- [Linkis管理台的使用](console-manual.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/sdk_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/sdk-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/sdk_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/sdk-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/jdbc_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/jdbc-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/jdbc_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/jdbc-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/linkis_task_operator.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/linkis-task-operator.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/linkis_task_operator.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/linkis-task-operator.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/login_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/login-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/login_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/login-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/overview.md
index 987616848e..a4d0d3889a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 1
## 1. 文档说明
Linkis1.0 在Linkix0.x版本的基础上进行了重构优化，同时也兼容了0.x的接口，但是为了防止在使用1.0版本时存在兼容性问题，需要您仔细阅读以下文档：
-1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login_api.md)。
+1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login-api.md)。
-2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc_api.md)。
+2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc-api.md)。
-3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis_task_operator.md)。
\ No newline at end of file
+3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis-task-operator.md)。
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/add_an_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/add-an-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/add_an_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/add-an-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/commons/message_scheduler.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/commons/message-scheduler.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/commons/message_scheduler.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/commons/message-scheduler.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn_plugin.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/app_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/label_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/resource_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/overview.md
index 65ea36c02d..b77e15fd3a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/computation_governance_services/overview.md
@@ -66,10 +66,10 @@ Linkis1.0将优化Job的整体执行流程，从提交 —\> 准备 —\>
EngineConnManager (简称ECM)是 Linkis0.X EngineManager 的精简升级版。Linkis1.0下的ECM去除了引擎的申请能力，整个微服务完全无状态，将聚焦于支持各类 EngineConn 的启动和销毁。
- [进入EngineConnManager架构设计](engine/engine_conn_manager.md)
+ [进入EngineConnManager架构设计](engine/engine-conn-manager.md)
### 5、EngineConn
EngineConn 是 Linkis0.X Engine 的优化升级版本，将提供 EngineConn 和 Executor 两大模块，其中 EngineConn 用于连接底层的计算存储引擎，提供一个打通了底层各计算存储引擎的 Session 会话；Executor 则基于这个 Session 会话，提供交互式计算、流式计算、离线计算、数据存储的全栈计算能力支持。
-[进入EngineConn架构设计](engine/engine_conn.md)
+[进入EngineConn架构设计](engine/engine-conn.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/difference_between_1.0_and_0.x.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/difference_between_1.0_and_0.x.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/difference-between-1.0-and-0.x.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/job_submission_preparation_and_execution_process.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/job_submission_preparation_and_execution_process.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/job-submission-preparation-and-execution-process.md
index d0a8dcfc82..88fa0409a1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/job_submission_preparation_and_execution_process.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/job-submission-preparation-and-execution-process.md
@@ -38,7 +38,7 @@ sidebar_position: 1
1. 首先，Client（如前端或客户端）发起Job请求，Job请求信息精简如下
-（关于Linkis的具体使用方式，请参考 [如何使用Linkis](user_guide/how_to_use.md)）：
+（关于Linkis的具体使用方式，请参考 [如何使用Linkis](../user_guide/how-to-use.md)）：
```
POST /api/rest_j/v1/entrance/submit
@@ -74,7 +74,7 @@ POST /api/rest_j/v1/entrance/submit
如何定义可复用EngineConn？指能匹配计算任务的所有标签要求的，且EngineConn本身健康状态为Healthy（负载低且实际EngineConn状态为Idle）的，然后再按规则对所有满足条件的EngineConn进行排序选择，最终锁定一个最佳的EngineConn。
-如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](add_an_engine_conn.md) 。
+如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](add-an-engine-conn.md) 。
#### 2.2 计算任务编排
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/overview.md
index 14d736ea87..c334ceedad 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/overview.md
@@ -18,7 +18,7 @@ Linkis 1.0 将所有微服务总体划分为三大类：公共增强服务、计
以下是 Linkis1.0 架构文档的目录列表：
-1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference_between_1.0_and_0.x)。
+1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference-between-1.0-and-0.x)。
2. Linkis1.0公共增强服务相关文档，请阅读[公共增强服务](public_enhancement_services/overview.md)。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_cache.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_client.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_client.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_listener.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_persistence.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_search.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_search.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/overview.md
index 2992203775..68591cc538 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/context_service/overview.md
@@ -101,29 +101,29 @@ CS，用于解决一个数据应用开发流程，跨多个系统间的数据和
### 1. Client
外部访问CS的入口，Client模块提供HA功能；
-[进入Client架构设计](context_service_client.md)
+[进入Client架构设计](context-service-client.md)
### 2. Service模块
提供Restful接口，封装和处理客户端提交的CS请求；
-[进入Service架构设计](context_service.md)
+[进入Service架构设计](context-service.md)
### 3. ContextSearch
上下文查询模块，提供丰富和强大的查询能力，供客户端查找上下文的Key-Value键值对；
-[进入ContextSearch架构设计](context_service_search.md)
+[进入ContextSearch架构设计](context-service-search.md)
### 4. Listener
CS的监听器模块，提供同步和异步的事件消费能力，具备类似Zookeeper的Key-Value一旦更新，实时通知Client的能力；
-[进入Listener架构设计](context_service_listener.md)
+[进入Listener架构设计](context-service-listener.md)
### 5. ContextCache
上下文的内存缓存模块，提供快速检索上下文的能力和对JVM内存使用的监听和清理能力；
-[进入ContextCache架构设计](context_service_cache.md)
+[进入ContextCache架构设计](context-service-cache.md)
### 6. HighAvailable
提供CS高可用能力；
-[进入HighAvailable架构设计](context_service_highavailable.md)
+[进入HighAvailable架构设计](context-service-highavailable.md)
### 7. Persistence
CS的持久化功能；
-[进入Persistence架构设计](context_service_persistence.md)
+[进入Persistence架构设计](context-service-persistence.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/public_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/public_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/architecture/public_enhancement_services/public-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/cluster_deployment.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/cluster-deployment.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/cluster_deployment.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/cluster-deployment.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/engine_conn_plugin_installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/engine_conn_plugin_installation.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/engine-conn-plugin-installation.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/installation_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/installation_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/installation-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/quick_deploy.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/quick-deploy.md
similarity index 95%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/quick_deploy.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/quick-deploy.md
index b1c38858f6..0ca4365b70 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/quick_deploy.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/quick-deploy.md
@@ -14,9 +14,9 @@ sidebar_position: 1
</font>
-**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference_between_1.0_and_0.x.md)**。
+**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference-between-1.0-and-0.x.md)**。
-请注意：除了 Linkis1.0 安装包默认已经包含的：Python/Shell/Hive/Spark四个EngineConnPlugin以外，如果大家有需要，可以手动安装如 JDBC 引擎等类型的其他引擎，具体请参考 [EngineConnPlugin引擎插件安装文档](../deployment/engine_conn_plugin_installation)。
+请注意：除了 Linkis1.0 安装包默认已经包含的：Python/Shell/Hive/Spark四个EngineConnPlugin以外，如果大家有需要，可以手动安装如 JDBC 引擎等类型的其他引擎，具体请参考 [EngineConnPlugin引擎插件安装文档](../deployment/engine-conn-plugin-installation)。
Linkis1.0.3 默认已适配的引擎列表如下：
@@ -208,11 +208,11 @@ Linkis1.0.3 默认已适配的引擎列表如下：
**第一次安装**必须选是。
- **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade_from_0.X_to_1.0_guide.md)**。
+ **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade-from-0.X-to-1.0-guide.md)**。
- **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade_from_0.X_to_1.0_guide.md)**。
+ **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade-from-0.X-to-1.0-guide.md)**。
- **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade_from_0.X_to_1.0_guide.md)**。
+ **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade-from-0.X-to-1.0-guide.md)**。
### 4.3 是否安装成功：
@@ -262,5 +262,5 @@ cp mysql-connector-java-5.1.49.jar {LINKIS_HOME}/lib/linkis-commons/public-modu
#### (3)、查看服务是否正常
-1. 服务启动成功后您可以通过，安装前端管理台，来检验服务的正常性，[点击跳转管理台安装文档](web_install.md)
-2. 您也可以通过Linkis用户手册来测试Linis是否能正常运行任务，[点击跳转用户手册](user_guide/overview.md)
+1. 服务启动成功后您可以通过，安装前端管理台，来检验服务的正常性，[点击跳转管理台安装文档](web-install.md)
+2. 您也可以通过Linkis用户手册来测试Linis是否能正常运行任务，[点击跳转用户手册](../user_guide/overview.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/sourcecode_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/sourcecode_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/sourcecode-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/web_install.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/web-install.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/web_install.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/web-install.md
index f883306786..bd07ba1ca1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/web_install.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/deployment/web-install.md
@@ -3,7 +3,7 @@ title: 前端管理台部署
sidebar_position: 6
---
-Linkis在1.0提供了单独的前端管理台功能，提供了展示Linis的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick_deploy.md)
+Linkis在1.0提供了单独的前端管理台功能，提供了展示Linis的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick-deploy.md)
## 1、准备工作
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis_compile_and_package.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis-compile-and-package.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis_compile_and_package.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis-compile-and-package.md
index 3c8d801b06..257f81407c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis_compile_and_package.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis-compile-and-package.md
@@ -107,7 +107,7 @@ __编译环境要求：__ 必须 **JDK8** 以上，**Oracle/Sun** 和 **OpenJDK
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/linkis-engineplugin-spark-x.x.x.jar
```
-如何单独安装 Spark 引擎？请参考 [Linkis 引擎插件安装文档](../deployment/engine_conn_plugin_installation)
+如何单独安装 Spark 引擎？请参考 [Linkis 引擎插件安装文档](../deployment/engine-conn-plugin-installation)
## 5. 如何修改Linkis的依赖的Hadoop、Hive、Spark版本
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis_debug.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis-debug.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis_debug.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/linkis-debug.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/new_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/new-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/new_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/new-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/web_build.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/web-build.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/web_build.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/development/web-build.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/flink.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/flink.md
index 71ae433cd2..2987dd4686 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/flink.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/flink.md
@@ -64,7 +64,7 @@ https://github.com/WeBankFinTech/Linkis/wiki/EngineConnPlugin%E5%BC%95%E6%93%8E%
Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3.Flink引擎的使用
@@ -118,7 +118,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
sh ./bin/linkis-cli -engineType flink-1.12.2 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 OnceEngineConn方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/hive.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/hive.md
index 0303af0383..d51ef395bb 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/hive.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/hive.md
@@ -35,13 +35,13 @@ on Tez，需要您按照此pr进行一下修改。
如果您已经编译完了您的hive引擎的插件已经编译完成，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 hive引擎的标签
Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.hive引擎的使用
@@ -57,7 +57,7 @@ hive的MapReduce任务是需要用到yarn的资源，所以需要您在一开始
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Hive任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -73,7 +73,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType hive-2.3.3 -codeType hql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/jdbc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/jdbc.md
index 010ef2ca24..1b1c1c2913 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/jdbc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/jdbc.md
@@ -42,7 +42,7 @@ wds.linkis.jdbc.password
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于JDBC任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -58,7 +58,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/python.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/python.md
index b72b7ce9d0..58678ea243 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/python.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/python.md
@@ -38,7 +38,7 @@ python3的，您可以简单更改配置就可以完成Python版本的切换，
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Python任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -54,7 +54,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/shell.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/shell.md
index 84bdc26630..98412d292f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/shell.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/shell.md
@@ -37,7 +37,7 @@ Shell引擎不需要用户自行编译，直接使用编译好的shell引擎插
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Shell任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -53,7 +53,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/spark.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/spark.md
index e9d183551c..d16dbacca8 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/spark.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/engine_usage/spark.md
@@ -33,13 +33,13 @@ sidebar_position: 1
如果您已经编译完了您的spark引擎的插件已经编译完成，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 spark引擎的标签
Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.spark引擎的使用
@@ -54,7 +54,7 @@ Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Spark任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -74,7 +74,7 @@ sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -
# 可以在提交参数通过-confMap wds.linkis.yarnqueue=dws 来指定yarn 队列
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -confMap wds.linkis.yarnqueue=dws -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/introduction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/introduction.md
index d3bceb80d3..15927d0630 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/introduction.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/introduction.md
@@ -42,8 +42,8 @@ Linkis 自2019年开源发布以来，已累计积累了700多家试验企业和
请前往[Linkis releases 页面](https://github.com/apache/incubator-linkis/releases) 下载Linkis 已编译的部署安装包或源码包。
## 编译和安装部署
-请参照[编译指引](development/linkis_compile_and_package.md) 来编译Linkis 源码。
-请参考[安装部署文档](deployment/quick_deploy.md) 来部署Linkis。
+请参照[编译指引](development/linkis-compile-and-package.md) 来编译Linkis 源码。
+请参考[安装部署文档](deployment/quick-deploy.md) 来部署Linkis。
## 示例和使用指引
请到[用户手册](user_guide/overview.md), [各引擎使用指引](engine_usage/overview.md) 和[API 文档](api/overview.md) 中，查看如何使用和管理Linkis 的示例和指引。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/tuning_and_troubleshooting/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/tuning_and_troubleshooting/overview.md
index 337501e74f..3c575cfb57 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/tuning_and_troubleshooting/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/tuning_and_troubleshooting/overview.md
@@ -111,6 +111,6 @@ sidebar_position: 0
### 六、定位源码远程debug
-通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode_hierarchical_structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis_debug.md) 》一文调试对应微服务下的代码。
+通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode-hierarchical-structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis-debug.md) 》一文调试对应微服务下的代码。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/upgrade/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/upgrade/overview.md
index 6b78e03140..beaa8f7fc4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/upgrade/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/upgrade/overview.md
@@ -6,4 +6,4 @@ Linkis1.0 与 Linkis0.X的架构差异巨大，且安装部署包和数据库表
1. 如果您是第一次安装使用 Linkis，或重装 Linkis，您无需关注 Linkis 升级指南。
-2. 如果您是从Linkis0.X 升级到 Linkis1.0，请一定要仔细阅读 [Linkis从0.X升级到1.0指南](upgrade_from_0.X_to_1.0_guide)
\ No newline at end of file
+2. 如果您是从Linkis0.X 升级到 Linkis1.0，请一定要仔细阅读 [Linkis从0.X升级到1.0指南](upgrade-from-0.X-to-1.0-guide)
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/upgrade/upgrade_from_0.X_to_1.0_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 95%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/upgrade/upgrade-from-0.X-to-1.0-guide.md
index a9f0be74ca..880fcd1782 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 1
## 1. 注意事项
- **如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference_between_1.0_and_0.x.md)**。
+ **如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference-between-1.0-and-0.x.md)**。
## 2. 服务升级安装
@@ -15,7 +15,7 @@ sidebar_position: 1
在安装时如果需要保留0.X的数据，一定要选择1跳过建表语句（见下面代码）。
- Linkis1.0 的安装可以参考[如何快速安装使用Linkis-1.0](deployment/quick_deploy.md)
+ Linkis1.0 的安装可以参考[如何快速安装使用Linkis-1.0](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ Please input the choice: ## choice 1
## 4. 安装Linkis1.0
- 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装使用Linkis-1.0](deployment/quick_deploy.md)
+ 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装使用Linkis-1.0](deployment/quick-deploy.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/console_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/console-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/console_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/console-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/how_to_use.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/how-to-use.md
similarity index 94%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/how_to_use.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/how-to-use.md
index bc3e1af344..9627ebc2b5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/user_guide/how_to_use.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/how-to-use.md
@@ -7,9 +7,9 @@ sidebar_position: 1
## 1. Client端使用
如果需要在Linkis的基础上，接入其它应用，需要针对Linkis提供的接口进行开发，Linkis提供了多种客户端接入接口，更详细的使用介绍可以参考以下内容：
-- [**Restful API使用方式**](api/linkis_task_operator.md)
-- [**JDBC API使用方式**](api/jdbc_api.md)
-- [**Java SDK使用方式**](user_guide/sdk_manual.md)
+- [**Restful API使用方式**](api/linkis-task-operator.md)
+- [**JDBC API使用方式**](api/jdbc-api.md)
+- [**Java SDK使用方式**](../user_guide/sdk-manual.md)
## 2. Scriptis使用Linkis
如果需要使用Linkis完成交互式在线分析处理的工作，并且不需要诸如工作流开发、工作流调度、数据服务等数据分析应用工具，可以单独安装[**Scriptis**](https://github.com/WeBankFinTech/Scriptis)，详细安装教程可参考其对应的安装部署文档。
### 2.1. 使用Scriptis执行脚本
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/linkiscli_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/linkiscli-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/linkiscli_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/linkiscli-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/overview.md
index c1f4a720e6..270a4ca227 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis在设计之初就考虑接入方式的拓展性问题，针对不同的接入场景，Linkis提供了前端接入和SDK接入的方式，在前端接口上又提供了HTTP和WebSocket两种方式，如果对接入并使用Linkis感兴趣，可以参考以下文档：
-- [如何使用Links](how_to_use.md)
-- [Linkis-Cli使用文档](linkiscli_manual.md)
-- [Linkis JAVA SDK 方式使用](sdk_manual.md)
-- [Linkis管理台的使用](console_manual.md)
+- [如何使用Links](how-to-use.md)
+- [Linkis-Cli使用文档](linkiscli-manual.md)
+- [Linkis JAVA SDK 方式使用](sdk-manual.md)
+- [Linkis管理台的使用](console-manual.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/sdk_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/sdk-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/sdk_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/sdk-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/jdbc_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/jdbc-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/jdbc_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/jdbc-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/linkis_task_operator.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/linkis-task-operator.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/linkis_task_operator.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/linkis-task-operator.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/login_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/login-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/login_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/login-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/overview.md
index 987616848e..a4d0d3889a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 1
## 1. 文档说明
Linkis1.0 在Linkix0.x版本的基础上进行了重构优化，同时也兼容了0.x的接口，但是为了防止在使用1.0版本时存在兼容性问题，需要您仔细阅读以下文档：
-1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login_api.md)。
+1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login-api.md)。
-2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc_api.md)。
+2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc-api.md)。
-3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis_task_operator.md)。
\ No newline at end of file
+3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis-task-operator.md)。
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/add_an_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/add-an-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/add_an_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/add-an-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/commons/message_scheduler.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/commons/message-scheduler.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/commons/message_scheduler.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/commons/message-scheduler.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn_plugin.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/app_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/label_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/resource_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/overview.md
index 65ea36c02d..b77e15fd3a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/computation_governance_services/overview.md
@@ -66,10 +66,10 @@ Linkis1.0将优化Job的整体执行流程，从提交 —\> 准备 —\>
EngineConnManager (简称ECM)是 Linkis0.X EngineManager 的精简升级版。Linkis1.0下的ECM去除了引擎的申请能力，整个微服务完全无状态，将聚焦于支持各类 EngineConn 的启动和销毁。
- [进入EngineConnManager架构设计](engine/engine_conn_manager.md)
+ [进入EngineConnManager架构设计](engine/engine-conn-manager.md)
### 5、EngineConn
EngineConn 是 Linkis0.X Engine 的优化升级版本，将提供 EngineConn 和 Executor 两大模块，其中 EngineConn 用于连接底层的计算存储引擎，提供一个打通了底层各计算存储引擎的 Session 会话；Executor 则基于这个 Session 会话，提供交互式计算、流式计算、离线计算、数据存储的全栈计算能力支持。
-[进入EngineConn架构设计](engine/engine_conn.md)
+[进入EngineConn架构设计](engine/engine-conn.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/difference_between_1.0_and_0.x.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/difference_between_1.0_and_0.x.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/difference-between-1.0-and-0.x.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/job_submission_preparation_and_execution_process.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/job_submission_preparation_and_execution_process.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/job-submission-preparation-and-execution-process.md
index d0a8dcfc82..88fa0409a1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/architecture/job_submission_preparation_and_execution_process.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/job-submission-preparation-and-execution-process.md
@@ -38,7 +38,7 @@ sidebar_position: 1
1. 首先，Client（如前端或客户端）发起Job请求，Job请求信息精简如下
-（关于Linkis的具体使用方式，请参考 [如何使用Linkis](user_guide/how_to_use.md)）：
+（关于Linkis的具体使用方式，请参考 [如何使用Linkis](../user_guide/how-to-use.md)）：
```
POST /api/rest_j/v1/entrance/submit
@@ -74,7 +74,7 @@ POST /api/rest_j/v1/entrance/submit
如何定义可复用EngineConn？指能匹配计算任务的所有标签要求的，且EngineConn本身健康状态为Healthy（负载低且实际EngineConn状态为Idle）的，然后再按规则对所有满足条件的EngineConn进行排序选择，最终锁定一个最佳的EngineConn。
-如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](add_an_engine_conn.md) 。
+如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](add-an-engine-conn.md) 。
#### 2.2 计算任务编排
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/overview.md
index 28f24690a5..1fdb1b395d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/overview.md
@@ -18,7 +18,7 @@ Linkis 1.0 将所有微服务总体划分为三大类：公共增强服务、计
以下是 Linkis1.0 架构文档的目录列表：
-1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference_between_1.0_and_0.x)。
+1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference-between-1.0-and-0.x)。
2. Linkis1.0公共增强服务相关文档，请阅读[公共增强服务](public_enhancement_services/overview.md)。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/bml/engine_bml_dissect.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/bml/engine-bml-dissect.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/bml/engine_bml_dissect.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/bml/engine-bml-dissect.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_cache.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_client.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_client.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_listener.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_persistence.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_search.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_search.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/overview.md
index 2992203775..68591cc538 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/context_service/overview.md
@@ -101,29 +101,29 @@ CS，用于解决一个数据应用开发流程，跨多个系统间的数据和
### 1. Client
外部访问CS的入口，Client模块提供HA功能；
-[进入Client架构设计](context_service_client.md)
+[进入Client架构设计](context-service-client.md)
### 2. Service模块
提供Restful接口，封装和处理客户端提交的CS请求；
-[进入Service架构设计](context_service.md)
+[进入Service架构设计](context-service.md)
### 3. ContextSearch
上下文查询模块，提供丰富和强大的查询能力，供客户端查找上下文的Key-Value键值对；
-[进入ContextSearch架构设计](context_service_search.md)
+[进入ContextSearch架构设计](context-service-search.md)
### 4. Listener
CS的监听器模块，提供同步和异步的事件消费能力，具备类似Zookeeper的Key-Value一旦更新，实时通知Client的能力；
-[进入Listener架构设计](context_service_listener.md)
+[进入Listener架构设计](context-service-listener.md)
### 5. ContextCache
上下文的内存缓存模块，提供快速检索上下文的能力和对JVM内存使用的监听和清理能力；
-[进入ContextCache架构设计](context_service_cache.md)
+[进入ContextCache架构设计](context-service-cache.md)
### 6. HighAvailable
提供CS高可用能力；
-[进入HighAvailable架构设计](context_service_highavailable.md)
+[进入HighAvailable架构设计](context-service-highavailable.md)
### 7. Persistence
CS的持久化功能；
-[进入Persistence架构设计](context_service_persistence.md)
+[进入Persistence架构设计](context-service-persistence.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/datasource_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/datasource-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/datasource_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/datasource-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/metadata_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/metadata-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/metadata_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/metadata-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/public_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/public_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/architecture/public_enhancement_services/public-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/cluster_deployment.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/cluster-deployment.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/cluster_deployment.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/cluster-deployment.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/engine_conn_plugin_installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/engine_conn_plugin_installation.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/engine-conn-plugin-installation.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/installation_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/installation_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/installation-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/involve_skywalking_into_linkis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/involve-skywalking-into-linkis.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/involve_skywalking_into_linkis.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/involve-skywalking-into-linkis.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/quick_deploy.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/quick-deploy.md
similarity index 95%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/quick_deploy.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/quick-deploy.md
index b1c38858f6..0ca4365b70 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/quick_deploy.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/quick-deploy.md
@@ -14,9 +14,9 @@ sidebar_position: 1
</font>
-**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference_between_1.0_and_0.x.md)**。
+**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference-between-1.0-and-0.x.md)**。
-请注意：除了 Linkis1.0 安装包默认已经包含的：Python/Shell/Hive/Spark四个EngineConnPlugin以外，如果大家有需要，可以手动安装如 JDBC 引擎等类型的其他引擎，具体请参考 [EngineConnPlugin引擎插件安装文档](../deployment/engine_conn_plugin_installation)。
+请注意：除了 Linkis1.0 安装包默认已经包含的：Python/Shell/Hive/Spark四个EngineConnPlugin以外，如果大家有需要，可以手动安装如 JDBC 引擎等类型的其他引擎，具体请参考 [EngineConnPlugin引擎插件安装文档](../deployment/engine-conn-plugin-installation)。
Linkis1.0.3 默认已适配的引擎列表如下：
@@ -208,11 +208,11 @@ Linkis1.0.3 默认已适配的引擎列表如下：
**第一次安装**必须选是。
- **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade_from_0.X_to_1.0_guide.md)**。
+ **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade-from-0.X-to-1.0-guide.md)**。
- **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade_from_0.X_to_1.0_guide.md)**。
+ **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade-from-0.X-to-1.0-guide.md)**。
- **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade_from_0.X_to_1.0_guide.md)**。
+ **请注意：如果您是升级已有环境的 Linkis0.X 到 Linkis1.0，请不要直接选是，请先参考 [Linkis1.0升级指南](upgrade/upgrade-from-0.X-to-1.0-guide.md)**。
### 4.3 是否安装成功：
@@ -262,5 +262,5 @@ cp mysql-connector-java-5.1.49.jar {LINKIS_HOME}/lib/linkis-commons/public-modu
#### (3)、查看服务是否正常
-1. 服务启动成功后您可以通过，安装前端管理台，来检验服务的正常性，[点击跳转管理台安装文档](web_install.md)
-2. 您也可以通过Linkis用户手册来测试Linis是否能正常运行任务，[点击跳转用户手册](user_guide/overview.md)
+1. 服务启动成功后您可以通过，安装前端管理台，来检验服务的正常性，[点击跳转管理台安装文档](web-install.md)
+2. 您也可以通过Linkis用户手册来测试Linis是否能正常运行任务，[点击跳转用户手册](../user_guide/overview.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/sourcecode_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/sourcecode_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/sourcecode-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/start_metadatasource.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/start-metadatasource.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/start_metadatasource.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/start-metadatasource.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/web_install.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/web-install.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/web_install.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/web-install.md
index f883306786..bd07ba1ca1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/web_install.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/deployment/web-install.md
@@ -3,7 +3,7 @@ title: 前端管理台部署
sidebar_position: 6
---
-Linkis在1.0提供了单独的前端管理台功能，提供了展示Linis的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick_deploy.md)
+Linkis在1.0提供了单独的前端管理台功能，提供了展示Linis的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick-deploy.md)
## 1、准备工作
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis_compile_and_package.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis-compile-and-package.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis_compile_and_package.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis-compile-and-package.md
index 3c8d801b06..257f81407c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis_compile_and_package.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis-compile-and-package.md
@@ -107,7 +107,7 @@ __编译环境要求：__ 必须 **JDK8** 以上，**Oracle/Sun** 和 **OpenJDK
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/linkis-engineplugin-spark-x.x.x.jar
```
-如何单独安装 Spark 引擎？请参考 [Linkis 引擎插件安装文档](../deployment/engine_conn_plugin_installation)
+如何单独安装 Spark 引擎？请参考 [Linkis 引擎插件安装文档](../deployment/engine-conn-plugin-installation)
## 5. 如何修改Linkis的依赖的Hadoop、Hive、Spark版本
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis_config.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis-config.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis_config.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis-config.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis_debug_in_mac.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis-debug-in-mac.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis_debug_in_mac.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis-debug-in-mac.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis_debug.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis-debug.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis_debug.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/linkis-debug.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/new_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/new-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/new_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/new-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/web_build.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/web-build.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/web_build.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/development/web-build.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/flink.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/flink.md
index 71ae433cd2..2987dd4686 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/flink.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/flink.md
@@ -64,7 +64,7 @@ https://github.com/WeBankFinTech/Linkis/wiki/EngineConnPlugin%E5%BC%95%E6%93%8E%
Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3.Flink引擎的使用
@@ -118,7 +118,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
sh ./bin/linkis-cli -engineType flink-1.12.2 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 OnceEngineConn方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/hive.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/hive.md
index 0303af0383..d51ef395bb 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/hive.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/hive.md
@@ -35,13 +35,13 @@ on Tez，需要您按照此pr进行一下修改。
如果您已经编译完了您的hive引擎的插件已经编译完成，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 hive引擎的标签
Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.hive引擎的使用
@@ -57,7 +57,7 @@ hive的MapReduce任务是需要用到yarn的资源，所以需要您在一开始
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Hive任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -73,7 +73,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType hive-2.3.3 -codeType hql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/jdbc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/jdbc.md
index 010ef2ca24..1b1c1c2913 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/jdbc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/jdbc.md
@@ -42,7 +42,7 @@ wds.linkis.jdbc.password
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于JDBC任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -58,7 +58,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/python.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/python.md
index b72b7ce9d0..58678ea243 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/python.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/python.md
@@ -38,7 +38,7 @@ python3的，您可以简单更改配置就可以完成Python版本的切换，
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Python任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -54,7 +54,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/shell.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/shell.md
index 84bdc26630..98412d292f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/shell.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/shell.md
@@ -37,7 +37,7 @@ Shell引擎不需要用户自行编译，直接使用编译好的shell引擎插
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Shell任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -53,7 +53,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/spark.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/spark.md
index 18d4b3eed6..c743401f47 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/spark.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/engine_usage/spark.md
@@ -33,13 +33,13 @@ sidebar_position: 1
如果您已经编译完了您的spark引擎的插件已经编译完成，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 spark引擎的标签
Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.spark引擎的使用
@@ -54,7 +54,7 @@ Linkis1.0是通过标签来进行的，所以需要在我们数据库中插入
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Spark任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -76,7 +76,7 @@ sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -confMap wds.linkis.yarnqueue=dws -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/introduction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/introduction.md
index 9b4801cf4b..af847f870a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/introduction.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/introduction.md
@@ -44,8 +44,8 @@ Linkis 自2019年开源发布以来，已累计积累了700多家试验企业和
请前往[Linkis releases 页面](https://github.com/apache/incubator-linkis/releases) 下载Linkis 已编译的部署安装包或源码包。
## 编译和安装部署
-请参照[编译指引](development/linkis_compile_and_package.md) 来编译Linkis 源码。
-请参考[安装部署文档](deployment/quick_deploy.md) 来部署Linkis。
+请参照[编译指引](development/linkis-compile-and-package.md) 来编译Linkis 源码。
+请参考[安装部署文档](deployment/quick-deploy.md) 来部署Linkis。
## 示例和使用指引
请到[用户手册](user_guide/overview.md), [各引擎使用指引](engine_usage/overview.md) 和[API 文档](api/overview.md) 中，查看如何使用和管理Linkis 的示例和指引。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/release.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/release.md
index ad487e05db..98ba547763 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/release.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/release.md
@@ -3,13 +3,13 @@ title: 版本总览
sidebar_position: 0.1
---
-- [数据源管理服务架构文档](/architecture/public_enhancement_services/datasource_manager.md)
-- [元数据查询服务架构文档](/architecture/public_enhancement_services/metadata_manager.md)
-- [数据源介绍&功能使用指引](/deployment/start_metadatasource.md)
+- [数据源管理服务架构文档](/architecture/public_enhancement_services/datasource-manager.md)
+- [元数据查询服务架构文档](/architecture/public_enhancement_services/metadata-manager.md)
+- [数据源介绍&功能使用指引](/deployment/start-metadatasource.md)
- [数据源客户端的使用指引](/user_guide/linkis-datasource-client.md)
- [数据源http接口文档](/api/http/data-source-manager-api.md)
- [元数据查询服务http接口文档](/api/http/metadatamanager-api.md)
-- [开启SkyWalking功能](/deployment/involve_skywalking_into_linkis.md)
+- [开启SkyWalking功能](/deployment/involve-skywalking-into-linkis.md)
- [版本的release-notes](/download/release-notes-1.1.0)
## 参数变化
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/tuning_and_troubleshooting/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/tuning_and_troubleshooting/overview.md
index 337501e74f..3c575cfb57 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/tuning_and_troubleshooting/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/tuning_and_troubleshooting/overview.md
@@ -111,6 +111,6 @@ sidebar_position: 0
### 六、定位源码远程debug
-通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode_hierarchical_structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis_debug.md) 》一文调试对应微服务下的代码。
+通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode-hierarchical-structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis-debug.md) 》一文调试对应微服务下的代码。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade_from_0.X_to_1.0_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 97%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade-from-0.X-to-1.0-guide.md
index 55d8b3aa8a..1c3986b77d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 1
## 1. 注意事项
-**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference_between_1.0_and_0.x.md)**。
+**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference-between-1.0-and-0.x.md)**。
## 2. 服务升级安装
@@ -15,7 +15,7 @@ sidebar_position: 1
在安装时如果需要保留0.X的数据，一定要选择1跳过建表语句（见下面代码）。
-Linkis1.0 的安装可以参考[如何快速安装](deployment/quick_deploy.md)
+Linkis1.0 的安装可以参考[如何快速安装](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ Please input the choice: ## choice 1
## 4. 安装Linkis1.0
- 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装](deployment/quick_deploy.md)
+ 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装](deployment/quick-deploy.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade-guide.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade-guide.md
index a39412dfe3..1764b0380a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade_guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade-guide.md
@@ -18,7 +18,7 @@ sidebar_position: 2
## 2 服务升级安装
-按[部署指引文档](../deployment/quick_deploy)（文档中关于管理台的安装可以跳过），进行新版本的安装。
+按[部署指引文档](../deployment/quick-deploy)（文档中关于管理台的安装可以跳过），进行新版本的安装。
安装服务时，如果历史数据保留，请保留历史数据，如果无需保留数据，直接重装即可，也无需关注升级流程
```shell script
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/console_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/console-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/console_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/console-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/how_to_use.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/how-to-use.md
similarity index 94%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/how_to_use.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/how-to-use.md
index bc3e1af344..9627ebc2b5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.3/user_guide/how_to_use.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/how-to-use.md
@@ -7,9 +7,9 @@ sidebar_position: 1
## 1. Client端使用
如果需要在Linkis的基础上，接入其它应用，需要针对Linkis提供的接口进行开发，Linkis提供了多种客户端接入接口，更详细的使用介绍可以参考以下内容：
-- [**Restful API使用方式**](api/linkis_task_operator.md)
-- [**JDBC API使用方式**](api/jdbc_api.md)
-- [**Java SDK使用方式**](user_guide/sdk_manual.md)
+- [**Restful API使用方式**](api/linkis-task-operator.md)
+- [**JDBC API使用方式**](api/jdbc-api.md)
+- [**Java SDK使用方式**](../user_guide/sdk-manual.md)
## 2. Scriptis使用Linkis
如果需要使用Linkis完成交互式在线分析处理的工作，并且不需要诸如工作流开发、工作流调度、数据服务等数据分析应用工具，可以单独安装[**Scriptis**](https://github.com/WeBankFinTech/Scriptis)，详细安装教程可参考其对应的安装部署文档。
### 2.1. 使用Scriptis执行脚本
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/linkiscli_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/linkiscli-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/linkiscli_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/linkiscli-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/overview.md
index 6f53e8b095..bf7a2e26d6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis在设计之初就考虑接入方式的拓展性问题，针对不同的接入场景，Linkis提供了前端接入和SDK接入的方式，在前端接口上又提供了HTTP和WebSocket两种方式，如果对接入并使用Linkis感兴趣，可以参考以下文档：
-- [如何使用Links](how_to_use.md)
-- [Linkis-Cli的使用](linkiscli_manual.md)
-- [Linkis JAVA SDK的使用](sdk_manual.md)
-- [Linkis管理台的使用](console_manual.md)
+- [如何使用Links](how-to-use.md)
+- [Linkis-Cli的使用](linkiscli-manual.md)
+- [Linkis JAVA SDK的使用](sdk-manual.md)
+- [Linkis管理台的使用](console-manual.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/sdk_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/sdk-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/sdk_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/user_guide/sdk-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/jdbc_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/jdbc-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/jdbc_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/jdbc-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/linkis_task_operator.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/linkis-task-operator.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/linkis_task_operator.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/linkis-task-operator.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/login_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/login-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/login_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/login-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/overview.md
index 987616848e..a4d0d3889a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 1
## 1. 文档说明
Linkis1.0 在Linkix0.x版本的基础上进行了重构优化，同时也兼容了0.x的接口，但是为了防止在使用1.0版本时存在兼容性问题，需要您仔细阅读以下文档：
-1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login_api.md)。
+1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login-api.md)。
-2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc_api.md)。
+2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc-api.md)。
-3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis_task_operator.md)。
\ No newline at end of file
+3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis-task-operator.md)。
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/add_an_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/add-an-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/add_an_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/add-an-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/commons/message_scheduler.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/commons/message-scheduler.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/commons/message_scheduler.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/commons/message-scheduler.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn_plugin.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/app_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/label_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/resource_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/overview.md
index 65ea36c02d..b77e15fd3a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/computation_governance_services/overview.md
@@ -66,10 +66,10 @@ Linkis1.0将优化Job的整体执行流程，从提交 —\> 准备 —\>
EngineConnManager (简称ECM)是 Linkis0.X EngineManager 的精简升级版。Linkis1.0下的ECM去除了引擎的申请能力，整个微服务完全无状态，将聚焦于支持各类 EngineConn 的启动和销毁。
- [进入EngineConnManager架构设计](engine/engine_conn_manager.md)
+ [进入EngineConnManager架构设计](engine/engine-conn-manager.md)
### 5、EngineConn
EngineConn 是 Linkis0.X Engine 的优化升级版本，将提供 EngineConn 和 Executor 两大模块，其中 EngineConn 用于连接底层的计算存储引擎，提供一个打通了底层各计算存储引擎的 Session 会话；Executor 则基于这个 Session 会话，提供交互式计算、流式计算、离线计算、数据存储的全栈计算能力支持。
-[进入EngineConn架构设计](engine/engine_conn.md)
+[进入EngineConn架构设计](engine/engine-conn.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/difference_between_1.0_and_0.x.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/difference_between_1.0_and_0.x.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/difference-between-1.0-and-0.x.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/job_submission_preparation_and_execution_process.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/job_submission_preparation_and_execution_process.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/job-submission-preparation-and-execution-process.md
index d0a8dcfc82..88fa0409a1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/job_submission_preparation_and_execution_process.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/job-submission-preparation-and-execution-process.md
@@ -38,7 +38,7 @@ sidebar_position: 1
1. 首先，Client（如前端或客户端）发起Job请求，Job请求信息精简如下
-（关于Linkis的具体使用方式，请参考 [如何使用Linkis](user_guide/how_to_use.md)）：
+（关于Linkis的具体使用方式，请参考 [如何使用Linkis](../user_guide/how-to-use.md)）：
```
POST /api/rest_j/v1/entrance/submit
@@ -74,7 +74,7 @@ POST /api/rest_j/v1/entrance/submit
如何定义可复用EngineConn？指能匹配计算任务的所有标签要求的，且EngineConn本身健康状态为Healthy（负载低且实际EngineConn状态为Idle）的，然后再按规则对所有满足条件的EngineConn进行排序选择，最终锁定一个最佳的EngineConn。
-如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](add_an_engine_conn.md) 。
+如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](add-an-engine-conn.md) 。
#### 2.2 计算任务编排
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/overview.md
index 28f24690a5..1fdb1b395d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/overview.md
@@ -18,7 +18,7 @@ Linkis 1.0 将所有微服务总体划分为三大类：公共增强服务、计
以下是 Linkis1.0 架构文档的目录列表：
-1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference_between_1.0_and_0.x)。
+1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference-between-1.0-and-0.x)。
2. Linkis1.0公共增强服务相关文档，请阅读[公共增强服务](public_enhancement_services/overview.md)。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/proxy_user.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/proxy-user.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/proxy_user.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/proxy-user.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/bml/engine_bml_dissect.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/bml/engine-bml-dissect.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/bml/engine_bml_dissect.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/bml/engine-bml-dissect.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_cache.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_client.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_client.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_listener.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_persistence.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_search.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_search.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/overview.md
index 2992203775..68591cc538 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/context_service/overview.md
@@ -101,29 +101,29 @@ CS，用于解决一个数据应用开发流程，跨多个系统间的数据和
### 1. Client
外部访问CS的入口，Client模块提供HA功能；
-[进入Client架构设计](context_service_client.md)
+[进入Client架构设计](context-service-client.md)
### 2. Service模块
提供Restful接口，封装和处理客户端提交的CS请求；
-[进入Service架构设计](context_service.md)
+[进入Service架构设计](context-service.md)
### 3. ContextSearch
上下文查询模块，提供丰富和强大的查询能力，供客户端查找上下文的Key-Value键值对；
-[进入ContextSearch架构设计](context_service_search.md)
+[进入ContextSearch架构设计](context-service-search.md)
### 4. Listener
CS的监听器模块，提供同步和异步的事件消费能力，具备类似Zookeeper的Key-Value一旦更新，实时通知Client的能力；
-[进入Listener架构设计](context_service_listener.md)
+[进入Listener架构设计](context-service-listener.md)
### 5. ContextCache
上下文的内存缓存模块，提供快速检索上下文的能力和对JVM内存使用的监听和清理能力；
-[进入ContextCache架构设计](context_service_cache.md)
+[进入ContextCache架构设计](context-service-cache.md)
### 6. HighAvailable
提供CS高可用能力；
-[进入HighAvailable架构设计](context_service_highavailable.md)
+[进入HighAvailable架构设计](context-service-highavailable.md)
### 7. Persistence
CS的持久化功能；
-[进入Persistence架构设计](context_service_persistence.md)
+[进入Persistence架构设计](context-service-persistence.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/datasource_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/datasource-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/datasource_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/datasource-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/metadata_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/metadata-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/metadata_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/metadata-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/public_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/public_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/architecture/public_enhancement_services/public-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/cluster_deployment.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/cluster-deployment.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/cluster_deployment.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/cluster-deployment.md
index d27e6b8600..8b057e86db 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/cluster_deployment.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/cluster-deployment.md
@@ -98,7 +98,7 @@ EngineConnManager（ECM）使用总资源
模式：Eureka服务多活部署 ，部分服务部署在服务器A，部分服务部署在服务器B上
### 2.1 分布式部署的环境准备
-和服务器A一样，服务器B需要进行基础的环境准备，请参考[Linkis环境准备](quick_deploy#3-linkis%E7%8E%AF%E5%A2%83%E5%87%86%E5%A4%87)
+和服务器A一样，服务器B需要进行基础的环境准备，请参考[Linkis环境准备](quick-deploy#3-linkis%E7%8E%AF%E5%A2%83%E5%87%86%E5%A4%87)
### 2.2 Eureka多活配置调整
注册中心Eureka服务，需要部署在服务器A和服务器B上，
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/engine_conn_plugin_installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/engine_conn_plugin_installation.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/engine-conn-plugin-installation.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/installation_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/installation_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/installation-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/involve_skywalking_into_linkis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/involve-skywalking-into-linkis.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/involve_skywalking_into_linkis.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/involve-skywalking-into-linkis.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/linkis_scriptis_install.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/linkis-scriptis-install.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/linkis_scriptis_install.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/linkis-scriptis-install.md
index ec0c4be813..b4ed7a3c02 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/linkis_scriptis_install.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/linkis-scriptis-install.md
@@ -8,7 +8,7 @@ sidebar_position: 10
> 在 Apache Linkis >= 1.1.1 和 DSS >= 1.1.0 之后，支持将 scriptis 单独部署和 Linkis 进行搭配使用，使用 scriptis 的交互式分析的功能，可以在 web 页面在线写 SQL、Pyspark、HiveQL 等脚本，提交给 Linkis 执行且支持 UDF、函数、资源管控和自定义变量等特性，本文将介绍如何单独部署 Web 组件-scriptis，并通过 scriptis 这种 Web 页面来使用 Apache Linkis 。
-前提:已经成功安装并可以正常使用了 Linkis 服务（后端和管理台服务），Linkis 的部署流程可以见[Apache Linkis 的快速部署 ](quick_deploy.md)
+前提:已经成功安装并可以正常使用了 Linkis 服务（后端和管理台服务），Linkis 的部署流程可以见[Apache Linkis 的快速部署 ](quick-deploy.md)
示例说明:
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/quick_deploy.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/quick-deploy.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/quick_deploy.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/quick-deploy.md
index a22e9f78f9..cd95a5f62d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/quick_deploy.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/quick-deploy.md
@@ -43,7 +43,7 @@ hadoop ALL=(ALL) NOPASSWD: NOPASSWD: ALL
### 2.1 安装包准备
- 方式1：从官网[下载地址](https://linkis.apache.org/zh-CN/download/main):https://linkis.apache.org/zh-CN/download/main，下载对应的安装包(项目安装包和管理台安装包)
-- 方式2：根据[Linkis 编译打包](../development/linkis_compile_and_package)和[前端管理台编译](../development/web_build) 自行编译出项目安装包和管理台安装包
+- 方式2：根据[Linkis 编译打包](../development/linkis-compile-and-package)和[前端管理台编译](../development/web-build) 自行编译出项目安装包和管理台安装包
上传安装包`apache-linkis-x.x.x-incubating-bin.tar.gz`后，进行解压安装包
@@ -383,7 +383,7 @@ wds.linkis.admin.user= #用户
wds.linkis.admin.password= #密码
```
-管理台使用指引见[使用手册](user_guide/console_manual.md)
+管理台使用指引见[使用手册](../user_guide/console-manual.md)
## 5. 验证基础功能
>根据实际需求，验证对应的引擎任务
@@ -407,13 +407,13 @@ sh bin/linkis-cli -submitUser hadoop -engineType python-python2 -codeType pyth
## 6 开发工具IDE（Scriptis）的安装(可选)
>安装Scripti工具后，可以支持在web页面在线写SQL、Pyspark、HiveQL等脚本
-详细指引见[工具Scriptis的安装部署](./linkis_scriptis_install)
+详细指引见[工具Scriptis的安装部署](./linkis-scriptis-install)
## 7 支持的引擎
### 7.1 引擎适配列表
-请注意：Linkis的单独安装包默认只包含的：Python/Shell/Hive/Spark四个引擎，如果有其他的引擎(如jdbc/flink/sqoop等引擎)使用场景，可以手动安装，具体请参考 [EngineConnPlugin引擎插件安装文档](engine_conn_plugin_installation)。
+请注意：Linkis的单独安装包默认只包含的：Python/Shell/Hive/Spark四个引擎，如果有其他的引擎(如jdbc/flink/sqoop等引擎)使用场景，可以手动安装，具体请参考 [EngineConnPlugin引擎插件安装文档](engine-conn-plugin-installation)。
本版本已适配的支持引擎列表如下：
@@ -521,7 +521,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
查看引擎的物料记录是否存在(如果有更新,查看更新时间是否正确)。
-- 如果不存在或则未更新，先尝试手动刷新物料资源(详细见[引擎物料资源刷新](engine_conn_plugin_installation#23-引擎刷新))。
+- 如果不存在或则未更新，先尝试手动刷新物料资源(详细见[引擎物料资源刷新](engine-conn-plugin-installation#23-引擎刷新))。
- 通过`log/linkis-cg-engineplugin.log`日志，查看物料失败的具体原因，很多时候可能是hdfs目录没有权限导致
- 检查gateway地址配置是否正确`conf/linkis.properties`的配置项`wds.linkis.gateway.url`
@@ -616,7 +616,7 @@ CDH本身不是使用的官方标准的hive/spark包,进行适配时，最好修
### 8.9 Http接口的调试
-- 方式1 可以开启[免登陆模式指引](/docs/latest/api/login_api/#2免登录配置)
+- 方式1 可以开启[免登陆模式指引](/docs/latest/api/login-api/#2免登录配置)
- 方式2 postman中的，请求头带上登陆成功的cookie值
cookie值可以在浏览器端登陆成功后，获取
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/sourcecode_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/sourcecode_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/sourcecode-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/start_metadatasource.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/start-metadatasource.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/start_metadatasource.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/start-metadatasource.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/unpack_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/unpack-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/unpack_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/unpack-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/web_install.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/web-install.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/web_install.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/web-install.md
index 7518e9267b..a3a9dbbce2 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/web_install.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/deployment/web-install.md
@@ -5,7 +5,7 @@ sidebar_position: 6
> web端是使用nginx作为静态资源服务器的，访问请求流程是:`Linkis管理台请求->nginx ip:port->linkis-gateway ip:port-> 其他服务`
-Linkis 提供了单独的前端管理台功能，提供了展示历史任务的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick_deploy.md)
+Linkis 提供了单独的前端管理台功能，提供了展示历史任务的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick-deploy.md)
## 1 准备工作
@@ -167,7 +167,7 @@ wds.linkis.admin.user= #用户
wds.linkis.admin.password= #密码
```
-管理台使用指引见[使用手册](user_guide/console_manual.md)
+管理台使用指引见[使用手册](../user_guide/console-manual.md)
## 4 注意事项
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis_compile_and_package.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis-compile-and-package.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis_compile_and_package.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis-compile-and-package.md
index 6679eaf944..da0b786f7f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/development/linkis_compile_and_package.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis-compile-and-package.md
@@ -107,7 +107,7 @@ __编译环境要求：__ 必须 **JDK8** 以上，**Oracle/Sun** 和 **OpenJDK
#spark文件下就是编译好的引擎物料
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/out/spark
```
-如何单独安装 Spark 引擎？请参考 [Linkis 引擎插件安装文档](../deployment/engine_conn_plugin_installation)
+如何单独安装 Spark 引擎？请参考 [Linkis 引擎插件安装文档](../deployment/engine-conn-plugin-installation)
### 3.2 如何将非默认引擎打包至安装部署包中
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis_config.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis-config.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis_config.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis-config.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis_debug_in_mac.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis-debug-in-mac.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis_debug_in_mac.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis-debug-in-mac.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis_debug.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis-debug.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis_debug.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis-debug.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/new_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/new-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/new_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/new-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/web_build.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/web-build.md
similarity index 97%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/web_build.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/web-build.md
index a838ca952e..2d8da5a999 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/web_build.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/web-build.md
@@ -38,7 +38,7 @@ $ npm install
```
$ npm run build
```
-上述命令执行成功后，会生成前端管理台安装包 `apache-linkis-${version}-incubating-web-bin.tar.gz`，可以直接将该文件夹放进您的静态服务器中，或者参考[安装文档](../deployment/web_install.md)，使用脚本进行部署安装。
+上述命令执行成功后，会生成前端管理台安装包 `apache-linkis-${version}-incubating-web-bin.tar.gz`，可以直接将该文件夹放进您的静态服务器中，或者参考[安装文档](../deployment/web-install.md)，使用脚本进行部署安装。
## 3 . 注意事项
### 3.1 Windows下npm install 步骤报错
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/flink.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/flink.md
index 12979f32cf..cfd311edf9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/flink.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/flink.md
@@ -58,12 +58,12 @@ cd ${LINKIS_HOME}/sbin
sh linkis-daemon.sh restart cg-engineplugin
```
engineplugin更详细的介绍可以参看下面的文章。
-https://linkis.apache.org/zh-CN/docs/1.1.1/deployment/engine_conn_plugin_installation
+https://linkis.apache.org/zh-CN/docs/1.1.1/deployment/engine-conn-plugin-installation
### 2.3 Flink引擎的标签
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3.Flink引擎的使用
@@ -117,7 +117,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
sh ./bin/linkis-cli -engineType flink-1.12.2 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 OnceEngineConn方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/hive.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/hive.md
index 47116ad53a..277c76d7a4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/hive.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/hive.md
@@ -35,13 +35,13 @@ on Tez，需要您按照此pr进行一下修改。
如果您已经编译完了您的hive引擎的插件已经编译完成，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 hive引擎的标签
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.hive引擎的使用
@@ -57,7 +57,7 @@ hive的MapReduce任务是需要用到yarn的资源，所以需要您在一开始
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Hive任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -73,7 +73,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType hive-2.3.3 -codeType hql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/jdbc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/jdbc.md
index fcd68a8f81..ef28f4d89f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/jdbc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/jdbc.md
@@ -44,7 +44,7 @@ sh linkis-daemon.sh restart cg-engineplugin
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3.JDBC引擎的使用
@@ -91,7 +91,7 @@ http 请求参数示例
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于JDBC任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -107,7 +107,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/openlookeng.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/openlookeng.md
index de4bb7a6a6..0ae5796613 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/openlookeng.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/openlookeng.md
@@ -47,7 +47,7 @@ sh linkis-daemon.sh restart cg-engineplugin
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3 引擎的使用
@@ -84,7 +84,7 @@ http 请求参数示例
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于openlookeng任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -100,5 +100,5 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType openlookeng-1.5.0 -codeType sql -code 'show databases;' -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/pipeline.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/pipeline.md
index 3bc6be11c1..5ea16b1ef9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/pipeline.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/pipeline.md
@@ -55,7 +55,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 2 引擎的使用
@@ -73,7 +73,7 @@ sh bin/linkis-cli -submitUser hadoop -engineType pipeline-1 -codeType pipelin
```
`from hdfs:///000/000/000/A.dolphin to file:///000/000/000/B.csv` 该内容 2.3 有解释
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/python.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/python.md
index eaba419773..ec656620bb 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/python.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/python.md
@@ -34,7 +34,7 @@ python3的，您可以简单更改配置就可以完成Python版本的切换，
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Python任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -50,7 +50,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/shell.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/shell.md
index d40e903ad7..6a509306ac 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/shell.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/shell.md
@@ -37,7 +37,7 @@ Shell引擎不需要用户自行编译，直接使用编译好的shell引擎插
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Shell任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -53,7 +53,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/spark.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/spark.md
index 780a4cbe8e..b4d9aa732a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/spark.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/engine_usage/spark.md
@@ -33,13 +33,13 @@ sidebar_position: 1
如果您已经编译完了您的spark引擎的插件，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 spark引擎的标签
Linkis1.X是通过标签配置来区分引擎版本的，所以需要我们在数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.spark引擎的使用
@@ -54,7 +54,7 @@ Linkis1.X是通过标签配置来区分引擎版本的，所以需要我们在
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Spark任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -76,7 +76,7 @@ sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -confMap wds.linkis.yarnqueue=dws -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/introduction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/introduction.md
index 2260bb8504..98867e7620 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/introduction.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/introduction.md
@@ -50,7 +50,7 @@ Linkis 自2019年开源发布以来，已累计积累了700多家试验企业和
## 安装部署
-请参考[安装部署文档](deployment/quick_deploy.md) 来部署Linkis
+请参考[安装部署文档](deployment/quick-deploy.md) 来部署Linkis
## 示例和使用指引
- [用户手册](user_guide/overview.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/release.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/release.md
index c82f084a29..1d1e539827 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/release.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/release.md
@@ -2,7 +2,7 @@
title: 版本总览
sidebar_position: 0.1
---
-- [代理用户模式介绍](/architecture/proxy_user.md)
+- [代理用户模式介绍](/architecture/proxy-user.md)
- [UDF函数介绍和使用指引](/user_guide/udf.md)
- [引擎物料刷新HTTP接口](/api/http/engineconn-plugin-refesh.md)
- [UDF相关的HTTP接口](/api/http/udf-api.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/tuning_and_troubleshooting/error_guide/error_code.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/tuning_and_troubleshooting/error_guide/error-code.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/tuning_and_troubleshooting/error_guide/error_code.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/tuning_and_troubleshooting/error_guide/error-code.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/tuning_and_troubleshooting/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/tuning_and_troubleshooting/overview.md
index 337501e74f..3c575cfb57 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/tuning_and_troubleshooting/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/tuning_and_troubleshooting/overview.md
@@ -111,6 +111,6 @@ sidebar_position: 0
### 六、定位源码远程debug
-通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode_hierarchical_structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis_debug.md) 》一文调试对应微服务下的代码。
+通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode-hierarchical-structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis-debug.md) 》一文调试对应微服务下的代码。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade_from_0.X_to_1.0_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 97%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade-from-0.X-to-1.0-guide.md
index 55d8b3aa8a..1c3986b77d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 1
## 1. 注意事项
-**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference_between_1.0_and_0.x.md)**。
+**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference-between-1.0-and-0.x.md)**。
## 2. 服务升级安装
@@ -15,7 +15,7 @@ sidebar_position: 1
在安装时如果需要保留0.X的数据，一定要选择1跳过建表语句（见下面代码）。
-Linkis1.0 的安装可以参考[如何快速安装](deployment/quick_deploy.md)
+Linkis1.0 的安装可以参考[如何快速安装](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ Please input the choice: ## choice 1
## 4. 安装Linkis1.0
- 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装](deployment/quick_deploy.md)
+ 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装](deployment/quick-deploy.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade-guide.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade-guide.md
index ffa8a437b3..1f129dbde5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade_guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/upgrade/upgrade-guide.md
@@ -18,7 +18,7 @@ sidebar_position: 2
## 2 服务升级安装
-按[部署指引文档](../deployment/quick_deploy)（文档中关于管理台的安装可以跳过），进行新版本的安装。
+按[部署指引文档](../deployment/quick-deploy)（文档中关于管理台的安装可以跳过），进行新版本的安装。
安装服务时，如果历史数据保留，请保留历史数据，如果无需保留数据，直接重装即可，也无需关注升级流程
```shell script
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/console_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/console-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/console_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/console-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how_to_use.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/how-to-use.md
similarity index 94%
copy from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how_to_use.md
copy to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/how-to-use.md
index bc3e1af344..9627ebc2b5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how_to_use.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/how-to-use.md
@@ -7,9 +7,9 @@ sidebar_position: 1
## 1. Client端使用
如果需要在Linkis的基础上，接入其它应用，需要针对Linkis提供的接口进行开发，Linkis提供了多种客户端接入接口，更详细的使用介绍可以参考以下内容：
-- [**Restful API使用方式**](api/linkis_task_operator.md)
-- [**JDBC API使用方式**](api/jdbc_api.md)
-- [**Java SDK使用方式**](user_guide/sdk_manual.md)
+- [**Restful API使用方式**](api/linkis-task-operator.md)
+- [**JDBC API使用方式**](api/jdbc-api.md)
+- [**Java SDK使用方式**](../user_guide/sdk-manual.md)
## 2. Scriptis使用Linkis
如果需要使用Linkis完成交互式在线分析处理的工作，并且不需要诸如工作流开发、工作流调度、数据服务等数据分析应用工具，可以单独安装[**Scriptis**](https://github.com/WeBankFinTech/Scriptis)，详细安装教程可参考其对应的安装部署文档。
### 2.1. 使用Scriptis执行脚本
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/how_to_use.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/how_to_use.md
deleted file mode 100644
index bc3e1af344..0000000000
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/how_to_use.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 如何使用 Linkis1.0
-sidebar_position: 1
----
-
- Linkis为了满足不同的使用场景需求，提供多种使用和接入方式，概括为三类，分别是Client端使用、Scriptis端使用、DataSphere Studio端使用，其中Scriptis和DataSphere Studio是微众银行大数据平台室开源的数据分析平台，由于这两个项目本质上完全兼容Linkis，所以通过Scriptis和DataSphere Studio使用Linkis最为简单。
-## 1. Client端使用
-
- 如果需要在Linkis的基础上，接入其它应用，需要针对Linkis提供的接口进行开发，Linkis提供了多种客户端接入接口，更详细的使用介绍可以参考以下内容：
-- [**Restful API使用方式**](api/linkis_task_operator.md)
-- [**JDBC API使用方式**](api/jdbc_api.md)
-- [**Java SDK使用方式**](user_guide/sdk_manual.md)
-## 2. Scriptis使用Linkis
- 如果需要使用Linkis完成交互式在线分析处理的工作，并且不需要诸如工作流开发、工作流调度、数据服务等数据分析应用工具，可以单独安装[**Scriptis**](https://github.com/WeBankFinTech/Scriptis)，详细安装教程可参考其对应的安装部署文档。
-### 2.1. 使用Scriptis执行脚本
- 目前Scriptis支持向Linkis提交多种任务类型，包括Spark SQL、Hive SQL、Scala、PythonSpark等，为了满足数据分析的需求，Scriptis左侧，提供查看用户工作空间信息、用户数据库和表信息、用户自定义函数，以及HDFS目录，同时支持上传下载，结果集导出等功能。Scriptis使用Linkis十分简单，可以很方便的在编辑栏书写脚本，提交到Linkis运行。
-
-### 2.2. Scriptis管理台
- Linkis提供资源配置和管理的接口，如果希望对任务资源进行配置管理，可以在Scriptis的管理台界面进行设置，包括队列设置、资源配置、引擎实例个数等。通过管理台，可以很方便的配置向Linkis提交任务的资源，使得更加方便快捷。
-
-
-## 3. DataSphere Studio使用Linkis
- [**DataSphere Studio**](https://github.com/WeBankFinTech/DataSphereStudio)简称DSS，是微众银行大数据平台开源的一站式数据分析处理平台，DSS交互式分析模块集成了Scriptis，使用DSS进行交互式分析和Scriptis一样，除了提供Scriptis的基本功能外，DSS提供和集成了更加丰富和强大的数据分析功能，包括用于数据提取的数据服务、开发报表的工作流、可视化分析软件Visualis等。由于原生的支持，目前DSS是与Linkis集成度最高的软件，如果希望使用完整的Linkis功能，建议使用DSS搭配Linkis一起使用。
-
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/linkiscli_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/linkiscli-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/linkiscli_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/linkiscli-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/overview.md
index 6f53e8b095..bf7a2e26d6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis在设计之初就考虑接入方式的拓展性问题，针对不同的接入场景，Linkis提供了前端接入和SDK接入的方式，在前端接口上又提供了HTTP和WebSocket两种方式，如果对接入并使用Linkis感兴趣，可以参考以下文档：
-- [如何使用Links](how_to_use.md)
-- [Linkis-Cli的使用](linkiscli_manual.md)
-- [Linkis JAVA SDK的使用](sdk_manual.md)
-- [Linkis管理台的使用](console_manual.md)
+- [如何使用Links](how-to-use.md)
+- [Linkis-Cli的使用](linkiscli-manual.md)
+- [Linkis JAVA SDK的使用](sdk-manual.md)
+- [Linkis管理台的使用](console-manual.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/sdk_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/sdk-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/sdk_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/user_guide/sdk-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/jdbc_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/jdbc-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/jdbc_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/jdbc-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/linkis_task_operator.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/linkis-task-operator.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/linkis_task_operator.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/linkis-task-operator.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/login_api.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/login-api.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/login_api.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/login-api.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/overview.md
index 987616848e..a4d0d3889a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 1
## 1. 文档说明
Linkis1.0 在Linkix0.x版本的基础上进行了重构优化，同时也兼容了0.x的接口，但是为了防止在使用1.0版本时存在兼容性问题，需要您仔细阅读以下文档：
-1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login_api.md)。
+1. 使用Linkis1.0定制化开发时，需要使用到Linkis的权限认证接口，请仔细阅读 [登录API文档](login-api.md)。
-2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc_api.md)。
+2. Linkis1.0提供JDBC的接口，需要使用JDBC的方式接入Linkis，请仔细阅读[任务提交执行JDBC API文档](jdbc-api.md)。
-3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis_task_operator.md)。
\ No newline at end of file
+3. Linkis1.0提供了Rest接口，如果需要在Linkis的基础上开发上层应用，请仔细阅读[任务提交执行Rest API文档](linkis-task-operator.md)。
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/commons/message_scheduler.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/commons/message-scheduler.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/commons/message_scheduler.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/commons/message-scheduler.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/add_an_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/add-an-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/add_an_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/add-an-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn_plugin.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/proxy_user.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/proxy-user.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/proxy_user.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/engine/proxy-user.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
index 833acc99f4..dfc1603585 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
@@ -38,7 +38,7 @@ sidebar_position: 1
1. 首先，Client（如前端或客户端）发起Job请求，Job请求信息精简如下
- （关于Linkis的具体使用方式，请参考 [如何使用Linkis](user_guide/how_to_use.md)）：
+ （关于Linkis的具体使用方式，请参考 [如何使用Linkis](user_guide/how-to-use.md)）：
```
POST /api/rest_j/v1/entrance/submit
@@ -74,7 +74,7 @@ POST /api/rest_j/v1/entrance/submit
如何定义可复用EngineConn？指能匹配计算任务的所有标签要求的，且EngineConn本身健康状态为Healthy（负载低且实际EngineConn状态为Idle）的，然后再按规则对所有满足条件的EngineConn进行排序选择，最终锁定一个最佳的EngineConn。
-如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](engine/add_an_engine_conn.md) 。
+如果该用户不存在可复用的EngineConn，则此时会触发EngineConn新增流程，关于EngineConn新增流程，请参阅：[EngineConn新增流程](engine/add-an-engine-conn.md) 。
#### 2.2 计算任务编排
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/app_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/label_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/resource_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/overview.md
index 65ea36c02d..b77e15fd3a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/computation_governance_services/overview.md
@@ -66,10 +66,10 @@ Linkis1.0将优化Job的整体执行流程，从提交 —\> 准备 —\>
EngineConnManager (简称ECM)是 Linkis0.X EngineManager 的精简升级版。Linkis1.0下的ECM去除了引擎的申请能力，整个微服务完全无状态，将聚焦于支持各类 EngineConn 的启动和销毁。
- [进入EngineConnManager架构设计](engine/engine_conn_manager.md)
+ [进入EngineConnManager架构设计](engine/engine-conn-manager.md)
### 5、EngineConn
EngineConn 是 Linkis0.X Engine 的优化升级版本，将提供 EngineConn 和 Executor 两大模块，其中 EngineConn 用于连接底层的计算存储引擎，提供一个打通了底层各计算存储引擎的 Session 会话；Executor 则基于这个 Session 会话，提供交互式计算、流式计算、离线计算、数据存储的全栈计算能力支持。
-[进入EngineConn架构设计](engine/engine_conn.md)
+[进入EngineConn架构设计](engine/engine-conn.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/difference_between_1.0_and_0.x.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/difference_between_1.0_and_0.x.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/difference-between-1.0-and-0.x.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/overview.md
index 28f24690a5..1fdb1b395d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/overview.md
@@ -18,7 +18,7 @@ Linkis 1.0 将所有微服务总体划分为三大类：公共增强服务、计
以下是 Linkis1.0 架构文档的目录列表：
-1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference_between_1.0_and_0.x)。
+1. Linkis1.0在架构上的特点，请阅读[Linkis1.0 与 Linkis0.x 的区别](difference-between-1.0-and-0.x)。
2. Linkis1.0公共增强服务相关文档，请阅读[公共增强服务](public_enhancement_services/overview.md)。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/bml/engine_bml_dissect.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/bml/engine-bml-dissect.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/bml/engine_bml_dissect.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/bml/engine-bml-dissect.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_cache.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_client.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_client.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_listener.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_persistence.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_search.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_search.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/overview.md
index 2992203775..68591cc538 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/context_service/overview.md
@@ -101,29 +101,29 @@ CS，用于解决一个数据应用开发流程，跨多个系统间的数据和
### 1. Client
外部访问CS的入口，Client模块提供HA功能；
-[进入Client架构设计](context_service_client.md)
+[进入Client架构设计](context-service-client.md)
### 2. Service模块
提供Restful接口，封装和处理客户端提交的CS请求；
-[进入Service架构设计](context_service.md)
+[进入Service架构设计](context-service.md)
### 3. ContextSearch
上下文查询模块，提供丰富和强大的查询能力，供客户端查找上下文的Key-Value键值对；
-[进入ContextSearch架构设计](context_service_search.md)
+[进入ContextSearch架构设计](context-service-search.md)
### 4. Listener
CS的监听器模块，提供同步和异步的事件消费能力，具备类似Zookeeper的Key-Value一旦更新，实时通知Client的能力；
-[进入Listener架构设计](context_service_listener.md)
+[进入Listener架构设计](context-service-listener.md)
### 5. ContextCache
上下文的内存缓存模块，提供快速检索上下文的能力和对JVM内存使用的监听和清理能力；
-[进入ContextCache架构设计](context_service_cache.md)
+[进入ContextCache架构设计](context-service-cache.md)
### 6. HighAvailable
提供CS高可用能力；
-[进入HighAvailable架构设计](context_service_highavailable.md)
+[进入HighAvailable架构设计](context-service-highavailable.md)
### 7. Persistence
CS的持久化功能；
-[进入Persistence架构设计](context_service_persistence.md)
+[进入Persistence架构设计](context-service-persistence.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/datasource_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/datasource-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/datasource_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/datasource-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/metadata_manager.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/metadata-manager.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/metadata_manager.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/metadata-manager.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/public_service.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/public_service.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/architecture/public_enhancement_services/public-service.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/cluster_deployment.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/cluster-deployment.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/cluster_deployment.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/cluster-deployment.md
index d27e6b8600..8b057e86db 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/cluster_deployment.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/cluster-deployment.md
@@ -98,7 +98,7 @@ EngineConnManager（ECM）使用总资源
模式：Eureka服务多活部署 ，部分服务部署在服务器A，部分服务部署在服务器B上
### 2.1 分布式部署的环境准备
-和服务器A一样，服务器B需要进行基础的环境准备，请参考[Linkis环境准备](quick_deploy#3-linkis%E7%8E%AF%E5%A2%83%E5%87%86%E5%A4%87)
+和服务器A一样，服务器B需要进行基础的环境准备，请参考[Linkis环境准备](quick-deploy#3-linkis%E7%8E%AF%E5%A2%83%E5%87%86%E5%A4%87)
### 2.2 Eureka多活配置调整
注册中心Eureka服务，需要部署在服务器A和服务器B上，
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/deploy_linkis_without_hdfs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/deploy-linkis-without-hdfs.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/deploy_linkis_without_hdfs.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/deploy-linkis-without-hdfs.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/engine_conn_plugin_installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/engine_conn_plugin_installation.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/engine-conn-plugin-installation.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/installation_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/installation_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/installation-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/involve_skywalking_into_linkis.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/involve-skywalking-into-linkis.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/involve_skywalking_into_linkis.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/involve-skywalking-into-linkis.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/linkis_scriptis_install.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/linkis-scriptis-install.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/linkis_scriptis_install.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/linkis-scriptis-install.md
index ec0c4be813..b4ed7a3c02 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/deployment/linkis_scriptis_install.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/linkis-scriptis-install.md
@@ -8,7 +8,7 @@ sidebar_position: 10
> 在 Apache Linkis >= 1.1.1 和 DSS >= 1.1.0 之后，支持将 scriptis 单独部署和 Linkis 进行搭配使用，使用 scriptis 的交互式分析的功能，可以在 web 页面在线写 SQL、Pyspark、HiveQL 等脚本，提交给 Linkis 执行且支持 UDF、函数、资源管控和自定义变量等特性，本文将介绍如何单独部署 Web 组件-scriptis，并通过 scriptis 这种 Web 页面来使用 Apache Linkis 。
-前提:已经成功安装并可以正常使用了 Linkis 服务（后端和管理台服务），Linkis 的部署流程可以见[Apache Linkis 的快速部署 ](quick_deploy.md)
+前提:已经成功安装并可以正常使用了 Linkis 服务（后端和管理台服务），Linkis 的部署流程可以见[Apache Linkis 的快速部署 ](quick-deploy.md)
示例说明:
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/quick_deploy.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/quick-deploy.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/quick_deploy.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/quick-deploy.md
index b67f802a7d..adb6c964b8 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/quick_deploy.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/quick-deploy.md
@@ -43,7 +43,7 @@ hadoop ALL=(ALL) NOPASSWD: NOPASSWD: ALL
### 2.1 安装包准备
- 方式1：从官网[下载地址](https://linkis.apache.org/zh-CN/download/main):https://linkis.apache.org/zh-CN/download/main，下载对应的安装包(项目安装包和管理台安装包)
-- 方式2：根据[Linkis 编译打包](../development/linkis_compile_and_package)和[前端管理台编译](../development/web_build) 自行编译出项目安装包和管理台安装包
+- 方式2：根据[Linkis 编译打包](../development/linkis-compile-and-package)和[前端管理台编译](../development/web-build) 自行编译出项目安装包和管理台安装包
上传安装包`apache-linkis-x.x.x-incubating-bin.tar.gz`后，进行解压安装包
@@ -387,7 +387,7 @@ wds.linkis.admin.user= #用户
wds.linkis.admin.password= #密码
```
-管理台使用指引见[使用手册](user_guide/console_manual.md)
+管理台使用指引见[使用手册](../user_guide/console-manual.md)
## 5. 验证基础功能
>根据实际需求，验证对应的引擎任务
@@ -411,13 +411,13 @@ sh bin/linkis-cli -submitUser hadoop -engineType python-python2 -codeType pyth
## 6 开发工具IDE（Scriptis）的安装(可选)
>安装Scripti工具后，可以支持在web页面在线写SQL、Pyspark、HiveQL等脚本
-详细指引见[工具Scriptis的安装部署](./linkis_scriptis_install)
+详细指引见[工具Scriptis的安装部署](./linkis-scriptis-install)
## 7. 支持的引擎
### 7.1 引擎适配列表
-请注意：Linkis的单独安装包默认只包含的：Python/Shell/Hive/Spark四个引擎，如果有其他的引擎(如jdbc/flink/sqoop等引擎)使用场景，可以手动安装，具体请参考 [EngineConnPlugin引擎插件安装文档](engine_conn_plugin_installation)。
+请注意：Linkis的单独安装包默认只包含的：Python/Shell/Hive/Spark四个引擎，如果有其他的引擎(如jdbc/flink/sqoop等引擎)使用场景，可以手动安装，具体请参考 [EngineConnPlugin引擎插件安装文档](engine-conn-plugin-installation)。
本版本已适配的支持引擎列表如下：
@@ -525,7 +525,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
查看引擎的物料记录是否存在(如果有更新,查看更新时间是否正确)。
-- 如果不存在或则未更新，先尝试手动刷新物料资源(详细见[引擎物料资源刷新](engine_conn_plugin_installation#23-引擎刷新))。
+- 如果不存在或则未更新，先尝试手动刷新物料资源(详细见[引擎物料资源刷新](engine-conn-plugin-installation#23-引擎刷新))。
- 通过`log/linkis-cg-engineplugin.log`日志，查看物料失败的具体原因，很多时候可能是hdfs目录没有权限导致
- 检查gateway地址配置是否正确`conf/linkis.properties`的配置项`wds.linkis.gateway.url`
@@ -622,7 +622,7 @@ CDH本身不是使用的官方标准的hive/spark包,进行适配时，最好修
### 8.9 Http接口的调试
-- 方式1 可以开启[免登陆模式指引](/docs/latest/api/login_api/#2免登录配置)
+- 方式1 可以开启[免登陆模式指引](/docs/latest/api/login-api/#2免登录配置)
- 方式2 postman中的，请求头带上登陆成功的cookie值
cookie值可以在浏览器端登陆成功后，获取
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/sourcecode_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/sourcecode_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/sourcecode-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/start_metadatasource.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/start-metadatasource.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/start_metadatasource.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/start-metadatasource.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/unpack_hierarchical_structure.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/unpack-hierarchical-structure.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/unpack_hierarchical_structure.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/unpack-hierarchical-structure.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/web_install.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/web-install.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/web_install.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/web-install.md
index 7518e9267b..a3a9dbbce2 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/web_install.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/deployment/web-install.md
@@ -5,7 +5,7 @@ sidebar_position: 6
> web端是使用nginx作为静态资源服务器的，访问请求流程是:`Linkis管理台请求->nginx ip:port->linkis-gateway ip:port-> 其他服务`
-Linkis 提供了单独的前端管理台功能，提供了展示历史任务的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick_deploy.md)
+Linkis 提供了单独的前端管理台功能，提供了展示历史任务的全局历史、修改用户参数、管理ECM和微服务等功能，部署前端管理台前需要先将Linkis后端进行部署，Linkis的部署手册见：[Linkis部署手册](deployment/quick-deploy.md)
## 1 准备工作
@@ -167,7 +167,7 @@ wds.linkis.admin.user= #用户
wds.linkis.admin.password= #密码
```
-管理台使用指引见[使用手册](user_guide/console_manual.md)
+管理台使用指引见[使用手册](../user_guide/console-manual.md)
## 4 注意事项
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis_compile_and_package.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis-compile-and-package.md
similarity index 99%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis_compile_and_package.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis-compile-and-package.md
index 6679eaf944..da0b786f7f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.1/development/linkis_compile_and_package.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis-compile-and-package.md
@@ -107,7 +107,7 @@ __编译环境要求：__ 必须 **JDK8** 以上，**Oracle/Sun** 和 **OpenJDK
#spark文件下就是编译好的引擎物料
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/out/spark
```
-如何单独安装 Spark 引擎？请参考 [Linkis 引擎插件安装文档](../deployment/engine_conn_plugin_installation)
+如何单独安装 Spark 引擎？请参考 [Linkis 引擎插件安装文档](../deployment/engine-conn-plugin-installation)
### 3.2 如何将非默认引擎打包至安装部署包中
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis_config.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis-config.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis_config.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis-config.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis_debug_in_mac.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis-debug-in-mac.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis_debug_in_mac.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis-debug-in-mac.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis_debug.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis-debug.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis_debug.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/linkis-debug.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/new_engine_conn.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/new-engine-conn.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/new_engine_conn.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/new-engine-conn.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/web_build.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/web-build.md
similarity index 97%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/web_build.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/web-build.md
index 231301ad11..7f971bcad5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/web_build.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/development/web-build.md
@@ -38,7 +38,7 @@ $ npm install
```
$ npm run build
```
-上述命令执行成功后，会生成前端管理台安装包 `apache-linkis-${version}-incubating-web-bin.tar.gz`，可以直接将该文件夹放进您的静态服务器中，或者参考[安装文档](../deployment/web_install.md)，使用脚本进行部署安装。
+上述命令执行成功后，会生成前端管理台安装包 `apache-linkis-${version}-incubating-web-bin.tar.gz`，可以直接将该文件夹放进您的静态服务器中，或者参考[安装文档](../deployment/web-install.md)，使用脚本进行部署安装。
## 3 . 注意事项
### 3.1 Windows下npm install 步骤报错
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/flink.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/flink.md
index 12979f32cf..cfd311edf9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/flink.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/flink.md
@@ -58,12 +58,12 @@ cd ${LINKIS_HOME}/sbin
sh linkis-daemon.sh restart cg-engineplugin
```
engineplugin更详细的介绍可以参看下面的文章。
-https://linkis.apache.org/zh-CN/docs/1.1.1/deployment/engine_conn_plugin_installation
+https://linkis.apache.org/zh-CN/docs/1.1.1/deployment/engine-conn-plugin-installation
### 2.3 Flink引擎的标签
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3.Flink引擎的使用
@@ -117,7 +117,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
sh ./bin/linkis-cli -engineType flink-1.12.2 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 OnceEngineConn方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/hive.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/hive.md
index 47116ad53a..277c76d7a4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/hive.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/hive.md
@@ -35,13 +35,13 @@ on Tez，需要您按照此pr进行一下修改。
如果您已经编译完了您的hive引擎的插件已经编译完成，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 hive引擎的标签
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.hive引擎的使用
@@ -57,7 +57,7 @@ hive的MapReduce任务是需要用到yarn的资源，所以需要您在一开始
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Hive任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -73,7 +73,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType hive-2.3.3 -codeType hql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/jdbc.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/jdbc.md
index fcd68a8f81..ef28f4d89f 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/jdbc.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/jdbc.md
@@ -44,7 +44,7 @@ sh linkis-daemon.sh restart cg-engineplugin
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3.JDBC引擎的使用
@@ -91,7 +91,7 @@ http 请求参数示例
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于JDBC任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -107,7 +107,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/openlookeng.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/openlookeng.md
index de4bb7a6a6..0ae5796613 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/openlookeng.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/openlookeng.md
@@ -47,7 +47,7 @@ sh linkis-daemon.sh restart cg-engineplugin
Linkis1.X是通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 3 引擎的使用
@@ -84,7 +84,7 @@ http 请求参数示例
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于openlookeng任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -100,5 +100,5 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType openlookeng-1.5.0 -codeType sql -code 'show databases;' -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/pipeline.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/pipeline.md
index 3bc6be11c1..5ea16b1ef9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/pipeline.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/pipeline.md
@@ -55,7 +55,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
通过标签来进行的，所以需要在我们数据库中插入数据，插入的方式如下文所示
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
## 2 引擎的使用
@@ -73,7 +73,7 @@ sh bin/linkis-cli -submitUser hadoop -engineType pipeline-1 -codeType pipelin
```
`from hdfs:///000/000/000/A.dolphin to file:///000/000/000/B.csv` 该内容 2.3 有解释
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/python.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/python.md
index eaba419773..ec656620bb 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/python.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/python.md
@@ -34,7 +34,7 @@ python3的，您可以简单更改配置就可以完成Python版本的切换，
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Python任务您只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -50,7 +50,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/shell.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/shell.md
index d40e903ad7..6a509306ac 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/shell.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/shell.md
@@ -37,7 +37,7 @@ Shell引擎不需要用户自行编译，直接使用编译好的shell引擎插
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Shell任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -53,7 +53,7 @@ Linkis 1.0后提供了cli的方式提交任务，我们只需要指定对应的E
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/spark.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/spark.md
index 780a4cbe8e..b4d9aa732a 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/spark.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/spark.md
@@ -33,13 +33,13 @@ sidebar_position: 1
如果您已经编译完了您的spark引擎的插件，那么您需要将新的插件放置到指定的位置中才能加载，具体可以参考下面这篇文章
-[EngineConnPlugin引擎插件安装](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装](../deployment/engine-conn-plugin-installation)
### 2.3 spark引擎的标签
Linkis1.X是通过标签配置来区分引擎版本的，所以需要我们在数据库中插入数据，插入的方式如下文所示。
-[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin引擎插件安装 > 2.2 管理台Configuration配置修改（可选）](../deployment/engine-conn-plugin-installation)
## 3.spark引擎的使用
@@ -54,7 +54,7 @@ Linkis1.X是通过标签配置来区分引擎版本的，所以需要我们在
### 3.1 通过Linkis SDK进行使用
-Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis提供了Java和Scala 的SDK向Linkis服务端提交任务. 具体可以参考 [JAVA SDK Manual](../user_guide/sdk-manual.md).
对于Spark任务你只需要修改Demo中的EngineConnType和CodeType参数即可:
```java
@@ -76,7 +76,7 @@ sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -confMap wds.linkis.yarnqueue=dws -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-具体使用可以参考： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+具体使用可以参考： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 Scriptis的使用方式
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/sqoop.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/sqoop.md
index 97258268aa..8e52c0f7d8 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/sqoop.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/engine_usage/sqoop.md
@@ -72,7 +72,7 @@ sh linkis-daemon.sh restart cg-engineplugin
```
engineplugin更详细的介绍可以参看下面的文章。
-https://linkis.apache.org/zh-CN/docs/latest/deployment/engine_conn_plugin_installation
+https://linkis.apache.org/zh-CN/docs/latest/deployment/engine-conn-plugin-installation
## 3 Sqoop引擎的使用
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/introduction.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/introduction.md
index 2260bb8504..98867e7620 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/introduction.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/introduction.md
@@ -50,7 +50,7 @@ Linkis 自2019年开源发布以来，已累计积累了700多家试验企业和
## 安装部署
-请参考[安装部署文档](deployment/quick_deploy.md) 来部署Linkis
+请参考[安装部署文档](deployment/quick-deploy.md) 来部署Linkis
## 示例和使用指引
- [用户手册](user_guide/overview.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/release.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/release.md
index a7a40a71e6..eccc2c00e8 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/release.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/release.md
@@ -2,10 +2,10 @@
title: 版本总览
sidebar_position: 0.1
---
-- [无HDFS模式的精简化部署指引](/deployment/deploy_linkis_without_hdfs.md)
+- [无HDFS模式的精简化部署指引](/deployment/deploy-linkis-without-hdfs.md)
- [Sqoop引擎的使用](/engine_usage/sqoop.md)
- [历史任务查询HTTP接口](/api/http/linkis-ps-publicservice-api/jobhistory-api.md)
-- [工具Scriptis的安装部署](/deployment/linkis_scriptis_install.md)
+- [工具Scriptis的安装部署](/deployment/linkis-scriptis-install.md)
- [版本的release-notes](/download/release-notes-1.1.2)
## 参数变化
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/tuning_and_troubleshooting/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/tuning_and_troubleshooting/overview.md
index 337501e74f..3c575cfb57 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/tuning_and_troubleshooting/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/tuning_and_troubleshooting/overview.md
@@ -111,6 +111,6 @@ sidebar_position: 0
### 六、定位源码远程debug
-通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode_hierarchical_structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis_debug.md) 》一文调试对应微服务下的代码。
+通常情况下，对源码远程debug是定位问题最有效的方式，但相对查阅文档来说，需要用户对源码结构有一定的了解，这里建议您在远程debug前查阅Linkis WIKI中的《 [Linkis源码层级结构详解](deployment/sourcecode-hierarchical-structure.md) 》,对项目的源码结构进行初步的了解，有一定程度上的熟悉之后，可以参考WIKI中的《 [如何DebugLinkis](development/linkis-debug.md) 》一文调试对应微服务下的代码。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade_from_0.X_to_1.0_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 97%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
index 55d8b3aa8a..1c3986b77d 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.0/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 1
## 1. 注意事项
-**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference_between_1.0_and_0.x.md)**。
+**如果您是首次接触并使用Linkis，您可以忽略该章节；如果您已经是 Linkis 的使用用户，安装或升级前建议先阅读：[Linkis1.0 与 Linkis0.X 的区别简述](architecture/difference-between-1.0-and-0.x.md)**。
## 2. 服务升级安装
@@ -15,7 +15,7 @@ sidebar_position: 1
在安装时如果需要保留0.X的数据，一定要选择1跳过建表语句（见下面代码）。
-Linkis1.0 的安装可以参考[如何快速安装](deployment/quick_deploy.md)
+Linkis1.0 的安装可以参考[如何快速安装](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ Please input the choice: ## choice 1
## 4. 安装Linkis1.0
- 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装](deployment/quick_deploy.md)
+ 启动Linkis1.0，验证服务是否已正常启动并对外提供服务，具体请参考： [如何快速安装](deployment/quick-deploy.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade_guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade-guide.md
similarity index 98%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade_guide.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade-guide.md
index 978d8a581a..a79c3ba2be 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/upgrade/upgrade_guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/upgrade/upgrade-guide.md
@@ -18,7 +18,7 @@ sidebar_position: 2
## 2 服务升级安装
-按[部署指引文档](../deployment/quick_deploy)（文档中关于管理台的安装可以跳过），进行新版本的安装。
+按[部署指引文档](../deployment/quick-deploy)（文档中关于管理台的安装可以跳过），进行新版本的安装。
安装服务时，如果历史数据保留，请保留历史数据，如果无需保留数据，直接重装即可，也无需关注升级流程
```shell script
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/console_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/console-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/console_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/console-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how_to_use.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/how-to-use.md
similarity index 94%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how_to_use.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/how-to-use.md
index bc3e1af344..9627ebc2b5 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.0.2/user_guide/how_to_use.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/how-to-use.md
@@ -7,9 +7,9 @@ sidebar_position: 1
## 1. Client端使用
如果需要在Linkis的基础上，接入其它应用，需要针对Linkis提供的接口进行开发，Linkis提供了多种客户端接入接口，更详细的使用介绍可以参考以下内容：
-- [**Restful API使用方式**](api/linkis_task_operator.md)
-- [**JDBC API使用方式**](api/jdbc_api.md)
-- [**Java SDK使用方式**](user_guide/sdk_manual.md)
+- [**Restful API使用方式**](api/linkis-task-operator.md)
+- [**JDBC API使用方式**](api/jdbc-api.md)
+- [**Java SDK使用方式**](../user_guide/sdk-manual.md)
## 2. Scriptis使用Linkis
如果需要使用Linkis完成交互式在线分析处理的工作，并且不需要诸如工作流开发、工作流调度、数据服务等数据分析应用工具，可以单独安装[**Scriptis**](https://github.com/WeBankFinTech/Scriptis)，详细安装教程可参考其对应的安装部署文档。
### 2.1. 使用Scriptis执行脚本
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/how_to_use.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/how_to_use.md
deleted file mode 100644
index bc3e1af344..0000000000
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/how_to_use.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: 如何使用 Linkis1.0
-sidebar_position: 1
----
-
- Linkis为了满足不同的使用场景需求，提供多种使用和接入方式，概括为三类，分别是Client端使用、Scriptis端使用、DataSphere Studio端使用，其中Scriptis和DataSphere Studio是微众银行大数据平台室开源的数据分析平台，由于这两个项目本质上完全兼容Linkis，所以通过Scriptis和DataSphere Studio使用Linkis最为简单。
-## 1. Client端使用
-
- 如果需要在Linkis的基础上，接入其它应用，需要针对Linkis提供的接口进行开发，Linkis提供了多种客户端接入接口，更详细的使用介绍可以参考以下内容：
-- [**Restful API使用方式**](api/linkis_task_operator.md)
-- [**JDBC API使用方式**](api/jdbc_api.md)
-- [**Java SDK使用方式**](user_guide/sdk_manual.md)
-## 2. Scriptis使用Linkis
- 如果需要使用Linkis完成交互式在线分析处理的工作，并且不需要诸如工作流开发、工作流调度、数据服务等数据分析应用工具，可以单独安装[**Scriptis**](https://github.com/WeBankFinTech/Scriptis)，详细安装教程可参考其对应的安装部署文档。
-### 2.1. 使用Scriptis执行脚本
- 目前Scriptis支持向Linkis提交多种任务类型，包括Spark SQL、Hive SQL、Scala、PythonSpark等，为了满足数据分析的需求，Scriptis左侧，提供查看用户工作空间信息、用户数据库和表信息、用户自定义函数，以及HDFS目录，同时支持上传下载，结果集导出等功能。Scriptis使用Linkis十分简单，可以很方便的在编辑栏书写脚本，提交到Linkis运行。
-
-### 2.2. Scriptis管理台
- Linkis提供资源配置和管理的接口，如果希望对任务资源进行配置管理，可以在Scriptis的管理台界面进行设置，包括队列设置、资源配置、引擎实例个数等。通过管理台，可以很方便的配置向Linkis提交任务的资源，使得更加方便快捷。
-
-
-## 3. DataSphere Studio使用Linkis
- [**DataSphere Studio**](https://github.com/WeBankFinTech/DataSphereStudio)简称DSS，是微众银行大数据平台开源的一站式数据分析处理平台，DSS交互式分析模块集成了Scriptis，使用DSS进行交互式分析和Scriptis一样，除了提供Scriptis的基本功能外，DSS提供和集成了更加丰富和强大的数据分析功能，包括用于数据提取的数据服务、开发报表的工作流、可视化分析软件Visualis等。由于原生的支持，目前DSS是与Linkis集成度最高的软件，如果希望使用完整的Linkis功能，建议使用DSS搭配Linkis一起使用。
-
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/linkiscli_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/linkiscli-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/linkiscli_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/linkiscli-manual.md
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/overview.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/overview.md
index 6f53e8b095..bf7a2e26d6 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/overview.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis在设计之初就考虑接入方式的拓展性问题，针对不同的接入场景，Linkis提供了前端接入和SDK接入的方式，在前端接口上又提供了HTTP和WebSocket两种方式，如果对接入并使用Linkis感兴趣，可以参考以下文档：
-- [如何使用Links](how_to_use.md)
-- [Linkis-Cli的使用](linkiscli_manual.md)
-- [Linkis JAVA SDK的使用](sdk_manual.md)
-- [Linkis管理台的使用](console_manual.md)
+- [如何使用Links](how-to-use.md)
+- [Linkis-Cli的使用](linkiscli-manual.md)
+- [Linkis JAVA SDK的使用](sdk-manual.md)
+- [Linkis管理台的使用](console-manual.md)
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/sdk_manual.md b/i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/sdk-manual.md
similarity index 100%
rename from i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/sdk_manual.md
rename to i18n/zh-CN/docusaurus-plugin-content-docs/version-1.1.2/user_guide/sdk-manual.md
diff --git a/src/pages/home/index.js b/src/pages/home/index.js
index be9378d589..77dc6f34dc 100644
--- a/src/pages/home/index.js
+++ b/src/pages/home/index.js
@@ -20,10 +20,10 @@ export default function() {
<p className="home-desc">{dataSource.home.banner.slogan}</p>
<div className="botton-row center">
{
- language === 'en' && <a href="/docs/latest/deployment/quick_deploy" className="corner-botton blue-fill">{dataSource.common.getStart}</a>
+ language === 'en' && <a href="/docs/latest/deployment/quick-deploy" className="corner-botton blue-fill">{dataSource.common.getStart}</a>
}
{
- language === 'zh-CN' &&<a href="/zh-CN/docs/latest/deployment/quick_deploy" className="corner-botton blue-fill">{dataSource.common.getStart}</a>
+ language === 'zh-CN' &&<a href="/zh-CN/docs/latest/deployment/quick-deploy" className="corner-botton blue-fill">{dataSource.common.getStart}</a>
}
<a href={systemConfiguration.github.projectUrl} target="_blank" className="corner-botton blue">
<img className="button-icon" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABwAAAAcCAYAAAByDd+UAAAAAXNSR0IArs4c6QAAAERlWElmTU0AKgAAAAgAAYdpAAQAAAABAAAAGgAAAAAAA6ABAAMAAAABAAEAAKACAAQAAAABAAAAHKADAAQAAAABAAAAHAAAAABkvfSiAAAE2klEQVRIDa1WSyykWRQ+qrwf8YzQ3iTKWyrxmoWoWJHMoqIRKWErs7AYk1jIWDS9YCdshQWxQMsIYUE6Wm1qiJAIimjSqPaI8hrEu+Z8d9xKVak2mDnJrfvXueee79zzuteFXkApKSlqNzc3rYuLSz6PCN7y7nHbd4vFYrq/v9fz+GN5eXn+39S5PCeQmppaykAfGUT1nJxcY9BVHr8vLS0NSp7j7BQwIyMjjgX7FApFHoM57nn2P5+Y7u7 [...]
diff --git a/versioned_docs/version-0.11.0/api/login_api.md b/versioned_docs/version-0.11.0/api/login-api.md
similarity index 100%
rename from versioned_docs/version-0.11.0/api/login_api.md
rename to versioned_docs/version-0.11.0/api/login-api.md
diff --git a/versioned_docs/version-0.11.0/api/rest_api.md b/versioned_docs/version-0.11.0/api/rest-api.md
similarity index 100%
rename from versioned_docs/version-0.11.0/api/rest_api.md
rename to versioned_docs/version-0.11.0/api/rest-api.md
diff --git a/versioned_docs/version-0.11.0/api/web_socket.md b/versioned_docs/version-0.11.0/api/web-socket.md
similarity index 100%
rename from versioned_docs/version-0.11.0/api/web_socket.md
rename to versioned_docs/version-0.11.0/api/web-socket.md
diff --git a/versioned_docs/version-0.11.0/architecture/commons/real-time_log_push.md b/versioned_docs/version-0.11.0/architecture/commons/real-time-log-push.md
similarity index 100%
rename from versioned_docs/version-0.11.0/architecture/commons/real-time_log_push.md
rename to versioned_docs/version-0.11.0/architecture/commons/real-time-log-push.md
diff --git a/versioned_docs/version-0.11.0/architecture/overview.md b/versioned_docs/version-0.11.0/architecture/overview.md
index 86518e518f..8249717b4b 100644
--- a/versioned_docs/version-0.11.0/architecture/overview.md
+++ b/versioned_docs/version-0.11.0/architecture/overview.md
@@ -35,7 +35,7 @@ Each microservice cluster bears part of the system's functional responsibilities
**Supported scripting languages are**: SparkSQL, Spark Scala, Pyspark, R, Python, HQL and Shell, etc.;
- For more information about unified job execution services, please check [UJES Architecture Design Document](ujes/ujes_design.md)
+ For more information about unified job execution services, please check [UJES Architecture Design Document](ujes/ujes-design.md)
-**Resource Management Service**: Support real-time management and control of the resource usage of each system and user, limit the resource usage and concurrency of the system and users, and provide real-time resource dynamic charts to facilitate viewing and managing the system and users resource;
@@ -134,4 +134,4 @@ Now let's introduce how the user submits a SQL in the upper system, and how Link
12. Once the SQL execution is successful, Engine actively pushes the result set to Entrance, and Entrance informs the front end to get the result.
-For the design plan under abnormal Entrance/EngineManager/Engine, please refer to [UJES Architecture Design Document](ujes/ujes_design.md)
\ No newline at end of file
+For the design plan under abnormal Entrance/EngineManager/Engine, please refer to [UJES Architecture Design Document](ujes/ujes-design.md)
\ No newline at end of file
diff --git a/versioned_docs/version-0.11.0/architecture/storage/file_system.md b/versioned_docs/version-0.11.0/architecture/storage/file-system.md
similarity index 100%
rename from versioned_docs/version-0.11.0/architecture/storage/file_system.md
rename to versioned_docs/version-0.11.0/architecture/storage/file-system.md
diff --git a/versioned_docs/version-0.11.0/architecture/storage/remote_file_system_architecture_design.md b/versioned_docs/version-0.11.0/architecture/storage/remote-file-system-architecture-design.md
similarity index 98%
rename from versioned_docs/version-0.11.0/architecture/storage/remote_file_system_architecture_design.md
rename to versioned_docs/version-0.11.0/architecture/storage/remote-file-system-architecture-design.md
index 37483743bd..cb557ac9f4 100644
--- a/versioned_docs/version-0.11.0/architecture/storage/remote_file_system_architecture_design.md
+++ b/versioned_docs/version-0.11.0/architecture/storage/remote-file-system-architecture-design.md
@@ -19,7 +19,7 @@ How do you avoid creating Linux users so you can access the relevant files of th
## 2 Ideas
-By launching the engine manager (IO-Engineer) of the filesystem on the remote server ([what is EngineManager?](/architecture/ujes/ujes_design.md)) and providing a compatible client API, allowing users access to remote file systems.
+By launching the engine manager (IO-Engineer) of the filesystem on the remote server ([what is EngineManager?](/architecture/ujes/ujes-design.md)) and providing a compatible client API, allowing users access to remote file systems.
The entire architecture is shown below in graph：
diff --git a/versioned_docs/version-0.11.0/architecture/storage/resultset_file.md b/versioned_docs/version-0.11.0/architecture/storage/resultset-file.md
similarity index 100%
rename from versioned_docs/version-0.11.0/architecture/storage/resultset_file.md
rename to versioned_docs/version-0.11.0/architecture/storage/resultset-file.md
diff --git a/versioned_docs/version-0.11.0/architecture/ujes/asynchronous_thread_pool.md b/versioned_docs/version-0.11.0/architecture/ujes/asynchronous-thread-pool.md
similarity index 100%
rename from versioned_docs/version-0.11.0/architecture/ujes/asynchronous_thread_pool.md
rename to versioned_docs/version-0.11.0/architecture/ujes/asynchronous-thread-pool.md
diff --git a/versioned_docs/version-0.11.0/architecture/ujes/file_import_and_export_structure.md b/versioned_docs/version-0.11.0/architecture/ujes/file-import-and-export-structure.md
similarity index 100%
rename from versioned_docs/version-0.11.0/architecture/ujes/file_import_and_export_structure.md
rename to versioned_docs/version-0.11.0/architecture/ujes/file-import-and-export-structure.md
diff --git a/versioned_docs/version-0.11.0/architecture/ujes/ujes_design.md b/versioned_docs/version-0.11.0/architecture/ujes/ujes-design.md
similarity index 99%
rename from versioned_docs/version-0.11.0/architecture/ujes/ujes_design.md
rename to versioned_docs/version-0.11.0/architecture/ujes/ujes-design.md
index e0a37099db..0c6da661af 100644
--- a/versioned_docs/version-0.11.0/architecture/ujes/ujes_design.md
+++ b/versioned_docs/version-0.11.0/architecture/ujes/ujes-design.md
@@ -219,6 +219,6 @@ In particular, the interaction between Entrance and Engineering.Entrance sends u
### 5.1 Traditional modes of deployment
-Please view the[rapid deployment document](deployment/quick_deploy.md).
+Please view the[rapid deployment document](deployment/quick-deploy.md).
diff --git a/versioned_docs/version-0.11.0/deployment/engine_conn_plugin_installation.md b/versioned_docs/version-0.11.0/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from versioned_docs/version-0.11.0/deployment/engine_conn_plugin_installation.md
rename to versioned_docs/version-0.11.0/deployment/engine-conn-plugin-installation.md
diff --git a/versioned_docs/version-0.11.0/deployment/production_deployment _guide.md b/versioned_docs/version-0.11.0/deployment/production-deployment -guide.md
similarity index 100%
rename from versioned_docs/version-0.11.0/deployment/production_deployment _guide.md
rename to versioned_docs/version-0.11.0/deployment/production-deployment -guide.md
diff --git a/versioned_docs/version-0.11.0/deployment/quick_deploy.md b/versioned_docs/version-0.11.0/deployment/quick-deploy.md
similarity index 99%
rename from versioned_docs/version-0.11.0/deployment/quick_deploy.md
rename to versioned_docs/version-0.11.0/deployment/quick-deploy.md
index 4d2a9d1c9c..12bd1e28d9 100644
--- a/versioned_docs/version-0.11.0/deployment/quick_deploy.md
+++ b/versioned_docs/version-0.11.0/deployment/quick-deploy.md
@@ -2,7 +2,7 @@
title: Quick Deployment
sidebar_position: 1
---
-#### Reminder: If you want to experience LINKIS Family Bucket: DSS + Linkis + Qualitis + Visualis + Azkaban, please visit [DSS One-Key Deployment](https://github.com/WeBankFinTech/DataSphereStudio/blob/master/docs/zh_CN/ch2/DSS_LINKIS_Quick_Install.md)
+#### Reminder: If you want to experience LINKIS Family Bucket: DSS + Linkis + Qualitis + Visualis + Azkaban, please visit [DSS One-Key Deployment](https://github.com/WeBankFinTech/DataSphereStudio/blob/master/docs/zh_CN/ch2/DSS-LINKIS-Quick-Install.md)
## 1 Determine the installation environment
diff --git a/versioned_docs/version-0.11.0/deployment/quick_start.md b/versioned_docs/version-0.11.0/deployment/quick-start.md
similarity index 92%
rename from versioned_docs/version-0.11.0/deployment/quick_start.md
rename to versioned_docs/version-0.11.0/deployment/quick-start.md
index aeca382b9d..ecfeb370a6 100644
--- a/versioned_docs/version-0.11.0/deployment/quick_start.md
+++ b/versioned_docs/version-0.11.0/deployment/quick-start.md
@@ -27,4 +27,4 @@ As shown in the figure below, if the following microservices appear on your Eure
## 3 Quick Use Linkis
-Please refer to[to quickly use Linkis](quick_deploy#5-快速使用linkis)
\ No newline at end of file
+Please refer to[to quickly use Linkis](quick-deploy#5-快速使用linkis)
\ No newline at end of file
diff --git a/versioned_docs/version-0.11.0/deployment/sourcecode_hierarchical_structure.md b/versioned_docs/version-0.11.0/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-0.11.0/deployment/sourcecode_hierarchical_structure.md
rename to versioned_docs/version-0.11.0/deployment/sourcecode-hierarchical-structure.md
diff --git a/versioned_docs/version-0.11.0/development/compile_and_package.md b/versioned_docs/version-0.11.0/development/compile-and-package.md
similarity index 100%
rename from versioned_docs/version-0.11.0/development/compile_and_package.md
rename to versioned_docs/version-0.11.0/development/compile-and-package.md
diff --git a/versioned_docs/version-0.11.0/development/new_engine_conn.md b/versioned_docs/version-0.11.0/development/new-engine-conn.md
similarity index 100%
rename from versioned_docs/version-0.11.0/development/new_engine_conn.md
rename to versioned_docs/version-0.11.0/development/new-engine-conn.md
diff --git a/versioned_docs/version-0.11.0/engine_usage/python.md b/versioned_docs/version-0.11.0/engine_usage/python.md
index 706c462def..548611ef27 100644
--- a/versioned_docs/version-0.11.0/engine_usage/python.md
+++ b/versioned_docs/version-0.11.0/engine_usage/python.md
@@ -71,7 +71,7 @@ Figure 3 Spark running effect Figure 2
## 2 Implementation of Python engine
- The implementation of the Linkis-Python execution engine is based on [How to implement a new engine](/development/new_engine_conn.md) to implement the Entrance, EngineManager and Engine three The necessary interface of the module.
+ The implementation of the Linkis-Python execution engine is based on [How to implement a new engine](/development/new-engine-conn.md) to implement the Entrance, EngineManager and Engine three The necessary interface of the module.
The implementation of the execution module uses the py4j framework to allow the python executor to interact with the JVM. After the user submits the code, the JVM submits the code to the py4j framework The python interpreter executes and gets the output or error message from the python process.
diff --git a/versioned_docs/version-0.11.0/engine_usage/spark.md b/versioned_docs/version-0.11.0/engine_usage/spark.md
index 14638c6c6e..0d43018ab1 100644
--- a/versioned_docs/version-0.11.0/engine_usage/spark.md
+++ b/versioned_docs/version-0.11.0/engine_usage/spark.md
@@ -84,7 +84,7 @@ Figure 4 Spark running effect Figure 3
## 2 How the Spark engine is implemented
- The implementation of the Linkis-Python execution engine is based on [How to implement a new engine](/development/new_engine_conn.md) to implement the Entrance, EngineManager and Engine three The necessary interface of the module.
+ The implementation of the Linkis-Python execution engine is based on [How to implement a new engine](/development/new-engine-conn.md) to implement the Entrance, EngineManager and Engine three The necessary interface of the module.
In the EngineManager module, we chose to use the spark-submit command to start the java process, so Linkis took the rewrite of ProcessEngineBuilder's build method to configure the spark The startup parameters of is integrated with the spark-submit command to form a command to start the spark engine, and then the command is executed.
diff --git a/versioned_docs/version-0.11.0/upgrade/upgrade_from_0.9.0_to_0.9.1_guide.md b/versioned_docs/version-0.11.0/upgrade/upgrade-from-0.9.0-to-0.9.1-guide.md
similarity index 100%
rename from versioned_docs/version-0.11.0/upgrade/upgrade_from_0.9.0_to_0.9.1_guide.md
rename to versioned_docs/version-0.11.0/upgrade/upgrade-from-0.9.0-to-0.9.1-guide.md
diff --git a/versioned_docs/version-0.11.0/user_guide/0.X_sdk_manual.md b/versioned_docs/version-0.11.0/user_guide/0.X-sdk-manual.md
similarity index 100%
rename from versioned_docs/version-0.11.0/user_guide/0.X_sdk_manual.md
rename to versioned_docs/version-0.11.0/user_guide/0.X-sdk-manual.md
diff --git a/versioned_docs/version-0.11.0/user_guide/1.0_sdk_manual.md b/versioned_docs/version-0.11.0/user_guide/1.0-sdk-manual.md
similarity index 100%
rename from versioned_docs/version-0.11.0/user_guide/1.0_sdk_manual.md
rename to versioned_docs/version-0.11.0/user_guide/1.0-sdk-manual.md
diff --git a/versioned_docs/version-1.0.2/api/jdbc_api.md b/versioned_docs/version-1.0.2/api/jdbc-api.md
similarity index 100%
rename from versioned_docs/version-1.0.2/api/jdbc_api.md
rename to versioned_docs/version-1.0.2/api/jdbc-api.md
diff --git a/versioned_docs/version-1.0.2/api/linkis_task_operator.md b/versioned_docs/version-1.0.2/api/linkis-task-operator.md
similarity index 100%
rename from versioned_docs/version-1.0.2/api/linkis_task_operator.md
rename to versioned_docs/version-1.0.2/api/linkis-task-operator.md
diff --git a/versioned_docs/version-1.0.2/api/login_api.md b/versioned_docs/version-1.0.2/api/login-api.md
similarity index 100%
rename from versioned_docs/version-1.0.2/api/login_api.md
rename to versioned_docs/version-1.0.2/api/login-api.md
diff --git a/versioned_docs/version-1.0.2/api/overview.md b/versioned_docs/version-1.0.2/api/overview.md
index 60a92418bb..3f08075bde 100644
--- a/versioned_docs/version-1.0.2/api/overview.md
+++ b/versioned_docs/version-1.0.2/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 0
## 1. Document description
Linkis1.0 has been refactored and optimized on the basis of Linkix0.x, and it is also compatible with the 0.x interface. However, in order to prevent compatibility problems when using version 1.0, you need to read the following documents carefully:
-1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login_api.md) carefully.
+1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login-api.md) carefully.
-2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc_api.md).
+2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc-api.md).
-3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis_task_operator.md).
\ No newline at end of file
+3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis-task-operator.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.0.2/architecture/add_an_engine_conn.md b/versioned_docs/version-1.0.2/architecture/add-an-engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/add_an_engine_conn.md
rename to versioned_docs/version-1.0.2/architecture/add-an-engine-conn.md
diff --git a/versioned_docs/version-1.0.2/architecture/commons/message_scheduler.md b/versioned_docs/version-1.0.2/architecture/commons/message-scheduler.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/commons/message_scheduler.md
rename to versioned_docs/version-1.0.2/architecture/commons/message-scheduler.md
diff --git a/versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn_manager.md b/versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn_plugin.md b/versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn.md b/versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine_conn.md
rename to versioned_docs/version-1.0.2/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/app_manager.md b/versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/label_manager.md b/versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/resource_manager.md b/versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to versioned_docs/version-1.0.2/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/versioned_docs/version-1.0.2/architecture/computation_governance_services/overview.md b/versioned_docs/version-1.0.2/architecture/computation_governance_services/overview.md
index b40026117d..2327c25b23 100644
--- a/versioned_docs/version-1.0.2/architecture/computation_governance_services/overview.md
+++ b/versioned_docs/version-1.0.2/architecture/computation_governance_services/overview.md
@@ -44,8 +44,8 @@ Perform three stages to fully upgrade Linkis's Job execution architecture, as sh
[Enter LinkisManager Architecture Design](linkis_manager/overview.md)
### 4. Engine Manager
Engine conn Manager (ECM) is a simplified and upgraded version of linkis0. X engine manager. The ECM under linkis1.0 removes the application ability of the engine, and the whole microservice is completely stateless. It will focus on supporting the startup and destruction of all kinds of enginecon.
-[Enter EngineConnManager Architecture Design](engine/engine_conn_manager.md)
+[Enter EngineConnManager Architecture Design](engine/engine-conn-manager.md)
### 5. EngineConn
EngineConn is an optimized and upgraded version of Linkis0.X Engine. It will provide EngineConn and Executor two modules. EngineConn is used to connect the underlying computing storage engine and provide a session session that connects the underlying computing storage engines; Executor is based on this Session session , Provide full-stack computing support for interactive computing, streaming computing, offline computing, and data storage.
- [Enter EngineConn Architecture Design](engine/engine_conn.md)
+ [Enter EngineConn Architecture Design](engine/engine-conn.md)
\ No newline at end of file
diff --git a/versioned_docs/version-1.0.2/architecture/difference_between_1.0_and_0.x.md b/versioned_docs/version-1.0.2/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/difference_between_1.0_and_0.x.md
rename to versioned_docs/version-1.0.2/architecture/difference-between-1.0-and-0.x.md
diff --git a/versioned_docs/version-1.0.2/architecture/job_submission_preparation_and_execution_process.md b/versioned_docs/version-1.0.2/architecture/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from versioned_docs/version-1.0.2/architecture/job_submission_preparation_and_execution_process.md
rename to versioned_docs/version-1.0.2/architecture/job-submission-preparation-and-execution-process.md
index 08e32acac8..a7449a3689 100644
--- a/versioned_docs/version-1.0.2/architecture/job_submission_preparation_and_execution_process.md
+++ b/versioned_docs/version-1.0.2/architecture/job-submission-preparation-and-execution-process.md
@@ -30,7 +30,7 @@ The submission phase is mainly the interaction of Client -> Linkis Gateway -> En
-1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](user_guide/how_to_use.md)):
+1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](../user_guide/how-to-use.md)):
```
POST /api/rest_j/v1/entrance/submit
```
@@ -62,7 +62,7 @@ If the user has a reusable EngineConn in LinkisManager, the EngineConn is direct
How to define a reusable EngineConn? It refers to those that can match all the label requirements of the computing task, and the EngineConn's own health status is Healthy (the load is low and the actual status is Idle). Then, all the EngineConn that meets the conditions are sorted and selected according to the rules, and finally the best one is locked.
-If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](add_an_engine_conn.md).
+If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](add-an-engine-conn.md).
#### 2.2 Orchestrate a computing task
diff --git a/versioned_docs/version-1.0.2/architecture/overview.md b/versioned_docs/version-1.0.2/architecture/overview.md
index 962fd3c7da..282cb9c4da 100644
--- a/versioned_docs/version-1.0.2/architecture/overview.md
+++ b/versioned_docs/version-1.0.2/architecture/overview.md
@@ -15,7 +15,7 @@ The specific responsibilities of each category are as follows:
The following is a directory listing of Linkis1.0 architecture documents:
-1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference_between_1.0_and_0.x.md).
+1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference-between-1.0-and-0.x.md).
2. Linkis1.0 public enhancement service related documents, please read [Public Enhancement Service](public_enhancement_services/overview.md).
3. Linkis1.0 microservice governance related documents, please read [Microservice Governance](microservice_governance_services/overview.md).
4. Linkis1.0 computing governance service related documents, please read [Computation Governance Service](computation_governance_services/overview.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_cache.md b/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_client.md b/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_client.md
rename to versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_listener.md b/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_persistence.md b/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_search.md b/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service_search.md
rename to versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service.md b/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context_service.md
rename to versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/overview.md b/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/overview.md
index 4fae9dfbab..d44f182f29 100644
--- a/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/overview.md
+++ b/versioned_docs/version-1.0.2/architecture/public_enhancement_services/context_service/overview.md
@@ -101,28 +101,28 @@ The runtime workflow is mainly used by Linkis.
### 1. Client
The entrance of external access to CS, Client module provides HA function;
-[Enter Client Architecture Design](context_service_client.md)
+[Enter Client Architecture Design](context-service-client.md)
### 2. Service Module
Provide a Restful interface to encapsulate and process CS requests submitted by the client;
-[Enter Service Architecture Design](context_service.md)
+[Enter Service Architecture Design](context-service.md)
### 3. ContextSearch
The context query module provides rich and powerful query capabilities for the client to find the key-value key-value pairs of the context;
-[Enter ContextSearch architecture design](context_service_search.md)
+[Enter ContextSearch architecture design](context-service-search.md)
### 4. Listener
The CS listener module provides synchronous and asynchronous event consumption capabilities, and has the ability to notify the Client in real time once the Zookeeper-like Key-Value is updated;
-[Enter Listener architecture design](context_service_listener.md)
+[Enter Listener architecture design](context-service-listener.md)
### 5. ContextCache
The context memory cache module provides the ability to quickly retrieve the context and the ability to monitor and clean up JVM memory usage;
-[Enter ContextCache architecture design](context_service_cache.md)
+[Enter ContextCache architecture design](context-service-cache.md)
### 6. HighAvailable
Provide CS high availability capability;
-[Enter HighAvailable architecture design](context_service_highavailable.md)
+[Enter HighAvailable architecture design](context-service-highavailable.md)
### 7. Persistence
The persistence function of CS;
-[Enter Persistence architecture design](context_service_persistence.md)
\ No newline at end of file
+[Enter Persistence architecture design](context-service-persistence.md)
\ No newline at end of file
diff --git a/versioned_docs/version-1.0.2/architecture/public_enhancement_services/public_service.md b/versioned_docs/version-1.0.2/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from versioned_docs/version-1.0.2/architecture/public_enhancement_services/public_service.md
rename to versioned_docs/version-1.0.2/architecture/public_enhancement_services/public-service.md
diff --git a/versioned_docs/version-1.0.2/deployment/cluster_deployment.md b/versioned_docs/version-1.0.2/deployment/cluster-deployment.md
similarity index 100%
rename from versioned_docs/version-1.0.2/deployment/cluster_deployment.md
rename to versioned_docs/version-1.0.2/deployment/cluster-deployment.md
diff --git a/versioned_docs/version-1.0.2/deployment/engine_conn_plugin_installation.md b/versioned_docs/version-1.0.2/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from versioned_docs/version-1.0.2/deployment/engine_conn_plugin_installation.md
rename to versioned_docs/version-1.0.2/deployment/engine-conn-plugin-installation.md
diff --git a/versioned_docs/version-1.0.2/deployment/installation_hierarchical_structure.md b/versioned_docs/version-1.0.2/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.0.2/deployment/installation_hierarchical_structure.md
rename to versioned_docs/version-1.0.2/deployment/installation-hierarchical-structure.md
diff --git a/versioned_docs/version-1.0.2/deployment/quick_deploy.md b/versioned_docs/version-1.0.2/deployment/quick-deploy.md
similarity index 99%
rename from versioned_docs/version-1.0.2/deployment/quick_deploy.md
rename to versioned_docs/version-1.0.2/deployment/quick-deploy.md
index 2f2ab71a9f..c88a67da73 100644
--- a/versioned_docs/version-1.0.2/deployment/quick_deploy.md
+++ b/versioned_docs/version-1.0.2/deployment/quick-deploy.md
@@ -5,7 +5,7 @@ sidebar_position: 1
## Notes
-If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md).
+If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md).
Please note: Apart from the four EngineConnPlugins included in the Linkis1.0 installation package by default: Python/Shell/Hive/Spark. You can manually install other types of engines such as JDBC depending on your own needs. For details, please refer to EngineConnPlugin installation documents.
diff --git a/versioned_docs/version-1.0.2/deployment/sourcecode_hierarchical_structure.md b/versioned_docs/version-1.0.2/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.0.2/deployment/sourcecode_hierarchical_structure.md
rename to versioned_docs/version-1.0.2/deployment/sourcecode-hierarchical-structure.md
diff --git a/versioned_docs/version-1.0.2/deployment/web_install.md b/versioned_docs/version-1.0.2/deployment/web-install.md
similarity index 99%
rename from versioned_docs/version-1.0.2/deployment/web_install.md
rename to versioned_docs/version-1.0.2/deployment/web-install.md
index 2faf3a3092..b31ddfeaef 100644
--- a/versioned_docs/version-1.0.2/deployment/web_install.md
+++ b/versioned_docs/version-1.0.2/deployment/web-install.md
@@ -3,7 +3,7 @@ title: Linkis Console Deployment
sidebar_position: 6
---
-Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linis's global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick_deploy.md)
+Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linis's global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick-deploy.md)
## 1. Preparation
diff --git a/versioned_docs/version-1.0.2/development/linkis_compile_and_package.md b/versioned_docs/version-1.0.2/development/linkis-compile-and-package.md
similarity index 98%
rename from versioned_docs/version-1.0.2/development/linkis_compile_and_package.md
rename to versioned_docs/version-1.0.2/development/linkis-compile-and-package.md
index 5b2d245a72..9710fb088e 100644
--- a/versioned_docs/version-1.0.2/development/linkis_compile_and_package.md
+++ b/versioned_docs/version-1.0.2/development/linkis-compile-and-package.md
@@ -92,7 +92,7 @@ Get the installation package, there will be a compiled package in the ->target d
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/linkis-engineplugin-spark-x.x.x.jar
```
-How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine_conn_plugin_installation)
+How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine-conn-plugin-installation)
## 5. How to modify the Hadoop, Hive, and Spark versions that Linkis depends on
diff --git a/versioned_docs/version-1.0.2/development/linkis_debug.md b/versioned_docs/version-1.0.2/development/linkis-debug.md
similarity index 100%
rename from versioned_docs/version-1.0.2/development/linkis_debug.md
rename to versioned_docs/version-1.0.2/development/linkis-debug.md
diff --git a/versioned_docs/version-1.0.2/development/new_engine_conn.md b/versioned_docs/version-1.0.2/development/new-engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.0.2/development/new_engine_conn.md
rename to versioned_docs/version-1.0.2/development/new-engine-conn.md
diff --git a/versioned_docs/version-1.0.2/development/web_build.md b/versioned_docs/version-1.0.2/development/web-build.md
similarity index 100%
rename from versioned_docs/version-1.0.2/development/web_build.md
rename to versioned_docs/version-1.0.2/development/web-build.md
diff --git a/versioned_docs/version-1.0.2/engine_usage/hive.md b/versioned_docs/version-1.0.2/engine_usage/hive.md
index f19ffb2077..6588faa885 100644
--- a/versioned_docs/version-1.0.2/engine_usage/hive.md
+++ b/versioned_docs/version-1.0.2/engine_usage/hive.md
@@ -33,13 +33,13 @@ Other hive operating modes are similar, just copy the corresponding dependencies
If you have already compiled your hive engineConn plug-in has been compiled, then you need to put the new plug-in in the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Linkis adds Hive console parameters(optional)
Linkis can configure the corresponding EngineConn parameters on the management console. If your newly added EngineConn needs this feature, you can refer to the following documents:
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of hive engineConn
@@ -55,7 +55,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -70,7 +70,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.0.2/engine_usage/jdbc.md b/versioned_docs/version-1.0.2/engine_usage/jdbc.md
index ed4372ebbb..e905362048 100644
--- a/versioned_docs/version-1.0.2/engine_usage/jdbc.md
+++ b/versioned_docs/version-1.0.2/engine_usage/jdbc.md
@@ -42,7 +42,7 @@ wds.linkis.jdbc.password
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -57,7 +57,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.0.2/engine_usage/python.md b/versioned_docs/version-1.0.2/engine_usage/python.md
index 1b46994e8b..b5bf8fbad7 100644
--- a/versioned_docs/version-1.0.2/engine_usage/python.md
+++ b/versioned_docs/version-1.0.2/engine_usage/python.md
@@ -38,7 +38,7 @@ Before submitting python on linkis, you only need to make sure that there is pyt
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -53,7 +53,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.0.2/engine_usage/shell.md b/versioned_docs/version-1.0.2/engine_usage/shell.md
index d99a4ca96e..3296981943 100644
--- a/versioned_docs/version-1.0.2/engine_usage/shell.md
+++ b/versioned_docs/version-1.0.2/engine_usage/shell.md
@@ -37,7 +37,7 @@ Before submitting the shell on linkis, you only need to ensure that there is the
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -52,7 +52,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.0.2/engine_usage/spark.md b/versioned_docs/version-1.0.2/engine_usage/spark.md
index 106ebce8f7..5bde17587c 100644
--- a/versioned_docs/version-1.0.2/engine_usage/spark.md
+++ b/versioned_docs/version-1.0.2/engine_usage/spark.md
@@ -34,13 +34,13 @@ In theory, Linkis1.0 supports all versions of spark2.x and above. Spark 2.4.3 is
If you have already compiled your spark EngineConn plug-in has been compiled, then you need to put the new plug-in to the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 tags of spark EngineConn
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of spark EngineConn
@@ -56,7 +56,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -72,7 +72,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
## codeType py-->pyspark sql-->sparkSQL scala-->Spark scala
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.0.2/introduction.md b/versioned_docs/version-1.0.2/introduction.md
index 58aeec8e03..81539f7b24 100644
--- a/versioned_docs/version-1.0.2/introduction.md
+++ b/versioned_docs/version-1.0.2/introduction.md
@@ -54,8 +54,8 @@ Since the first release of Linkis in 2019, it has accumulated more than **700**
Please go to the [Linkis releases page](https://github.com/apache/incubator-linkis/releases) to download a compiled distribution or a source code package of Linkis.
# Compile and deploy
-Please follow [Compile Guide](development/linkis_compile_and_package.md) to compile Linkis from source code.
-Please refer to [Deployment_Documents](deployment/quick_deploy.md) to do the deployment.
+Please follow [Compile Guide](development/linkis-compile-and-package.md) to compile Linkis from source code.
+Please refer to [Deployment_Documents](deployment/quick-deploy.md) to do the deployment.
# Examples and Guidance
You can find examples and guidance for how to use and manage Linkis in [User_Manual](user_guide/overview.md), [Engine_Usage_Documents](engine_usage/overview.md) and [API_Documents](../version-1.0.2/api/overview.md).
diff --git a/versioned_docs/version-1.0.2/tuning_and_troubleshooting/overview.md b/versioned_docs/version-1.0.2/tuning_and_troubleshooting/overview.md
index 1211422047..3d2ba065a5 100644
--- a/versioned_docs/version-1.0.2/tuning_and_troubleshooting/overview.md
+++ b/versioned_docs/version-1.0.2/tuning_and_troubleshooting/overview.md
@@ -100,4 +100,4 @@ For problems that cannot be resolved according to the above process positioning
### Ⅵ. locate the source code by remote debug
-Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode_hierarchical_structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
+Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode-hierarchical-structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
diff --git a/versioned_docs/version-1.0.2/upgrade/overview.md b/versioned_docs/version-1.0.2/upgrade/overview.md
index cb2cca3079..11a268a06e 100644
--- a/versioned_docs/version-1.0.2/upgrade/overview.md
+++ b/versioned_docs/version-1.0.2/upgrade/overview.md
@@ -8,4 +8,4 @@ The architecture of Linkis1.0 is very different from Linkis0.x, and there are so
1. If you are installing Linkis for the first time, or reinstalling Linkis, you do not need to pay attention to the Linkis Upgrade Guide.
-2. If you are upgrading from Linkis0.x to Linkis1.0, be sure to read the [Linkis Upgrade from 0.x to 1.0 guide](upgrade_from_0.X_to_1.0_guide.md) carefully.
+2. If you are upgrading from Linkis0.x to Linkis1.0, be sure to read the [Linkis Upgrade from 0.x to 1.0 guide](upgrade-from-0.X-to-1.0-guide.md) carefully.
diff --git a/versioned_docs/version-1.0.2/upgrade/upgrade_from_0.X_to_1.0_guide.md b/versioned_docs/version-1.0.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 95%
rename from versioned_docs/version-1.0.2/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to versioned_docs/version-1.0.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
index d030c2aca9..6c16652529 100644
--- a/versioned_docs/version-1.0.2/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/versioned_docs/version-1.0.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 3
## 1.Precautions
- **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md)**.
+ **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md)**.
## 2. Service upgrade installation
@@ -15,7 +15,7 @@ sidebar_position: 3
If you need to keep 0.X data during the upgrade, you must select 1 to skip the table building statement (see the code below).
- For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ source linkis_configuration_dml.sql
## 4. Installation and startup Linkis1.0
- Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
diff --git a/versioned_docs/version-1.0.2/user_guide/console_manual.md b/versioned_docs/version-1.0.2/user_guide/console-manual.md
similarity index 100%
rename from versioned_docs/version-1.0.2/user_guide/console_manual.md
rename to versioned_docs/version-1.0.2/user_guide/console-manual.md
diff --git a/versioned_docs/version-1.1.0/user_guide/how_to_use.md b/versioned_docs/version-1.0.2/user_guide/how-to-use.md
similarity index 94%
rename from versioned_docs/version-1.1.0/user_guide/how_to_use.md
rename to versioned_docs/version-1.0.2/user_guide/how-to-use.md
index a7654d58ce..8d84c4ec80 100644
--- a/versioned_docs/version-1.1.0/user_guide/how_to_use.md
+++ b/versioned_docs/version-1.0.2/user_guide/how-to-use.md
@@ -10,9 +10,9 @@ sidebar_position: 1
## 1. Client side usage
If you need to connect to other applications on the basis of Linkis, you need to develop the interface provided by Linkis. Linkis provides a variety of client access interfaces. For detailed usage introduction, please refer to the following:
-- [**Restful API Usage**](api/linkis_task_operator.md)
-- [**JDBC API Usage**](api/jdbc_api.md)
-- [**How to use Java SDK**](user_guide/sdk_manual.md)
+- [**Restful API Usage**](api/linkis-task-operator.md)
+- [**JDBC API Usage**](api/jdbc-api.md)
+- [**How to use Java SDK**](../user_guide/sdk-manual.md)
## 2. Scriptis uses Linkis
diff --git a/versioned_docs/version-1.0.2/user_guide/linkiscli_manual.md b/versioned_docs/version-1.0.2/user_guide/linkiscli-manual.md
similarity index 100%
rename from versioned_docs/version-1.0.2/user_guide/linkiscli_manual.md
rename to versioned_docs/version-1.0.2/user_guide/linkiscli-manual.md
diff --git a/versioned_docs/version-1.0.2/user_guide/overview.md b/versioned_docs/version-1.0.2/user_guide/overview.md
index 2a6d4b1b9b..3aa5f4450a 100644
--- a/versioned_docs/version-1.0.2/user_guide/overview.md
+++ b/versioned_docs/version-1.0.2/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis considered the scalability of the access method at the beginning of the design. For different access scenarios, Linkis provides front-end access and SDK access. HTTP and WebSocket interfaces are also provided on the basis of front-end interfaces. If you are interested in accessing and using Linkis, you can refer to the following documents:
-- [How to Use Links](how_to_use.md)
-- [Linkis Management Console Manual](console_manual.md)
-- [Linkis1.0 SDK Manual](sdk_manual.md)
-- [Linkis-Cli Manual](linkiscli_manual.md)
+- [How to Use Links](how-to-use.md)
+- [Linkis Management Console Manual](console-manual.md)
+- [Linkis1.0 SDK Manual](sdk-manual.md)
+- [Linkis-Cli Manual](linkiscli-manual.md)
diff --git a/versioned_docs/version-1.0.2/user_guide/sdk_manual.md b/versioned_docs/version-1.0.2/user_guide/sdk-manual.md
similarity index 100%
rename from versioned_docs/version-1.0.2/user_guide/sdk_manual.md
rename to versioned_docs/version-1.0.2/user_guide/sdk-manual.md
diff --git a/versioned_docs/version-1.0.3/api/jdbc_api.md b/versioned_docs/version-1.0.3/api/jdbc-api.md
similarity index 100%
rename from versioned_docs/version-1.0.3/api/jdbc_api.md
rename to versioned_docs/version-1.0.3/api/jdbc-api.md
diff --git a/versioned_docs/version-1.0.3/api/linkis_task_operator.md b/versioned_docs/version-1.0.3/api/linkis-task-operator.md
similarity index 100%
rename from versioned_docs/version-1.0.3/api/linkis_task_operator.md
rename to versioned_docs/version-1.0.3/api/linkis-task-operator.md
diff --git a/versioned_docs/version-1.0.3/api/login_api.md b/versioned_docs/version-1.0.3/api/login-api.md
similarity index 100%
rename from versioned_docs/version-1.0.3/api/login_api.md
rename to versioned_docs/version-1.0.3/api/login-api.md
diff --git a/versioned_docs/version-1.0.3/api/overview.md b/versioned_docs/version-1.0.3/api/overview.md
index 60a92418bb..3f08075bde 100644
--- a/versioned_docs/version-1.0.3/api/overview.md
+++ b/versioned_docs/version-1.0.3/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 0
## 1. Document description
Linkis1.0 has been refactored and optimized on the basis of Linkix0.x, and it is also compatible with the 0.x interface. However, in order to prevent compatibility problems when using version 1.0, you need to read the following documents carefully:
-1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login_api.md) carefully.
+1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login-api.md) carefully.
-2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc_api.md).
+2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc-api.md).
-3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis_task_operator.md).
\ No newline at end of file
+3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis-task-operator.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.0.3/architecture/add_an_engine_conn.md b/versioned_docs/version-1.0.3/architecture/add-an-engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/add_an_engine_conn.md
rename to versioned_docs/version-1.0.3/architecture/add-an-engine-conn.md
diff --git a/versioned_docs/version-1.0.3/architecture/commons/message_scheduler.md b/versioned_docs/version-1.0.3/architecture/commons/message-scheduler.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/commons/message_scheduler.md
rename to versioned_docs/version-1.0.3/architecture/commons/message-scheduler.md
diff --git a/versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn_manager.md b/versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn_plugin.md b/versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn.md b/versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine_conn.md
rename to versioned_docs/version-1.0.3/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/app_manager.md b/versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/label_manager.md b/versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/resource_manager.md b/versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to versioned_docs/version-1.0.3/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/versioned_docs/version-1.0.3/architecture/computation_governance_services/overview.md b/versioned_docs/version-1.0.3/architecture/computation_governance_services/overview.md
index 80c421ad74..9446468701 100644
--- a/versioned_docs/version-1.0.3/architecture/computation_governance_services/overview.md
+++ b/versioned_docs/version-1.0.3/architecture/computation_governance_services/overview.md
@@ -44,7 +44,7 @@ Perform three stages to fully upgrade Linkis's Job execution architecture, as sh
[Enter LinkisManager Architecture Design](linkis_manager/overview.md)
### 4. Engine Manager
Engine conn Manager (ECM) is a simplified and upgraded version of linkis0. X engine manager. The ECM under linkis1.0 removes the application ability of the engine, and the whole microservice is completely stateless. It will focus on supporting the startup and destruction of all kinds of enginecon.
-[Enter EngineConnManager Architecture Design](engine/engine_conn_manager.md)
+[Enter EngineConnManager Architecture Design](engine/engine-conn-manager.md)
### 5. EngineConn
EngineConn is an optimized and upgraded version of Linkis0.X Engine. It will provide EngineConn and Executor two modules. EngineConn is used to connect the underlying computing storage engine and provide a session session that connects the underlying computing storage engines; Executor is based on this Session session , Provide full-stack computing support for interactive computing, streaming computing, offline computing, and data storage.
- [Enter EngineConn Architecture Design](engine/engine_conn.md)
+ [Enter EngineConn Architecture Design](engine/engine-conn.md)
diff --git a/versioned_docs/version-1.0.3/architecture/difference_between_1.0_and_0.x.md b/versioned_docs/version-1.0.3/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/difference_between_1.0_and_0.x.md
rename to versioned_docs/version-1.0.3/architecture/difference-between-1.0-and-0.x.md
diff --git a/versioned_docs/version-1.1.0/architecture/job_submission_preparation_and_execution_process.md b/versioned_docs/version-1.0.3/architecture/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from versioned_docs/version-1.1.0/architecture/job_submission_preparation_and_execution_process.md
rename to versioned_docs/version-1.0.3/architecture/job-submission-preparation-and-execution-process.md
index dd6e8436c9..1d62458cc6 100644
--- a/versioned_docs/version-1.1.0/architecture/job_submission_preparation_and_execution_process.md
+++ b/versioned_docs/version-1.0.3/architecture/job-submission-preparation-and-execution-process.md
@@ -30,7 +30,7 @@ The submission phase is mainly the interaction of Client -> Linkis Gateway -> En
-1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](user_guide/how_to_use.md)):
+1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](../user_guide/how-to-use.md)):
```
POST /api/rest_j/v1/entrance/submit
```
@@ -62,7 +62,7 @@ If the user has a reusable EngineConn in LinkisManager, the EngineConn is direct
How to define a reusable EngineConn? It refers to those that can match all the label requirements of the computing task, and the EngineConn's own health status is Healthy (the load is low and the actual status is Idle). Then, all the EngineConn that meets the conditions are sorted and selected according to the rules, and finally the best one is locked.
-If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](add_an_engine_conn.md).
+If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](add-an-engine-conn.md).
#### 2.2 Orchestrate a computing task
diff --git a/versioned_docs/version-1.0.3/architecture/overview.md b/versioned_docs/version-1.0.3/architecture/overview.md
index 3a45df32c6..e3efc03e13 100644
--- a/versioned_docs/version-1.0.3/architecture/overview.md
+++ b/versioned_docs/version-1.0.3/architecture/overview.md
@@ -15,7 +15,7 @@ The specific responsibilities of each category are as follows:
The following is a directory listing of Linkis1.0 architecture documents:
-1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference_between_1.0_and_0.x.md).
+1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference-between-1.0-and-0.x.md).
2. Linkis 1.0 public enhancement service related documents, please read [Public Enhancement Service](public_enhancement_services/overview.md).
3. Linkis 1.0 microservice governance related documents, please read [Microservice Governance](microservice_governance_services/overview.md).
4. Linkis 1.0 computing governance service related documents, please read [Computation Governance Service](computation_governance_services/overview.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_cache.md b/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_client.md b/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_client.md
rename to versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_listener.md b/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_persistence.md b/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_search.md b/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service_search.md
rename to versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service.md b/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context_service.md
rename to versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/overview.md b/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/overview.md
index 4fae9dfbab..d44f182f29 100644
--- a/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/overview.md
+++ b/versioned_docs/version-1.0.3/architecture/public_enhancement_services/context_service/overview.md
@@ -101,28 +101,28 @@ The runtime workflow is mainly used by Linkis.
### 1. Client
The entrance of external access to CS, Client module provides HA function;
-[Enter Client Architecture Design](context_service_client.md)
+[Enter Client Architecture Design](context-service-client.md)
### 2. Service Module
Provide a Restful interface to encapsulate and process CS requests submitted by the client;
-[Enter Service Architecture Design](context_service.md)
+[Enter Service Architecture Design](context-service.md)
### 3. ContextSearch
The context query module provides rich and powerful query capabilities for the client to find the key-value key-value pairs of the context;
-[Enter ContextSearch architecture design](context_service_search.md)
+[Enter ContextSearch architecture design](context-service-search.md)
### 4. Listener
The CS listener module provides synchronous and asynchronous event consumption capabilities, and has the ability to notify the Client in real time once the Zookeeper-like Key-Value is updated;
-[Enter Listener architecture design](context_service_listener.md)
+[Enter Listener architecture design](context-service-listener.md)
### 5. ContextCache
The context memory cache module provides the ability to quickly retrieve the context and the ability to monitor and clean up JVM memory usage;
-[Enter ContextCache architecture design](context_service_cache.md)
+[Enter ContextCache architecture design](context-service-cache.md)
### 6. HighAvailable
Provide CS high availability capability;
-[Enter HighAvailable architecture design](context_service_highavailable.md)
+[Enter HighAvailable architecture design](context-service-highavailable.md)
### 7. Persistence
The persistence function of CS;
-[Enter Persistence architecture design](context_service_persistence.md)
\ No newline at end of file
+[Enter Persistence architecture design](context-service-persistence.md)
\ No newline at end of file
diff --git a/versioned_docs/version-1.0.3/architecture/public_enhancement_services/public_service.md b/versioned_docs/version-1.0.3/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from versioned_docs/version-1.0.3/architecture/public_enhancement_services/public_service.md
rename to versioned_docs/version-1.0.3/architecture/public_enhancement_services/public-service.md
diff --git a/versioned_docs/version-1.0.3/deployment/cluster_deployment.md b/versioned_docs/version-1.0.3/deployment/cluster-deployment.md
similarity index 100%
rename from versioned_docs/version-1.0.3/deployment/cluster_deployment.md
rename to versioned_docs/version-1.0.3/deployment/cluster-deployment.md
diff --git a/versioned_docs/version-1.0.3/deployment/engine_conn_plugin_installation.md b/versioned_docs/version-1.0.3/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from versioned_docs/version-1.0.3/deployment/engine_conn_plugin_installation.md
rename to versioned_docs/version-1.0.3/deployment/engine-conn-plugin-installation.md
diff --git a/versioned_docs/version-1.0.3/deployment/installation_hierarchical_structure.md b/versioned_docs/version-1.0.3/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.0.3/deployment/installation_hierarchical_structure.md
rename to versioned_docs/version-1.0.3/deployment/installation-hierarchical-structure.md
diff --git a/versioned_docs/version-1.1.0/deployment/quick_deploy.md b/versioned_docs/version-1.0.3/deployment/quick-deploy.md
similarity index 99%
rename from versioned_docs/version-1.1.0/deployment/quick_deploy.md
rename to versioned_docs/version-1.0.3/deployment/quick-deploy.md
index c59aee52fc..55bb0847a8 100644
--- a/versioned_docs/version-1.1.0/deployment/quick_deploy.md
+++ b/versioned_docs/version-1.0.3/deployment/quick-deploy.md
@@ -8,7 +8,7 @@ sidebar_position: 1
Because the mysql-connector-java driver is under the GPL2.0 agreement and does not meet the license policy of the Apache open source agreement, starting from version 1.0.3, the official deployment package of the Apache version is provided. The default is no mysql-connector-java-x.x.x.jar dependency package. You need to add dependencies to the corresponding lib package during installation and deployment.
</font>
-If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md).
+If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md).
Please note: Apart from the four EngineConnPlugins included in the Linkis 1.0 installation package by default: Python/Shell/Hive/Spark. You can manually install other types of engines such as JDBC depending on your own needs. For details, please refer to EngineConnPlugin installation documents.
diff --git a/versioned_docs/version-1.0.3/deployment/sourcecode_hierarchical_structure.md b/versioned_docs/version-1.0.3/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.0.3/deployment/sourcecode_hierarchical_structure.md
rename to versioned_docs/version-1.0.3/deployment/sourcecode-hierarchical-structure.md
diff --git a/docs/deployment/web_install.md b/versioned_docs/version-1.0.3/deployment/web-install.md
similarity index 99%
rename from docs/deployment/web_install.md
rename to versioned_docs/version-1.0.3/deployment/web-install.md
index 38f9e471be..6e91d7ef11 100644
--- a/docs/deployment/web_install.md
+++ b/versioned_docs/version-1.0.3/deployment/web-install.md
@@ -3,7 +3,7 @@ title: Linkis Console Deployment
sidebar_position: 6
---
-Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick_deploy.md)
+Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick-deploy.md)
## 1. Preparation
diff --git a/versioned_docs/version-1.1.0/development/linkis_compile_and_package.md b/versioned_docs/version-1.0.3/development/linkis-compile-and-package.md
similarity index 98%
rename from versioned_docs/version-1.1.0/development/linkis_compile_and_package.md
rename to versioned_docs/version-1.0.3/development/linkis-compile-and-package.md
index f90db5fd2f..50c1a4a279 100644
--- a/versioned_docs/version-1.1.0/development/linkis_compile_and_package.md
+++ b/versioned_docs/version-1.0.3/development/linkis-compile-and-package.md
@@ -108,7 +108,7 @@ Get the installation package, there will be a compiled package in the ->target d
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/linkis-engineplugin-spark-x.x.x.jar
```
-How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine_conn_plugin_installation)
+How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine-conn-plugin-installation)
## 5. How to modify the Hadoop, Hive, and Spark versions that Linkis depends on
diff --git a/versioned_docs/version-1.0.3/development/linkis_debug.md b/versioned_docs/version-1.0.3/development/linkis-debug.md
similarity index 100%
rename from versioned_docs/version-1.0.3/development/linkis_debug.md
rename to versioned_docs/version-1.0.3/development/linkis-debug.md
diff --git a/versioned_docs/version-1.0.3/development/new_engine_conn.md b/versioned_docs/version-1.0.3/development/new-engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.0.3/development/new_engine_conn.md
rename to versioned_docs/version-1.0.3/development/new-engine-conn.md
diff --git a/versioned_docs/version-1.0.3/development/web_build.md b/versioned_docs/version-1.0.3/development/web-build.md
similarity index 100%
rename from versioned_docs/version-1.0.3/development/web_build.md
rename to versioned_docs/version-1.0.3/development/web-build.md
diff --git a/versioned_docs/version-1.0.3/engine_usage/flink.md b/versioned_docs/version-1.0.3/engine_usage/flink.md
index 2e61249144..535264d7ba 100644
--- a/versioned_docs/version-1.0.3/engine_usage/flink.md
+++ b/versioned_docs/version-1.0.3/engine_usage/flink.md
@@ -56,13 +56,13 @@ cd ${LINKIS_HOME}/sbin
sh linkis-daemon restart cg-engineplugin
```
A more detailed introduction to engineplugin can be found in the following article.
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Flink engine tags
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. The use of Flink engine
@@ -115,7 +115,7 @@ After Linkis 1.0, a cli method is provided to submit tasks. We only need to spec
sh ./bin/linkis-cli -engineType flink-1.12.2 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-For specific usage, please refer to: [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+For specific usage, please refer to: [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 OnceEngineConn method
diff --git a/versioned_docs/version-1.0.3/engine_usage/hive.md b/versioned_docs/version-1.0.3/engine_usage/hive.md
index bc52ab4846..b685701af7 100644
--- a/versioned_docs/version-1.0.3/engine_usage/hive.md
+++ b/versioned_docs/version-1.0.3/engine_usage/hive.md
@@ -32,13 +32,13 @@ Other hive operating modes are similar, just copy the corresponding dependencies
If you have already compiled your hive engineConn plug-in has been compiled, then you need to put the new plug-in in the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Linkis adds Hive console parameters(optional)
Linkis can configure the corresponding EngineConn parameters on the management console. If your newly added EngineConn needs this feature, you can refer to the following documents:
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of hive engineConn
@@ -54,7 +54,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -69,7 +69,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.0.3/engine_usage/jdbc.md b/versioned_docs/version-1.0.3/engine_usage/jdbc.md
index 1db1d63951..47d84a6aab 100644
--- a/versioned_docs/version-1.0.3/engine_usage/jdbc.md
+++ b/versioned_docs/version-1.0.3/engine_usage/jdbc.md
@@ -43,7 +43,7 @@ wds.linkis.jdbc.password
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -58,7 +58,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.0.3/engine_usage/python.md b/versioned_docs/version-1.0.3/engine_usage/python.md
index 97ee168c13..5cc6fb2418 100644
--- a/versioned_docs/version-1.0.3/engine_usage/python.md
+++ b/versioned_docs/version-1.0.3/engine_usage/python.md
@@ -39,7 +39,7 @@ Before submitting python on linkis, you only need to make sure that there is pyt
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -54,7 +54,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.0.3/engine_usage/shell.md b/versioned_docs/version-1.0.3/engine_usage/shell.md
index d99a4ca96e..3296981943 100644
--- a/versioned_docs/version-1.0.3/engine_usage/shell.md
+++ b/versioned_docs/version-1.0.3/engine_usage/shell.md
@@ -37,7 +37,7 @@ Before submitting the shell on linkis, you only need to ensure that there is the
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -52,7 +52,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.0.3/engine_usage/spark.md b/versioned_docs/version-1.0.3/engine_usage/spark.md
index 106ebce8f7..5bde17587c 100644
--- a/versioned_docs/version-1.0.3/engine_usage/spark.md
+++ b/versioned_docs/version-1.0.3/engine_usage/spark.md
@@ -34,13 +34,13 @@ In theory, Linkis1.0 supports all versions of spark2.x and above. Spark 2.4.3 is
If you have already compiled your spark EngineConn plug-in has been compiled, then you need to put the new plug-in to the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 tags of spark EngineConn
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of spark EngineConn
@@ -56,7 +56,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -72,7 +72,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
## codeType py-->pyspark sql-->sparkSQL scala-->Spark scala
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.0.3/introduction.md b/versioned_docs/version-1.0.3/introduction.md
index 0f7629efe4..5782880e05 100644
--- a/versioned_docs/version-1.0.3/introduction.md
+++ b/versioned_docs/version-1.0.3/introduction.md
@@ -54,8 +54,8 @@ Since the first release of Linkis in 2019, it has accumulated more than **700**
Please go to the [Linkis releases page](https://github.com/apache/incubator-linkis/releases) to download a compiled distribution or a source code package of Linkis.
## Compile and deploy
-Please follow [Compile Guide](development/linkis_compile_and_package.md) to compile Linkis from source code.
-Please refer to [Deployment_Documents](deployment/quick_deploy.md) to do the deployment.
+Please follow [Compile Guide](development/linkis-compile-and-package.md) to compile Linkis from source code.
+Please refer to [Deployment_Documents](deployment/quick-deploy.md) to do the deployment.
## Examples and Guidance
You can find examples and guidance for how to use and manage Linkis in [User_Manual](user_guide/overview.md), [Engine_Usage_Documents](engine_usage/overview.md) and [API_Documents](../../docs/api/overview.md).
diff --git a/versioned_docs/version-1.0.3/tuning_and_troubleshooting/overview.md b/versioned_docs/version-1.0.3/tuning_and_troubleshooting/overview.md
index 1211422047..3d2ba065a5 100644
--- a/versioned_docs/version-1.0.3/tuning_and_troubleshooting/overview.md
+++ b/versioned_docs/version-1.0.3/tuning_and_troubleshooting/overview.md
@@ -100,4 +100,4 @@ For problems that cannot be resolved according to the above process positioning
### Ⅵ. locate the source code by remote debug
-Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode_hierarchical_structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
+Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode-hierarchical-structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
diff --git a/versioned_docs/version-1.0.3/upgrade/overview.md b/versioned_docs/version-1.0.3/upgrade/overview.md
index cb2cca3079..11a268a06e 100644
--- a/versioned_docs/version-1.0.3/upgrade/overview.md
+++ b/versioned_docs/version-1.0.3/upgrade/overview.md
@@ -8,4 +8,4 @@ The architecture of Linkis1.0 is very different from Linkis0.x, and there are so
1. If you are installing Linkis for the first time, or reinstalling Linkis, you do not need to pay attention to the Linkis Upgrade Guide.
-2. If you are upgrading from Linkis0.x to Linkis1.0, be sure to read the [Linkis Upgrade from 0.x to 1.0 guide](upgrade_from_0.X_to_1.0_guide.md) carefully.
+2. If you are upgrading from Linkis0.x to Linkis1.0, be sure to read the [Linkis Upgrade from 0.x to 1.0 guide](upgrade-from-0.X-to-1.0-guide.md) carefully.
diff --git a/versioned_docs/version-1.0.3/upgrade/upgrade_from_0.X_to_1.0_guide.md b/versioned_docs/version-1.0.3/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 95%
rename from versioned_docs/version-1.0.3/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to versioned_docs/version-1.0.3/upgrade/upgrade-from-0.X-to-1.0-guide.md
index d030c2aca9..6c16652529 100644
--- a/versioned_docs/version-1.0.3/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/versioned_docs/version-1.0.3/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 3
## 1.Precautions
- **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md)**.
+ **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md)**.
## 2. Service upgrade installation
@@ -15,7 +15,7 @@ sidebar_position: 3
If you need to keep 0.X data during the upgrade, you must select 1 to skip the table building statement (see the code below).
- For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ source linkis_configuration_dml.sql
## 4. Installation and startup Linkis1.0
- Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
diff --git a/versioned_docs/version-1.0.3/user_guide/console_manual.md b/versioned_docs/version-1.0.3/user_guide/console-manual.md
similarity index 100%
rename from versioned_docs/version-1.0.3/user_guide/console_manual.md
rename to versioned_docs/version-1.0.3/user_guide/console-manual.md
diff --git a/versioned_docs/version-1.0.2/user_guide/how_to_use.md b/versioned_docs/version-1.0.3/user_guide/how-to-use.md
similarity index 94%
rename from versioned_docs/version-1.0.2/user_guide/how_to_use.md
rename to versioned_docs/version-1.0.3/user_guide/how-to-use.md
index a7654d58ce..8d84c4ec80 100644
--- a/versioned_docs/version-1.0.2/user_guide/how_to_use.md
+++ b/versioned_docs/version-1.0.3/user_guide/how-to-use.md
@@ -10,9 +10,9 @@ sidebar_position: 1
## 1. Client side usage
If you need to connect to other applications on the basis of Linkis, you need to develop the interface provided by Linkis. Linkis provides a variety of client access interfaces. For detailed usage introduction, please refer to the following:
-- [**Restful API Usage**](api/linkis_task_operator.md)
-- [**JDBC API Usage**](api/jdbc_api.md)
-- [**How to use Java SDK**](user_guide/sdk_manual.md)
+- [**Restful API Usage**](api/linkis-task-operator.md)
+- [**JDBC API Usage**](api/jdbc-api.md)
+- [**How to use Java SDK**](../user_guide/sdk-manual.md)
## 2. Scriptis uses Linkis
diff --git a/versioned_docs/version-1.0.3/user_guide/linkiscli_manual.md b/versioned_docs/version-1.0.3/user_guide/linkiscli-manual.md
similarity index 100%
rename from versioned_docs/version-1.0.3/user_guide/linkiscli_manual.md
rename to versioned_docs/version-1.0.3/user_guide/linkiscli-manual.md
diff --git a/versioned_docs/version-1.0.3/user_guide/overview.md b/versioned_docs/version-1.0.3/user_guide/overview.md
index 2a6d4b1b9b..3aa5f4450a 100644
--- a/versioned_docs/version-1.0.3/user_guide/overview.md
+++ b/versioned_docs/version-1.0.3/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis considered the scalability of the access method at the beginning of the design. For different access scenarios, Linkis provides front-end access and SDK access. HTTP and WebSocket interfaces are also provided on the basis of front-end interfaces. If you are interested in accessing and using Linkis, you can refer to the following documents:
-- [How to Use Links](how_to_use.md)
-- [Linkis Management Console Manual](console_manual.md)
-- [Linkis1.0 SDK Manual](sdk_manual.md)
-- [Linkis-Cli Manual](linkiscli_manual.md)
+- [How to Use Links](how-to-use.md)
+- [Linkis Management Console Manual](console-manual.md)
+- [Linkis1.0 SDK Manual](sdk-manual.md)
+- [Linkis-Cli Manual](linkiscli-manual.md)
diff --git a/versioned_docs/version-1.0.3/user_guide/sdk_manual.md b/versioned_docs/version-1.0.3/user_guide/sdk-manual.md
similarity index 100%
rename from versioned_docs/version-1.0.3/user_guide/sdk_manual.md
rename to versioned_docs/version-1.0.3/user_guide/sdk-manual.md
diff --git a/versioned_docs/version-1.1.0/api/jdbc_api.md b/versioned_docs/version-1.1.0/api/jdbc-api.md
similarity index 100%
rename from versioned_docs/version-1.1.0/api/jdbc_api.md
rename to versioned_docs/version-1.1.0/api/jdbc-api.md
diff --git a/versioned_docs/version-1.1.0/api/linkis_task_operator.md b/versioned_docs/version-1.1.0/api/linkis-task-operator.md
similarity index 100%
rename from versioned_docs/version-1.1.0/api/linkis_task_operator.md
rename to versioned_docs/version-1.1.0/api/linkis-task-operator.md
diff --git a/versioned_docs/version-1.1.0/api/login_api.md b/versioned_docs/version-1.1.0/api/login-api.md
similarity index 100%
rename from versioned_docs/version-1.1.0/api/login_api.md
rename to versioned_docs/version-1.1.0/api/login-api.md
diff --git a/versioned_docs/version-1.1.0/api/overview.md b/versioned_docs/version-1.1.0/api/overview.md
index 60a92418bb..3f08075bde 100644
--- a/versioned_docs/version-1.1.0/api/overview.md
+++ b/versioned_docs/version-1.1.0/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 0
## 1. Document description
Linkis1.0 has been refactored and optimized on the basis of Linkix0.x, and it is also compatible with the 0.x interface. However, in order to prevent compatibility problems when using version 1.0, you need to read the following documents carefully:
-1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login_api.md) carefully.
+1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login-api.md) carefully.
-2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc_api.md).
+2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc-api.md).
-3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis_task_operator.md).
\ No newline at end of file
+3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis-task-operator.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.0/architecture/add_an_engine_conn.md b/versioned_docs/version-1.1.0/architecture/add-an-engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/add_an_engine_conn.md
rename to versioned_docs/version-1.1.0/architecture/add-an-engine-conn.md
diff --git a/versioned_docs/version-1.1.0/architecture/commons/message_scheduler.md b/versioned_docs/version-1.1.0/architecture/commons/message-scheduler.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/commons/message_scheduler.md
rename to versioned_docs/version-1.1.0/architecture/commons/message-scheduler.md
diff --git a/versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn_manager.md b/versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn_plugin.md b/versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn.md b/versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine_conn.md
rename to versioned_docs/version-1.1.0/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/app_manager.md b/versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/label_manager.md b/versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/resource_manager.md b/versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to versioned_docs/version-1.1.0/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/versioned_docs/version-1.1.0/architecture/computation_governance_services/overview.md b/versioned_docs/version-1.1.0/architecture/computation_governance_services/overview.md
index 80c421ad74..9446468701 100644
--- a/versioned_docs/version-1.1.0/architecture/computation_governance_services/overview.md
+++ b/versioned_docs/version-1.1.0/architecture/computation_governance_services/overview.md
@@ -44,7 +44,7 @@ Perform three stages to fully upgrade Linkis's Job execution architecture, as sh
[Enter LinkisManager Architecture Design](linkis_manager/overview.md)
### 4. Engine Manager
Engine conn Manager (ECM) is a simplified and upgraded version of linkis0. X engine manager. The ECM under linkis1.0 removes the application ability of the engine, and the whole microservice is completely stateless. It will focus on supporting the startup and destruction of all kinds of enginecon.
-[Enter EngineConnManager Architecture Design](engine/engine_conn_manager.md)
+[Enter EngineConnManager Architecture Design](engine/engine-conn-manager.md)
### 5. EngineConn
EngineConn is an optimized and upgraded version of Linkis0.X Engine. It will provide EngineConn and Executor two modules. EngineConn is used to connect the underlying computing storage engine and provide a session session that connects the underlying computing storage engines; Executor is based on this Session session , Provide full-stack computing support for interactive computing, streaming computing, offline computing, and data storage.
- [Enter EngineConn Architecture Design](engine/engine_conn.md)
+ [Enter EngineConn Architecture Design](engine/engine-conn.md)
diff --git a/versioned_docs/version-1.1.0/architecture/difference_between_1.0_and_0.x.md b/versioned_docs/version-1.1.0/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/difference_between_1.0_and_0.x.md
rename to versioned_docs/version-1.1.0/architecture/difference-between-1.0-and-0.x.md
diff --git a/versioned_docs/version-1.1.1/architecture/job_submission_preparation_and_execution_process.md b/versioned_docs/version-1.1.0/architecture/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from versioned_docs/version-1.1.1/architecture/job_submission_preparation_and_execution_process.md
rename to versioned_docs/version-1.1.0/architecture/job-submission-preparation-and-execution-process.md
index dd6e8436c9..1d62458cc6 100644
--- a/versioned_docs/version-1.1.1/architecture/job_submission_preparation_and_execution_process.md
+++ b/versioned_docs/version-1.1.0/architecture/job-submission-preparation-and-execution-process.md
@@ -30,7 +30,7 @@ The submission phase is mainly the interaction of Client -> Linkis Gateway -> En
-1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](user_guide/how_to_use.md)):
+1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](../user_guide/how-to-use.md)):
```
POST /api/rest_j/v1/entrance/submit
```
@@ -62,7 +62,7 @@ If the user has a reusable EngineConn in LinkisManager, the EngineConn is direct
How to define a reusable EngineConn? It refers to those that can match all the label requirements of the computing task, and the EngineConn's own health status is Healthy (the load is low and the actual status is Idle). Then, all the EngineConn that meets the conditions are sorted and selected according to the rules, and finally the best one is locked.
-If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](add_an_engine_conn.md).
+If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](add-an-engine-conn.md).
#### 2.2 Orchestrate a computing task
diff --git a/versioned_docs/version-1.1.0/architecture/overview.md b/versioned_docs/version-1.1.0/architecture/overview.md
index 3a45df32c6..e3efc03e13 100644
--- a/versioned_docs/version-1.1.0/architecture/overview.md
+++ b/versioned_docs/version-1.1.0/architecture/overview.md
@@ -15,7 +15,7 @@ The specific responsibilities of each category are as follows:
The following is a directory listing of Linkis1.0 architecture documents:
-1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference_between_1.0_and_0.x.md).
+1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference-between-1.0-and-0.x.md).
2. Linkis 1.0 public enhancement service related documents, please read [Public Enhancement Service](public_enhancement_services/overview.md).
3. Linkis 1.0 microservice governance related documents, please read [Microservice Governance](microservice_governance_services/overview.md).
4. Linkis 1.0 computing governance service related documents, please read [Computation Governance Service](computation_governance_services/overview.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/bml/engine_bml_dissect.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/bml/engine-bml-dissect.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/bml/engine_bml_dissect.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/bml/engine-bml-dissect.md
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_cache.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_client.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_client.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_listener.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_persistence.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_search.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service_search.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context_service.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/overview.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/overview.md
index 4fae9dfbab..d44f182f29 100644
--- a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/overview.md
+++ b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/context_service/overview.md
@@ -101,28 +101,28 @@ The runtime workflow is mainly used by Linkis.
### 1. Client
The entrance of external access to CS, Client module provides HA function;
-[Enter Client Architecture Design](context_service_client.md)
+[Enter Client Architecture Design](context-service-client.md)
### 2. Service Module
Provide a Restful interface to encapsulate and process CS requests submitted by the client;
-[Enter Service Architecture Design](context_service.md)
+[Enter Service Architecture Design](context-service.md)
### 3. ContextSearch
The context query module provides rich and powerful query capabilities for the client to find the key-value key-value pairs of the context;
-[Enter ContextSearch architecture design](context_service_search.md)
+[Enter ContextSearch architecture design](context-service-search.md)
### 4. Listener
The CS listener module provides synchronous and asynchronous event consumption capabilities, and has the ability to notify the Client in real time once the Zookeeper-like Key-Value is updated;
-[Enter Listener architecture design](context_service_listener.md)
+[Enter Listener architecture design](context-service-listener.md)
### 5. ContextCache
The context memory cache module provides the ability to quickly retrieve the context and the ability to monitor and clean up JVM memory usage;
-[Enter ContextCache architecture design](context_service_cache.md)
+[Enter ContextCache architecture design](context-service-cache.md)
### 6. HighAvailable
Provide CS high availability capability;
-[Enter HighAvailable architecture design](context_service_highavailable.md)
+[Enter HighAvailable architecture design](context-service-highavailable.md)
### 7. Persistence
The persistence function of CS;
-[Enter Persistence architecture design](context_service_persistence.md)
\ No newline at end of file
+[Enter Persistence architecture design](context-service-persistence.md)
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/datasource_manager.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/datasource-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/datasource_manager.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/datasource-manager.md
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/metadata_manager.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/metadata-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/metadata_manager.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/metadata-manager.md
diff --git a/versioned_docs/version-1.1.0/architecture/public_enhancement_services/public_service.md b/versioned_docs/version-1.1.0/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from versioned_docs/version-1.1.0/architecture/public_enhancement_services/public_service.md
rename to versioned_docs/version-1.1.0/architecture/public_enhancement_services/public-service.md
diff --git a/versioned_docs/version-1.1.0/deployment/cluster_deployment.md b/versioned_docs/version-1.1.0/deployment/cluster-deployment.md
similarity index 100%
rename from versioned_docs/version-1.1.0/deployment/cluster_deployment.md
rename to versioned_docs/version-1.1.0/deployment/cluster-deployment.md
diff --git a/versioned_docs/version-1.1.0/deployment/engine_conn_plugin_installation.md b/versioned_docs/version-1.1.0/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from versioned_docs/version-1.1.0/deployment/engine_conn_plugin_installation.md
rename to versioned_docs/version-1.1.0/deployment/engine-conn-plugin-installation.md
diff --git a/versioned_docs/version-1.1.0/deployment/installation_hierarchical_structure.md b/versioned_docs/version-1.1.0/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.1.0/deployment/installation_hierarchical_structure.md
rename to versioned_docs/version-1.1.0/deployment/installation-hierarchical-structure.md
diff --git a/versioned_docs/version-1.1.0/deployment/involve_skywalking_into_linkis.md b/versioned_docs/version-1.1.0/deployment/involve-skywalking-into-linkis.md
similarity index 100%
rename from versioned_docs/version-1.1.0/deployment/involve_skywalking_into_linkis.md
rename to versioned_docs/version-1.1.0/deployment/involve-skywalking-into-linkis.md
diff --git a/versioned_docs/version-1.0.3/deployment/quick_deploy.md b/versioned_docs/version-1.1.0/deployment/quick-deploy.md
similarity index 99%
rename from versioned_docs/version-1.0.3/deployment/quick_deploy.md
rename to versioned_docs/version-1.1.0/deployment/quick-deploy.md
index c59aee52fc..55bb0847a8 100644
--- a/versioned_docs/version-1.0.3/deployment/quick_deploy.md
+++ b/versioned_docs/version-1.1.0/deployment/quick-deploy.md
@@ -8,7 +8,7 @@ sidebar_position: 1
Because the mysql-connector-java driver is under the GPL2.0 agreement and does not meet the license policy of the Apache open source agreement, starting from version 1.0.3, the official deployment package of the Apache version is provided. The default is no mysql-connector-java-x.x.x.jar dependency package. You need to add dependencies to the corresponding lib package during installation and deployment.
</font>
-If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md).
+If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md).
Please note: Apart from the four EngineConnPlugins included in the Linkis 1.0 installation package by default: Python/Shell/Hive/Spark. You can manually install other types of engines such as JDBC depending on your own needs. For details, please refer to EngineConnPlugin installation documents.
diff --git a/versioned_docs/version-1.1.0/deployment/sourcecode_hierarchical_structure.md b/versioned_docs/version-1.1.0/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.1.0/deployment/sourcecode_hierarchical_structure.md
rename to versioned_docs/version-1.1.0/deployment/sourcecode-hierarchical-structure.md
diff --git a/versioned_docs/version-1.1.0/deployment/start_metadatasource.md b/versioned_docs/version-1.1.0/deployment/start-metadatasource.md
similarity index 100%
rename from versioned_docs/version-1.1.0/deployment/start_metadatasource.md
rename to versioned_docs/version-1.1.0/deployment/start-metadatasource.md
diff --git a/versioned_docs/version-1.1.0/deployment/web_install.md b/versioned_docs/version-1.1.0/deployment/web-install.md
similarity index 99%
rename from versioned_docs/version-1.1.0/deployment/web_install.md
rename to versioned_docs/version-1.1.0/deployment/web-install.md
index 38f9e471be..6e91d7ef11 100644
--- a/versioned_docs/version-1.1.0/deployment/web_install.md
+++ b/versioned_docs/version-1.1.0/deployment/web-install.md
@@ -3,7 +3,7 @@ title: Linkis Console Deployment
sidebar_position: 6
---
-Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick_deploy.md)
+Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick-deploy.md)
## 1. Preparation
diff --git a/versioned_docs/version-1.1.1/development/linkis_compile_and_package.md b/versioned_docs/version-1.1.0/development/linkis-compile-and-package.md
similarity index 98%
rename from versioned_docs/version-1.1.1/development/linkis_compile_and_package.md
rename to versioned_docs/version-1.1.0/development/linkis-compile-and-package.md
index f90db5fd2f..50c1a4a279 100644
--- a/versioned_docs/version-1.1.1/development/linkis_compile_and_package.md
+++ b/versioned_docs/version-1.1.0/development/linkis-compile-and-package.md
@@ -108,7 +108,7 @@ Get the installation package, there will be a compiled package in the ->target d
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/linkis-engineplugin-spark-x.x.x.jar
```
-How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine_conn_plugin_installation)
+How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine-conn-plugin-installation)
## 5. How to modify the Hadoop, Hive, and Spark versions that Linkis depends on
diff --git a/versioned_docs/version-1.1.0/development/linkis_config.md b/versioned_docs/version-1.1.0/development/linkis-config.md
similarity index 100%
rename from versioned_docs/version-1.1.0/development/linkis_config.md
rename to versioned_docs/version-1.1.0/development/linkis-config.md
diff --git a/versioned_docs/version-1.1.0/development/linkis_debug_in_mac.md b/versioned_docs/version-1.1.0/development/linkis-debug-in-mac.md
similarity index 100%
rename from versioned_docs/version-1.1.0/development/linkis_debug_in_mac.md
rename to versioned_docs/version-1.1.0/development/linkis-debug-in-mac.md
diff --git a/versioned_docs/version-1.1.0/development/linkis_debug.md b/versioned_docs/version-1.1.0/development/linkis-debug.md
similarity index 100%
rename from versioned_docs/version-1.1.0/development/linkis_debug.md
rename to versioned_docs/version-1.1.0/development/linkis-debug.md
diff --git a/versioned_docs/version-1.1.0/development/new_engine_conn.md b/versioned_docs/version-1.1.0/development/new-engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.1.0/development/new_engine_conn.md
rename to versioned_docs/version-1.1.0/development/new-engine-conn.md
diff --git a/versioned_docs/version-1.1.0/development/web_build.md b/versioned_docs/version-1.1.0/development/web-build.md
similarity index 100%
rename from versioned_docs/version-1.1.0/development/web_build.md
rename to versioned_docs/version-1.1.0/development/web-build.md
diff --git a/versioned_docs/version-1.1.0/engine_usage/flink.md b/versioned_docs/version-1.1.0/engine_usage/flink.md
index 2e61249144..535264d7ba 100644
--- a/versioned_docs/version-1.1.0/engine_usage/flink.md
+++ b/versioned_docs/version-1.1.0/engine_usage/flink.md
@@ -56,13 +56,13 @@ cd ${LINKIS_HOME}/sbin
sh linkis-daemon restart cg-engineplugin
```
A more detailed introduction to engineplugin can be found in the following article.
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Flink engine tags
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. The use of Flink engine
@@ -115,7 +115,7 @@ After Linkis 1.0, a cli method is provided to submit tasks. We only need to spec
sh ./bin/linkis-cli -engineType flink-1.12.2 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-For specific usage, please refer to: [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+For specific usage, please refer to: [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 OnceEngineConn method
diff --git a/versioned_docs/version-1.1.0/engine_usage/hive.md b/versioned_docs/version-1.1.0/engine_usage/hive.md
index bc52ab4846..b685701af7 100644
--- a/versioned_docs/version-1.1.0/engine_usage/hive.md
+++ b/versioned_docs/version-1.1.0/engine_usage/hive.md
@@ -32,13 +32,13 @@ Other hive operating modes are similar, just copy the corresponding dependencies
If you have already compiled your hive engineConn plug-in has been compiled, then you need to put the new plug-in in the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Linkis adds Hive console parameters(optional)
Linkis can configure the corresponding EngineConn parameters on the management console. If your newly added EngineConn needs this feature, you can refer to the following documents:
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of hive engineConn
@@ -54,7 +54,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -69,7 +69,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.0/engine_usage/jdbc.md b/versioned_docs/version-1.1.0/engine_usage/jdbc.md
index 1db1d63951..47d84a6aab 100644
--- a/versioned_docs/version-1.1.0/engine_usage/jdbc.md
+++ b/versioned_docs/version-1.1.0/engine_usage/jdbc.md
@@ -43,7 +43,7 @@ wds.linkis.jdbc.password
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -58,7 +58,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.0/engine_usage/python.md b/versioned_docs/version-1.1.0/engine_usage/python.md
index 97ee168c13..5cc6fb2418 100644
--- a/versioned_docs/version-1.1.0/engine_usage/python.md
+++ b/versioned_docs/version-1.1.0/engine_usage/python.md
@@ -39,7 +39,7 @@ Before submitting python on linkis, you only need to make sure that there is pyt
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -54,7 +54,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.0/engine_usage/shell.md b/versioned_docs/version-1.1.0/engine_usage/shell.md
index d99a4ca96e..3296981943 100644
--- a/versioned_docs/version-1.1.0/engine_usage/shell.md
+++ b/versioned_docs/version-1.1.0/engine_usage/shell.md
@@ -37,7 +37,7 @@ Before submitting the shell on linkis, you only need to ensure that there is the
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -52,7 +52,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.0/engine_usage/spark.md b/versioned_docs/version-1.1.0/engine_usage/spark.md
index 106ebce8f7..5bde17587c 100644
--- a/versioned_docs/version-1.1.0/engine_usage/spark.md
+++ b/versioned_docs/version-1.1.0/engine_usage/spark.md
@@ -34,13 +34,13 @@ In theory, Linkis1.0 supports all versions of spark2.x and above. Spark 2.4.3 is
If you have already compiled your spark EngineConn plug-in has been compiled, then you need to put the new plug-in to the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 tags of spark EngineConn
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of spark EngineConn
@@ -56,7 +56,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -72,7 +72,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
## codeType py-->pyspark sql-->sparkSQL scala-->Spark scala
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.0/introduction.md b/versioned_docs/version-1.1.0/introduction.md
index e72932ac7c..443fd72bbf 100644
--- a/versioned_docs/version-1.1.0/introduction.md
+++ b/versioned_docs/version-1.1.0/introduction.md
@@ -51,8 +51,8 @@ Since the first release of Linkis in 2019, it has accumulated more than **700**
Please go to the [Linkis releases page](https://github.com/apache/incubator-linkis/releases) to download a compiled distribution or a source code package of Linkis.
## Compile and deploy
-Please follow [Compile Guide](development/linkis_compile_and_package.md) to compile Linkis from source code.
-Please refer to [Deployment_Documents](deployment/quick_deploy.md) to do the deployment.
+Please follow [Compile Guide](development/linkis-compile-and-package.md) to compile Linkis from source code.
+Please refer to [Deployment_Documents](deployment/quick-deploy.md) to do the deployment.
## Examples and Guidance
You can find examples and guidance for how to use and manage Linkis in [User_Manual](user_guide/overview.md), [Engine_Usage_Documents](engine_usage/overview.md) and [API_Documents](api/overview.md).
diff --git a/versioned_docs/version-1.1.0/release.md b/versioned_docs/version-1.1.0/release.md
index ad5a07a2f0..370ff7512f 100644
--- a/versioned_docs/version-1.1.0/release.md
+++ b/versioned_docs/version-1.1.0/release.md
@@ -3,13 +3,13 @@ title: Version Overview
sidebar_position: 0.1
---
-- [Datasource Management Service Architecture Documentation](/architecture/public_enhancement_services/datasource_manager.md)
-- [Metadata Management Services Architecture Documentation](/architecture/public_enhancement_services/metadata_manager.md)
-- [Data source introduction & function usage guide](/deployment/start_metadatasource.md)
-- [Guidelines for using the datasource client](/user_guide/linkis-datasource-client.md)
+- [Datasource Management Service Architecture Documentation](/architecture/public_enhancement_services/datasource-manager.md)
+- [Metadata Management Services Architecture Documentation](/architecture/public_enhancement_services/metadata-manager.md)
+- [Data source introduction & function usage guide](/deployment/start-metadatasource.md)
+- [Guidelines for using the datasource client](user_guide/linkis-datasource-client.md)
- [Data source http interface documentation](/api/http/data-source-manager-api.md)
- [Metadata http interface documentation](/api/http/metadatamanager-api.md)
-- [Start SkyWalking](/deployment/involve_skywalking_into_linkis.md)
+- [Start SkyWalking](/deployment/involve-skywalking-into-linkis.md)
- [Release-notes](/download/release-notes-1.1.0)
## Configuration Item
diff --git a/versioned_docs/version-1.1.0/tuning_and_troubleshooting/overview.md b/versioned_docs/version-1.1.0/tuning_and_troubleshooting/overview.md
index 1211422047..3d2ba065a5 100644
--- a/versioned_docs/version-1.1.0/tuning_and_troubleshooting/overview.md
+++ b/versioned_docs/version-1.1.0/tuning_and_troubleshooting/overview.md
@@ -100,4 +100,4 @@ For problems that cannot be resolved according to the above process positioning
### Ⅵ. locate the source code by remote debug
-Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode_hierarchical_structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
+Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode-hierarchical-structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.2/upgrade/upgrade_from_0.X_to_1.0_guide.md b/versioned_docs/version-1.1.0/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 95%
rename from versioned_docs/version-1.1.2/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to versioned_docs/version-1.1.0/upgrade/upgrade-from-0.X-to-1.0-guide.md
index 447bc141b1..60c1bed5a9 100644
--- a/versioned_docs/version-1.1.2/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/versioned_docs/version-1.1.0/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 1
## 1.Precautions
- **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md)**.
+ **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md)**.
## 2. Service upgrade installation
@@ -15,7 +15,7 @@ sidebar_position: 1
If you need to keep 0.X data during the upgrade, you must select 1 to skip the table building statement (see the code below).
- For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ source linkis_configuration_dml.sql
## 4. Installation and startup Linkis1.0
- Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
diff --git a/versioned_docs/version-1.1.0/upgrade/upgrade_guide.md b/versioned_docs/version-1.1.0/upgrade/upgrade-guide.md
similarity index 98%
rename from versioned_docs/version-1.1.0/upgrade/upgrade_guide.md
rename to versioned_docs/version-1.1.0/upgrade/upgrade-guide.md
index 5a26609071..2cfb67fd95 100644
--- a/versioned_docs/version-1.1.0/upgrade/upgrade_guide.md
+++ b/versioned_docs/version-1.1.0/upgrade/upgrade-guide.md
@@ -18,7 +18,7 @@ sidebar_position: 2
## 2 Service upgrade installation
-Press [Deployment guide document](../deployment/quick_deploy) (the installation of the management console in the document can be skipped) to install the new version.
+Press [Deployment guide document](../deployment/quick-deploy) (the installation of the management console in the document can be skipped) to install the new version.
When installing the service, if the historical data is retained, please retain the historical data, if you do not need to retain the data, just reinstall it directly
```shell script
diff --git a/versioned_docs/version-1.1.0/user_guide/console_manual.md b/versioned_docs/version-1.1.0/user_guide/console-manual.md
similarity index 100%
rename from versioned_docs/version-1.1.0/user_guide/console_manual.md
rename to versioned_docs/version-1.1.0/user_guide/console-manual.md
diff --git a/versioned_docs/version-1.0.3/user_guide/how_to_use.md b/versioned_docs/version-1.1.0/user_guide/how-to-use.md
similarity index 94%
rename from versioned_docs/version-1.0.3/user_guide/how_to_use.md
rename to versioned_docs/version-1.1.0/user_guide/how-to-use.md
index a7654d58ce..8d84c4ec80 100644
--- a/versioned_docs/version-1.0.3/user_guide/how_to_use.md
+++ b/versioned_docs/version-1.1.0/user_guide/how-to-use.md
@@ -10,9 +10,9 @@ sidebar_position: 1
## 1. Client side usage
If you need to connect to other applications on the basis of Linkis, you need to develop the interface provided by Linkis. Linkis provides a variety of client access interfaces. For detailed usage introduction, please refer to the following:
-- [**Restful API Usage**](api/linkis_task_operator.md)
-- [**JDBC API Usage**](api/jdbc_api.md)
-- [**How to use Java SDK**](user_guide/sdk_manual.md)
+- [**Restful API Usage**](api/linkis-task-operator.md)
+- [**JDBC API Usage**](api/jdbc-api.md)
+- [**How to use Java SDK**](../user_guide/sdk-manual.md)
## 2. Scriptis uses Linkis
diff --git a/versioned_docs/version-1.1.0/user_guide/linkiscli_manual.md b/versioned_docs/version-1.1.0/user_guide/linkiscli-manual.md
similarity index 100%
rename from versioned_docs/version-1.1.0/user_guide/linkiscli_manual.md
rename to versioned_docs/version-1.1.0/user_guide/linkiscli-manual.md
diff --git a/versioned_docs/version-1.1.0/user_guide/overview.md b/versioned_docs/version-1.1.0/user_guide/overview.md
index 2a6d4b1b9b..3aa5f4450a 100644
--- a/versioned_docs/version-1.1.0/user_guide/overview.md
+++ b/versioned_docs/version-1.1.0/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis considered the scalability of the access method at the beginning of the design. For different access scenarios, Linkis provides front-end access and SDK access. HTTP and WebSocket interfaces are also provided on the basis of front-end interfaces. If you are interested in accessing and using Linkis, you can refer to the following documents:
-- [How to Use Links](how_to_use.md)
-- [Linkis Management Console Manual](console_manual.md)
-- [Linkis1.0 SDK Manual](sdk_manual.md)
-- [Linkis-Cli Manual](linkiscli_manual.md)
+- [How to Use Links](how-to-use.md)
+- [Linkis Management Console Manual](console-manual.md)
+- [Linkis1.0 SDK Manual](sdk-manual.md)
+- [Linkis-Cli Manual](linkiscli-manual.md)
diff --git a/versioned_docs/version-1.1.0/user_guide/sdk_manual.md b/versioned_docs/version-1.1.0/user_guide/sdk-manual.md
similarity index 100%
rename from versioned_docs/version-1.1.0/user_guide/sdk_manual.md
rename to versioned_docs/version-1.1.0/user_guide/sdk-manual.md
diff --git a/versioned_docs/version-1.1.1/api/jdbc_api.md b/versioned_docs/version-1.1.1/api/jdbc-api.md
similarity index 100%
rename from versioned_docs/version-1.1.1/api/jdbc_api.md
rename to versioned_docs/version-1.1.1/api/jdbc-api.md
diff --git a/versioned_docs/version-1.1.1/api/linkis_task_operator.md b/versioned_docs/version-1.1.1/api/linkis-task-operator.md
similarity index 100%
rename from versioned_docs/version-1.1.1/api/linkis_task_operator.md
rename to versioned_docs/version-1.1.1/api/linkis-task-operator.md
diff --git a/versioned_docs/version-1.1.1/api/login_api.md b/versioned_docs/version-1.1.1/api/login-api.md
similarity index 100%
rename from versioned_docs/version-1.1.1/api/login_api.md
rename to versioned_docs/version-1.1.1/api/login-api.md
diff --git a/versioned_docs/version-1.1.1/api/overview.md b/versioned_docs/version-1.1.1/api/overview.md
index 60a92418bb..3f08075bde 100644
--- a/versioned_docs/version-1.1.1/api/overview.md
+++ b/versioned_docs/version-1.1.1/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 0
## 1. Document description
Linkis1.0 has been refactored and optimized on the basis of Linkix0.x, and it is also compatible with the 0.x interface. However, in order to prevent compatibility problems when using version 1.0, you need to read the following documents carefully:
-1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login_api.md) carefully.
+1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login-api.md) carefully.
-2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc_api.md).
+2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc-api.md).
-3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis_task_operator.md).
\ No newline at end of file
+3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis-task-operator.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.1/architecture/add_an_engine_conn.md b/versioned_docs/version-1.1.1/architecture/add-an-engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/add_an_engine_conn.md
rename to versioned_docs/version-1.1.1/architecture/add-an-engine-conn.md
diff --git a/versioned_docs/version-1.1.1/architecture/commons/message_scheduler.md b/versioned_docs/version-1.1.1/architecture/commons/message-scheduler.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/commons/message_scheduler.md
rename to versioned_docs/version-1.1.1/architecture/commons/message-scheduler.md
diff --git a/versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn_manager.md b/versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn_plugin.md b/versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn.md b/versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine_conn.md
rename to versioned_docs/version-1.1.1/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/app_manager.md b/versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/label_manager.md b/versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/resource_manager.md b/versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to versioned_docs/version-1.1.1/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/versioned_docs/version-1.1.1/architecture/computation_governance_services/overview.md b/versioned_docs/version-1.1.1/architecture/computation_governance_services/overview.md
index 80c421ad74..9446468701 100644
--- a/versioned_docs/version-1.1.1/architecture/computation_governance_services/overview.md
+++ b/versioned_docs/version-1.1.1/architecture/computation_governance_services/overview.md
@@ -44,7 +44,7 @@ Perform three stages to fully upgrade Linkis's Job execution architecture, as sh
[Enter LinkisManager Architecture Design](linkis_manager/overview.md)
### 4. Engine Manager
Engine conn Manager (ECM) is a simplified and upgraded version of linkis0. X engine manager. The ECM under linkis1.0 removes the application ability of the engine, and the whole microservice is completely stateless. It will focus on supporting the startup and destruction of all kinds of enginecon.
-[Enter EngineConnManager Architecture Design](engine/engine_conn_manager.md)
+[Enter EngineConnManager Architecture Design](engine/engine-conn-manager.md)
### 5. EngineConn
EngineConn is an optimized and upgraded version of Linkis0.X Engine. It will provide EngineConn and Executor two modules. EngineConn is used to connect the underlying computing storage engine and provide a session session that connects the underlying computing storage engines; Executor is based on this Session session , Provide full-stack computing support for interactive computing, streaming computing, offline computing, and data storage.
- [Enter EngineConn Architecture Design](engine/engine_conn.md)
+ [Enter EngineConn Architecture Design](engine/engine-conn.md)
diff --git a/versioned_docs/version-1.1.1/architecture/difference_between_1.0_and_0.x.md b/versioned_docs/version-1.1.1/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/difference_between_1.0_and_0.x.md
rename to versioned_docs/version-1.1.1/architecture/difference-between-1.0-and-0.x.md
diff --git a/versioned_docs/version-1.0.3/architecture/job_submission_preparation_and_execution_process.md b/versioned_docs/version-1.1.1/architecture/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from versioned_docs/version-1.0.3/architecture/job_submission_preparation_and_execution_process.md
rename to versioned_docs/version-1.1.1/architecture/job-submission-preparation-and-execution-process.md
index dd6e8436c9..1d62458cc6 100644
--- a/versioned_docs/version-1.0.3/architecture/job_submission_preparation_and_execution_process.md
+++ b/versioned_docs/version-1.1.1/architecture/job-submission-preparation-and-execution-process.md
@@ -30,7 +30,7 @@ The submission phase is mainly the interaction of Client -> Linkis Gateway -> En
-1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](user_guide/how_to_use.md)):
+1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](../user_guide/how-to-use.md)):
```
POST /api/rest_j/v1/entrance/submit
```
@@ -62,7 +62,7 @@ If the user has a reusable EngineConn in LinkisManager, the EngineConn is direct
How to define a reusable EngineConn? It refers to those that can match all the label requirements of the computing task, and the EngineConn's own health status is Healthy (the load is low and the actual status is Idle). Then, all the EngineConn that meets the conditions are sorted and selected according to the rules, and finally the best one is locked.
-If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](add_an_engine_conn.md).
+If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](add-an-engine-conn.md).
#### 2.2 Orchestrate a computing task
diff --git a/versioned_docs/version-1.1.1/architecture/overview.md b/versioned_docs/version-1.1.1/architecture/overview.md
index 3a45df32c6..e3efc03e13 100644
--- a/versioned_docs/version-1.1.1/architecture/overview.md
+++ b/versioned_docs/version-1.1.1/architecture/overview.md
@@ -15,7 +15,7 @@ The specific responsibilities of each category are as follows:
The following is a directory listing of Linkis1.0 architecture documents:
-1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference_between_1.0_and_0.x.md).
+1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference-between-1.0-and-0.x.md).
2. Linkis 1.0 public enhancement service related documents, please read [Public Enhancement Service](public_enhancement_services/overview.md).
3. Linkis 1.0 microservice governance related documents, please read [Microservice Governance](microservice_governance_services/overview.md).
4. Linkis 1.0 computing governance service related documents, please read [Computation Governance Service](computation_governance_services/overview.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.1/architecture/proxy_user.md b/versioned_docs/version-1.1.1/architecture/proxy-user.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/proxy_user.md
rename to versioned_docs/version-1.1.1/architecture/proxy-user.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/bml/engine_bml_dissect.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/bml/engine-bml-dissect.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/bml/engine_bml_dissect.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/bml/engine-bml-dissect.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_cache.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_client.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_client.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_listener.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_persistence.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_search.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service_search.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context_service.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/overview.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/overview.md
index 4fae9dfbab..d44f182f29 100644
--- a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/overview.md
+++ b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/context_service/overview.md
@@ -101,28 +101,28 @@ The runtime workflow is mainly used by Linkis.
### 1. Client
The entrance of external access to CS, Client module provides HA function;
-[Enter Client Architecture Design](context_service_client.md)
+[Enter Client Architecture Design](context-service-client.md)
### 2. Service Module
Provide a Restful interface to encapsulate and process CS requests submitted by the client;
-[Enter Service Architecture Design](context_service.md)
+[Enter Service Architecture Design](context-service.md)
### 3. ContextSearch
The context query module provides rich and powerful query capabilities for the client to find the key-value key-value pairs of the context;
-[Enter ContextSearch architecture design](context_service_search.md)
+[Enter ContextSearch architecture design](context-service-search.md)
### 4. Listener
The CS listener module provides synchronous and asynchronous event consumption capabilities, and has the ability to notify the Client in real time once the Zookeeper-like Key-Value is updated;
-[Enter Listener architecture design](context_service_listener.md)
+[Enter Listener architecture design](context-service-listener.md)
### 5. ContextCache
The context memory cache module provides the ability to quickly retrieve the context and the ability to monitor and clean up JVM memory usage;
-[Enter ContextCache architecture design](context_service_cache.md)
+[Enter ContextCache architecture design](context-service-cache.md)
### 6. HighAvailable
Provide CS high availability capability;
-[Enter HighAvailable architecture design](context_service_highavailable.md)
+[Enter HighAvailable architecture design](context-service-highavailable.md)
### 7. Persistence
The persistence function of CS;
-[Enter Persistence architecture design](context_service_persistence.md)
\ No newline at end of file
+[Enter Persistence architecture design](context-service-persistence.md)
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/datasource_manager.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/datasource-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/datasource_manager.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/datasource-manager.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/metadata_manager.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/metadata-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/metadata_manager.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/metadata-manager.md
diff --git a/versioned_docs/version-1.1.1/architecture/public_enhancement_services/public_service.md b/versioned_docs/version-1.1.1/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from versioned_docs/version-1.1.1/architecture/public_enhancement_services/public_service.md
rename to versioned_docs/version-1.1.1/architecture/public_enhancement_services/public-service.md
diff --git a/versioned_docs/version-1.1.1/deployment/cluster_deployment.md b/versioned_docs/version-1.1.1/deployment/cluster-deployment.md
similarity index 100%
rename from versioned_docs/version-1.1.1/deployment/cluster_deployment.md
rename to versioned_docs/version-1.1.1/deployment/cluster-deployment.md
diff --git a/versioned_docs/version-1.1.1/deployment/engine_conn_plugin_installation.md b/versioned_docs/version-1.1.1/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from versioned_docs/version-1.1.1/deployment/engine_conn_plugin_installation.md
rename to versioned_docs/version-1.1.1/deployment/engine-conn-plugin-installation.md
diff --git a/versioned_docs/version-1.1.1/deployment/installation_hierarchical_structure.md b/versioned_docs/version-1.1.1/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.1.1/deployment/installation_hierarchical_structure.md
rename to versioned_docs/version-1.1.1/deployment/installation-hierarchical-structure.md
diff --git a/versioned_docs/version-1.1.1/deployment/involve_skywalking_into_linkis.md b/versioned_docs/version-1.1.1/deployment/involve-skywalking-into-linkis.md
similarity index 100%
rename from versioned_docs/version-1.1.1/deployment/involve_skywalking_into_linkis.md
rename to versioned_docs/version-1.1.1/deployment/involve-skywalking-into-linkis.md
diff --git a/versioned_docs/version-1.1.2/deployment/linkis_scriptis_install.md b/versioned_docs/version-1.1.1/deployment/linkis-scriptis-install.md
similarity index 99%
rename from versioned_docs/version-1.1.2/deployment/linkis_scriptis_install.md
rename to versioned_docs/version-1.1.1/deployment/linkis-scriptis-install.md
index d86b292cf1..b2a991fe93 100644
--- a/versioned_docs/version-1.1.2/deployment/linkis_scriptis_install.md
+++ b/versioned_docs/version-1.1.1/deployment/linkis-scriptis-install.md
@@ -7,7 +7,7 @@ sidebar_position: 10
> On linkis1.0 and DSS 1.1 After X, scriptpis can be deployed separately to integrate with linkis. Using the interactive analysis function of scriptis, you can write SQL, pyspark, hiveql and other scripts online on the web page, submit them to linkis for execution, and support UDF, functions, resource control, user-defined variables and other features. This article will introduce how to deploy the web component scriptis separately, and use linkis through such a web page as scriptis.
:::caution be careful
-Premise: the linkis service (back-end and management console services) has been successfully installed and can be used normally. See [rapid deployment of linkis] (deployment/quick_deploy) for the deployment process of linkis
+Premise: the linkis service (back-end and management console services) has been successfully installed and can be used normally. See [rapid deployment of linkis] (deployment/quick-deploy) for the deployment process of linkis
Example description:
- The address of the linkis gateway service is 10.10.10.10 and the port is 9001
- The management console nginx of linkis is deployed on port 8080 of 10.10.10.10
diff --git a/versioned_docs/version-1.1.1/deployment/quick_deploy.md b/versioned_docs/version-1.1.1/deployment/quick-deploy.md
similarity index 99%
rename from versioned_docs/version-1.1.1/deployment/quick_deploy.md
rename to versioned_docs/version-1.1.1/deployment/quick-deploy.md
index 2def9be4c0..81800bb0c7 100644
--- a/versioned_docs/version-1.1.1/deployment/quick_deploy.md
+++ b/versioned_docs/version-1.1.1/deployment/quick-deploy.md
@@ -8,7 +8,7 @@ sidebar_position: 1
Because the mysql-connector-java driver is under the GPL2.0 agreement and does not meet the license policy of the Apache open source agreement, starting from version 1.0.3, the official deployment package of the Apache version is provided. The default is no mysql-connector-java-x.x.x.jar dependency package. You need to add dependencies to the corresponding lib package during installation and deployment.
</font>
-If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md).
+If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md).
Please note: Apart from the four EngineConnPlugins included in the Linkis 1.0 installation package by default: Python/Shell/Hive/Spark. You can manually install other types of engines such as JDBC depending on your own needs. For details, please refer to EngineConnPlugin installation documents.
diff --git a/versioned_docs/version-1.1.1/deployment/sourcecode_hierarchical_structure.md b/versioned_docs/version-1.1.1/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.1.1/deployment/sourcecode_hierarchical_structure.md
rename to versioned_docs/version-1.1.1/deployment/sourcecode-hierarchical-structure.md
diff --git a/versioned_docs/version-1.1.1/deployment/start_metadatasource.md b/versioned_docs/version-1.1.1/deployment/start-metadatasource.md
similarity index 100%
rename from versioned_docs/version-1.1.1/deployment/start_metadatasource.md
rename to versioned_docs/version-1.1.1/deployment/start-metadatasource.md
diff --git a/versioned_docs/version-1.1.1/deployment/unpack_hierarchical_structure.md b/versioned_docs/version-1.1.1/deployment/unpack-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.1.1/deployment/unpack_hierarchical_structure.md
rename to versioned_docs/version-1.1.1/deployment/unpack-hierarchical-structure.md
diff --git a/versioned_docs/version-1.1.1/deployment/web_install.md b/versioned_docs/version-1.1.1/deployment/web-install.md
similarity index 99%
rename from versioned_docs/version-1.1.1/deployment/web_install.md
rename to versioned_docs/version-1.1.1/deployment/web-install.md
index 38f9e471be..6e91d7ef11 100644
--- a/versioned_docs/version-1.1.1/deployment/web_install.md
+++ b/versioned_docs/version-1.1.1/deployment/web-install.md
@@ -3,7 +3,7 @@ title: Linkis Console Deployment
sidebar_position: 6
---
-Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick_deploy.md)
+Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick-deploy.md)
## 1. Preparation
diff --git a/docs/development/linkis_compile_and_package.md b/versioned_docs/version-1.1.1/development/linkis-compile-and-package.md
similarity index 98%
rename from docs/development/linkis_compile_and_package.md
rename to versioned_docs/version-1.1.1/development/linkis-compile-and-package.md
index f90db5fd2f..50c1a4a279 100644
--- a/docs/development/linkis_compile_and_package.md
+++ b/versioned_docs/version-1.1.1/development/linkis-compile-and-package.md
@@ -108,7 +108,7 @@ Get the installation package, there will be a compiled package in the ->target d
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/linkis-engineplugin-spark-x.x.x.jar
```
-How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine_conn_plugin_installation)
+How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine-conn-plugin-installation)
## 5. How to modify the Hadoop, Hive, and Spark versions that Linkis depends on
diff --git a/versioned_docs/version-1.1.1/development/linkis_config.md b/versioned_docs/version-1.1.1/development/linkis-config.md
similarity index 100%
rename from versioned_docs/version-1.1.1/development/linkis_config.md
rename to versioned_docs/version-1.1.1/development/linkis-config.md
diff --git a/versioned_docs/version-1.1.1/development/linkis_debug_in_mac.md b/versioned_docs/version-1.1.1/development/linkis-debug-in-mac.md
similarity index 100%
rename from versioned_docs/version-1.1.1/development/linkis_debug_in_mac.md
rename to versioned_docs/version-1.1.1/development/linkis-debug-in-mac.md
diff --git a/versioned_docs/version-1.1.1/development/linkis_debug.md b/versioned_docs/version-1.1.1/development/linkis-debug.md
similarity index 100%
rename from versioned_docs/version-1.1.1/development/linkis_debug.md
rename to versioned_docs/version-1.1.1/development/linkis-debug.md
diff --git a/versioned_docs/version-1.1.1/development/new_engine_conn.md b/versioned_docs/version-1.1.1/development/new-engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.1.1/development/new_engine_conn.md
rename to versioned_docs/version-1.1.1/development/new-engine-conn.md
diff --git a/versioned_docs/version-1.1.1/development/web_build.md b/versioned_docs/version-1.1.1/development/web-build.md
similarity index 100%
rename from versioned_docs/version-1.1.1/development/web_build.md
rename to versioned_docs/version-1.1.1/development/web-build.md
diff --git a/versioned_docs/version-1.1.1/engine_usage/flink.md b/versioned_docs/version-1.1.1/engine_usage/flink.md
index 2e61249144..535264d7ba 100644
--- a/versioned_docs/version-1.1.1/engine_usage/flink.md
+++ b/versioned_docs/version-1.1.1/engine_usage/flink.md
@@ -56,13 +56,13 @@ cd ${LINKIS_HOME}/sbin
sh linkis-daemon restart cg-engineplugin
```
A more detailed introduction to engineplugin can be found in the following article.
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Flink engine tags
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. The use of Flink engine
@@ -115,7 +115,7 @@ After Linkis 1.0, a cli method is provided to submit tasks. We only need to spec
sh ./bin/linkis-cli -engineType flink-1.12.2 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-For specific usage, please refer to: [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+For specific usage, please refer to: [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 OnceEngineConn method
diff --git a/versioned_docs/version-1.1.1/engine_usage/hive.md b/versioned_docs/version-1.1.1/engine_usage/hive.md
index bc52ab4846..b685701af7 100644
--- a/versioned_docs/version-1.1.1/engine_usage/hive.md
+++ b/versioned_docs/version-1.1.1/engine_usage/hive.md
@@ -32,13 +32,13 @@ Other hive operating modes are similar, just copy the corresponding dependencies
If you have already compiled your hive engineConn plug-in has been compiled, then you need to put the new plug-in in the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Linkis adds Hive console parameters(optional)
Linkis can configure the corresponding EngineConn parameters on the management console. If your newly added EngineConn needs this feature, you can refer to the following documents:
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of hive engineConn
@@ -54,7 +54,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -69,7 +69,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.1/engine_usage/jdbc.md b/versioned_docs/version-1.1.1/engine_usage/jdbc.md
index 1db1d63951..47d84a6aab 100644
--- a/versioned_docs/version-1.1.1/engine_usage/jdbc.md
+++ b/versioned_docs/version-1.1.1/engine_usage/jdbc.md
@@ -43,7 +43,7 @@ wds.linkis.jdbc.password
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -58,7 +58,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.1/engine_usage/openlookeng.md b/versioned_docs/version-1.1.1/engine_usage/openlookeng.md
index 80586220b8..c6f0898347 100644
--- a/versioned_docs/version-1.1.1/engine_usage/openlookeng.md
+++ b/versioned_docs/version-1.1.1/engine_usage/openlookeng.md
@@ -47,7 +47,7 @@ sh linkis-daemon restart cg-engineplugin
Linkis1.X is done through tags, so we need to insert data into our database, and the insertion method is as follows.
-[EngineConnPlugin engine plugin installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin engine plugin installation](../deployment/engine-conn-plugin-installation)
## 3 The use of the engine
@@ -84,7 +84,7 @@ Example of http request parameters
### 3.1 Using Linkis SDK
-Linkis provides Java and Scala SDKs to submit tasks to the Linkis server. For details, please refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides Java and Scala SDKs to submit tasks to the Linkis server. For details, please refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
For the openlookeng task, you only need to modify the EngineConnType and CodeType parameters in the Demo:
````java
@@ -100,4 +100,4 @@ After Linkis 1.0, the cli method is provided to submit tasks. We only need to sp
```shell
sh ./bin/linkis-cli -engineType openlookeng-1.5.0 -codeType sql -code 'show databases;' -submitUser hadoop -proxyUser hadoop
````
-For specific usage, please refer to: [Linkis CLI Manual](user_guide/linkiscli_manual.md).
\ No newline at end of file
+For specific usage, please refer to: [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.1/engine_usage/pipeline.md b/versioned_docs/version-1.1.1/engine_usage/pipeline.md
index 7017c50c6f..978b801630 100644
--- a/versioned_docs/version-1.1.1/engine_usage/pipeline.md
+++ b/versioned_docs/version-1.1.1/engine_usage/pipeline.md
@@ -62,7 +62,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
Linkis1.XIt is carried out through labels, so it is necessary to insert data into our database. The insertion method is shown below.
-[EngineConnPlugin Engine plug-in installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Engine plug-in installation](../deployment/engine-conn-plugin-installation)
## 2 Use of engine
@@ -76,7 +76,7 @@ sh bin/linkis-cli -submitUser hadoop -engineType pipeline-1 -codeType pipelin
```
from hdfs:///000/000/000/A.dolphin to file:///000/000/000/B.csv 3.3 Explained
-For specific use, please refer to： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+For specific use, please refer to： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
because`pipeline`The engine is mainly used to import and export files. Now let's assume that importing files from a to B is the most introduced case
diff --git a/versioned_docs/version-1.1.1/engine_usage/python.md b/versioned_docs/version-1.1.1/engine_usage/python.md
index 97ee168c13..5cc6fb2418 100644
--- a/versioned_docs/version-1.1.1/engine_usage/python.md
+++ b/versioned_docs/version-1.1.1/engine_usage/python.md
@@ -39,7 +39,7 @@ Before submitting python on linkis, you only need to make sure that there is pyt
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -54,7 +54,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.1/engine_usage/shell.md b/versioned_docs/version-1.1.1/engine_usage/shell.md
index d99a4ca96e..3296981943 100644
--- a/versioned_docs/version-1.1.1/engine_usage/shell.md
+++ b/versioned_docs/version-1.1.1/engine_usage/shell.md
@@ -37,7 +37,7 @@ Before submitting the shell on linkis, you only need to ensure that there is the
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -52,7 +52,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.1/engine_usage/spark.md b/versioned_docs/version-1.1.1/engine_usage/spark.md
index 106ebce8f7..5bde17587c 100644
--- a/versioned_docs/version-1.1.1/engine_usage/spark.md
+++ b/versioned_docs/version-1.1.1/engine_usage/spark.md
@@ -34,13 +34,13 @@ In theory, Linkis1.0 supports all versions of spark2.x and above. Spark 2.4.3 is
If you have already compiled your spark EngineConn plug-in has been compiled, then you need to put the new plug-in to the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 tags of spark EngineConn
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of spark EngineConn
@@ -56,7 +56,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -72,7 +72,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
## codeType py-->pyspark sql-->sparkSQL scala-->Spark scala
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.1/introduction.md b/versioned_docs/version-1.1.1/introduction.md
index e72932ac7c..443fd72bbf 100644
--- a/versioned_docs/version-1.1.1/introduction.md
+++ b/versioned_docs/version-1.1.1/introduction.md
@@ -51,8 +51,8 @@ Since the first release of Linkis in 2019, it has accumulated more than **700**
Please go to the [Linkis releases page](https://github.com/apache/incubator-linkis/releases) to download a compiled distribution or a source code package of Linkis.
## Compile and deploy
-Please follow [Compile Guide](development/linkis_compile_and_package.md) to compile Linkis from source code.
-Please refer to [Deployment_Documents](deployment/quick_deploy.md) to do the deployment.
+Please follow [Compile Guide](development/linkis-compile-and-package.md) to compile Linkis from source code.
+Please refer to [Deployment_Documents](deployment/quick-deploy.md) to do the deployment.
## Examples and Guidance
You can find examples and guidance for how to use and manage Linkis in [User_Manual](user_guide/overview.md), [Engine_Usage_Documents](engine_usage/overview.md) and [API_Documents](api/overview.md).
diff --git a/versioned_docs/version-1.1.1/release.md b/versioned_docs/version-1.1.1/release.md
index 6201e7c563..fc5bb9a76d 100644
--- a/versioned_docs/version-1.1.1/release.md
+++ b/versioned_docs/version-1.1.1/release.md
@@ -2,7 +2,7 @@
title: Version overview
sidebar_position: 0.1
---
-- [Introduction of Proxy User Mode](/architecture/proxy_user.md)
+- [Introduction of Proxy User Mode](/architecture/proxy-user.md)
- [UDF function introduction and usage guide](/user_guide/udf.md)
- [Engine material refresh HTTP interface](/api/http/engineconn-plugin-refesh.md)
- [UDF related HTTP interface](/api/http/udf-api.md)
diff --git a/versioned_docs/version-1.1.1/tuning_and_troubleshooting/error_guide/error_code.md b/versioned_docs/version-1.1.1/tuning_and_troubleshooting/error_guide/error-code.md
similarity index 100%
rename from versioned_docs/version-1.1.1/tuning_and_troubleshooting/error_guide/error_code.md
rename to versioned_docs/version-1.1.1/tuning_and_troubleshooting/error_guide/error-code.md
diff --git a/versioned_docs/version-1.1.1/tuning_and_troubleshooting/overview.md b/versioned_docs/version-1.1.1/tuning_and_troubleshooting/overview.md
index 1211422047..3d2ba065a5 100644
--- a/versioned_docs/version-1.1.1/tuning_and_troubleshooting/overview.md
+++ b/versioned_docs/version-1.1.1/tuning_and_troubleshooting/overview.md
@@ -100,4 +100,4 @@ For problems that cannot be resolved according to the above process positioning
### Ⅵ. locate the source code by remote debug
-Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode_hierarchical_structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
+Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode-hierarchical-structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.1/upgrade/upgrade_from_0.X_to_1.0_guide.md b/versioned_docs/version-1.1.1/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 95%
rename from versioned_docs/version-1.1.1/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to versioned_docs/version-1.1.1/upgrade/upgrade-from-0.X-to-1.0-guide.md
index d030c2aca9..6c16652529 100644
--- a/versioned_docs/version-1.1.1/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/versioned_docs/version-1.1.1/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 3
## 1.Precautions
- **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md)**.
+ **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md)**.
## 2. Service upgrade installation
@@ -15,7 +15,7 @@ sidebar_position: 3
If you need to keep 0.X data during the upgrade, you must select 1 to skip the table building statement (see the code below).
- For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ source linkis_configuration_dml.sql
## 4. Installation and startup Linkis1.0
- Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
diff --git a/versioned_docs/version-1.1.1/upgrade/upgrade_guide.md b/versioned_docs/version-1.1.1/upgrade/upgrade-guide.md
similarity index 98%
rename from versioned_docs/version-1.1.1/upgrade/upgrade_guide.md
rename to versioned_docs/version-1.1.1/upgrade/upgrade-guide.md
index eaa72e78a3..230c516eba 100644
--- a/versioned_docs/version-1.1.1/upgrade/upgrade_guide.md
+++ b/versioned_docs/version-1.1.1/upgrade/upgrade-guide.md
@@ -18,7 +18,7 @@ sidebar_position: 2
## 2 Service upgrade installation
-Press [Deployment guide document](../deployment/quick_deploy) (the installation of the management console in the document can be skipped) to install the new version.
+Press [Deployment guide document](../deployment/quick-deploy) (the installation of the management console in the document can be skipped) to install the new version.
When installing the service, if the historical data is retained, please retain the historical data, if you do not need to retain the data, just reinstall it directly
```shell script
diff --git a/versioned_docs/version-1.1.1/user_guide/console_manual.md b/versioned_docs/version-1.1.1/user_guide/console-manual.md
similarity index 100%
rename from versioned_docs/version-1.1.1/user_guide/console_manual.md
rename to versioned_docs/version-1.1.1/user_guide/console-manual.md
diff --git a/docs/user_guide/how_to_use.md b/versioned_docs/version-1.1.1/user_guide/how-to-use.md
similarity index 94%
copy from docs/user_guide/how_to_use.md
copy to versioned_docs/version-1.1.1/user_guide/how-to-use.md
index a7654d58ce..8d84c4ec80 100644
--- a/docs/user_guide/how_to_use.md
+++ b/versioned_docs/version-1.1.1/user_guide/how-to-use.md
@@ -10,9 +10,9 @@ sidebar_position: 1
## 1. Client side usage
If you need to connect to other applications on the basis of Linkis, you need to develop the interface provided by Linkis. Linkis provides a variety of client access interfaces. For detailed usage introduction, please refer to the following:
-- [**Restful API Usage**](api/linkis_task_operator.md)
-- [**JDBC API Usage**](api/jdbc_api.md)
-- [**How to use Java SDK**](user_guide/sdk_manual.md)
+- [**Restful API Usage**](api/linkis-task-operator.md)
+- [**JDBC API Usage**](api/jdbc-api.md)
+- [**How to use Java SDK**](../user_guide/sdk-manual.md)
## 2. Scriptis uses Linkis
diff --git a/versioned_docs/version-1.1.1/user_guide/how_to_use.md b/versioned_docs/version-1.1.1/user_guide/how_to_use.md
deleted file mode 100644
index a7654d58ce..0000000000
--- a/versioned_docs/version-1.1.1/user_guide/how_to_use.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: How to Use
-sidebar_position: 1
----
-
-# How to use Linkis?
-
- In order to meet the needs of different usage scenarios, Linkis provides a variety of usage and access methods, which can be summarized into three categories, namely Client-side use, Scriptis-side use, and DataSphere It is used on the Studio side, among which Scriptis and DataSphere Studio are the open source data analysis platforms of the WeBank Big Data Platform Room. Since these two projects are essentially compatible with Linkis, it is [...]
-
-## 1. Client side usage
-
- If you need to connect to other applications on the basis of Linkis, you need to develop the interface provided by Linkis. Linkis provides a variety of client access interfaces. For detailed usage introduction, please refer to the following:
-- [**Restful API Usage**](api/linkis_task_operator.md)
-- [**JDBC API Usage**](api/jdbc_api.md)
-- [**How to use Java SDK**](user_guide/sdk_manual.md)
-
-## 2. Scriptis uses Linkis
-
- If you need to use Linkis to complete interactive online analysis and processing, and you do not need data analysis application tools such as workflow development, workflow scheduling, data services, etc., you can Install [**Scriptis**](https://github.com/WeBankFinTech/Scriptis) separately. For detailed installation tutorial, please refer to its corresponding installation and deployment documents.
-
-## 2.1. Use Scriptis to execute scripts
-
- Currently Scriptis supports submitting a variety of task types to Linkis, including Spark SQL, Hive SQL, Scala, PythonSpark, etc. In order to meet the needs of data analysis, the left side of Scriptis, Provides viewing user workspace information, user database and table information, user-defined functions, and HDFS directories. It also supports uploading and downloading, result set exporting and other functions. Scriptis is very simple to u [...]
-
-
-## 2.2. Scriptis Management Console
-
- Linkis provides an interface for resource configuration and management. If you want to configure and manage task resources, you can set it on the Scriptis management console interface, including queue settings and resource configuration , The number of engine instances, etc. Through the management console, you can easily configure the resources for submitting tasks to Linkis, making it more convenient and faster.
-
-
-## 3. DataSphere Studio uses Linkis
-
- [**DataSphere Studio**](https://github.com/WeBankFinTech/DataSphereStudio), referred to as DSS, is an open source part of WeBank’s big data platform Station-type data analysis and processing platform, the DSS interactive analysis module integrates Scriptis. Using DSS for interactive analysis is the same as Scriptis. In addition to providing the basic functions of Scriptis, DSS provides and integrates richer and more powerful data analysis f [...]
-
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.1/user_guide/linkiscli_manual.md b/versioned_docs/version-1.1.1/user_guide/linkiscli-manual.md
similarity index 100%
rename from versioned_docs/version-1.1.1/user_guide/linkiscli_manual.md
rename to versioned_docs/version-1.1.1/user_guide/linkiscli-manual.md
diff --git a/versioned_docs/version-1.1.1/user_guide/overview.md b/versioned_docs/version-1.1.1/user_guide/overview.md
index 2a6d4b1b9b..3aa5f4450a 100644
--- a/versioned_docs/version-1.1.1/user_guide/overview.md
+++ b/versioned_docs/version-1.1.1/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis considered the scalability of the access method at the beginning of the design. For different access scenarios, Linkis provides front-end access and SDK access. HTTP and WebSocket interfaces are also provided on the basis of front-end interfaces. If you are interested in accessing and using Linkis, you can refer to the following documents:
-- [How to Use Links](how_to_use.md)
-- [Linkis Management Console Manual](console_manual.md)
-- [Linkis1.0 SDK Manual](sdk_manual.md)
-- [Linkis-Cli Manual](linkiscli_manual.md)
+- [How to Use Links](how-to-use.md)
+- [Linkis Management Console Manual](console-manual.md)
+- [Linkis1.0 SDK Manual](sdk-manual.md)
+- [Linkis-Cli Manual](linkiscli-manual.md)
diff --git a/versioned_docs/version-1.1.1/user_guide/sdk_manual.md b/versioned_docs/version-1.1.1/user_guide/sdk-manual.md
similarity index 100%
rename from versioned_docs/version-1.1.1/user_guide/sdk_manual.md
rename to versioned_docs/version-1.1.1/user_guide/sdk-manual.md
diff --git a/versioned_docs/version-1.1.2/api/jdbc_api.md b/versioned_docs/version-1.1.2/api/jdbc-api.md
similarity index 100%
rename from versioned_docs/version-1.1.2/api/jdbc_api.md
rename to versioned_docs/version-1.1.2/api/jdbc-api.md
diff --git a/versioned_docs/version-1.1.2/api/linkis_task_operator.md b/versioned_docs/version-1.1.2/api/linkis-task-operator.md
similarity index 100%
rename from versioned_docs/version-1.1.2/api/linkis_task_operator.md
rename to versioned_docs/version-1.1.2/api/linkis-task-operator.md
diff --git a/versioned_docs/version-1.1.2/api/login_api.md b/versioned_docs/version-1.1.2/api/login-api.md
similarity index 100%
rename from versioned_docs/version-1.1.2/api/login_api.md
rename to versioned_docs/version-1.1.2/api/login-api.md
diff --git a/versioned_docs/version-1.1.2/api/overview.md b/versioned_docs/version-1.1.2/api/overview.md
index 60a92418bb..3f08075bde 100644
--- a/versioned_docs/version-1.1.2/api/overview.md
+++ b/versioned_docs/version-1.1.2/api/overview.md
@@ -6,8 +6,8 @@ sidebar_position: 0
## 1. Document description
Linkis1.0 has been refactored and optimized on the basis of Linkix0.x, and it is also compatible with the 0.x interface. However, in order to prevent compatibility problems when using version 1.0, you need to read the following documents carefully:
-1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login_api.md) carefully.
+1. When using Linkis1.0 for customized development, you need to use Linkis's authorization authentication interface. Please read [Login API Document](login-api.md) carefully.
-2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc_api.md).
+2. Linkis1.0 provides a JDBC interface. You need to use JDBC to access Linkis. Please read [Task Submit and Execute JDBC API Document](jdbc-api.md).
-3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis_task_operator.md).
\ No newline at end of file
+3. Linkis1.0 provides the Rest interface. If you need to develop upper-level applications on the basis of Linkis, please read [Task Submit and Execute Rest API Document](linkis-task-operator.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.2/architecture/commons/message_scheduler.md b/versioned_docs/version-1.1.2/architecture/commons/message-scheduler.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/commons/message_scheduler.md
rename to versioned_docs/version-1.1.2/architecture/commons/message-scheduler.md
diff --git a/versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/add_an_engine_conn.md b/versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/add-an-engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/add_an_engine_conn.md
rename to versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/add-an-engine-conn.md
diff --git a/versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn_manager.md b/versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn_manager.md
rename to versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn-manager.md
diff --git a/versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn_plugin.md b/versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn-plugin.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn_plugin.md
rename to versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn-plugin.md
diff --git a/versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn.md b/versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine_conn.md
rename to versioned_docs/version-1.1.2/architecture/computation_governance_services/engine/engine-conn.md
diff --git a/versioned_docs/version-1.1.2/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md b/versioned_docs/version-1.1.2/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
similarity index 99%
rename from versioned_docs/version-1.1.2/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md
rename to versioned_docs/version-1.1.2/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
index 1eab642967..abff385e2a 100644
--- a/versioned_docs/version-1.1.2/architecture/computation_governance_services/job_submission_preparation_and_execution_process.md
+++ b/versioned_docs/version-1.1.2/architecture/computation_governance_services/job-submission-preparation-and-execution-process.md
@@ -30,7 +30,7 @@ The submission phase is mainly the interaction of Client -> Linkis Gateway -> En
-1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](user_guide/how_to_use.md)):
+1. First, the Client (such as the front end or the client) initiates a Job request, and the job request information is simplified as follows (for the specific usage of Linkis, please refer to [How to use Linkis](../../user_guide/how-to-use.md)):
```
POST /api/rest_j/v1/entrance/submit
```
@@ -62,7 +62,7 @@ If the user has a reusable EngineConn in LinkisManager, the EngineConn is direct
How to define a reusable EngineConn? It refers to those that can match all the label requirements of the computing task, and the EngineConn's own health status is Healthy (the load is low and the actual status is Idle). Then, all the EngineConn that meets the conditions are sorted and selected according to the rules, and finally the best one is locked.
-If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](engine/add_an_engine_conn.md).
+If the user does not have a reusable EngineConn, a process to request a new EngineConn will be triggered at this time. Regarding the process, please refer to: [How to add an EngineConn](engine/add-an-engine-conn.md).
#### 2.2 Orchestrate a computing task
diff --git a/versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/app_manager.md b/versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/app-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/app_manager.md
rename to versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/app-manager.md
diff --git a/versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/label_manager.md b/versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/label-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/label_manager.md
rename to versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/label-manager.md
diff --git a/versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/resource_manager.md b/versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/resource-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/resource_manager.md
rename to versioned_docs/version-1.1.2/architecture/computation_governance_services/linkis_manager/resource-manager.md
diff --git a/versioned_docs/version-1.1.2/architecture/computation_governance_services/overview.md b/versioned_docs/version-1.1.2/architecture/computation_governance_services/overview.md
index 80c421ad74..9446468701 100644
--- a/versioned_docs/version-1.1.2/architecture/computation_governance_services/overview.md
+++ b/versioned_docs/version-1.1.2/architecture/computation_governance_services/overview.md
@@ -44,7 +44,7 @@ Perform three stages to fully upgrade Linkis's Job execution architecture, as sh
[Enter LinkisManager Architecture Design](linkis_manager/overview.md)
### 4. Engine Manager
Engine conn Manager (ECM) is a simplified and upgraded version of linkis0. X engine manager. The ECM under linkis1.0 removes the application ability of the engine, and the whole microservice is completely stateless. It will focus on supporting the startup and destruction of all kinds of enginecon.
-[Enter EngineConnManager Architecture Design](engine/engine_conn_manager.md)
+[Enter EngineConnManager Architecture Design](engine/engine-conn-manager.md)
### 5. EngineConn
EngineConn is an optimized and upgraded version of Linkis0.X Engine. It will provide EngineConn and Executor two modules. EngineConn is used to connect the underlying computing storage engine and provide a session session that connects the underlying computing storage engines; Executor is based on this Session session , Provide full-stack computing support for interactive computing, streaming computing, offline computing, and data storage.
- [Enter EngineConn Architecture Design](engine/engine_conn.md)
+ [Enter EngineConn Architecture Design](engine/engine-conn.md)
diff --git a/versioned_docs/version-1.1.2/architecture/computation_governance_services/proxy_user.md b/versioned_docs/version-1.1.2/architecture/computation_governance_services/proxy-user.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/computation_governance_services/proxy_user.md
rename to versioned_docs/version-1.1.2/architecture/computation_governance_services/proxy-user.md
diff --git a/versioned_docs/version-1.1.2/architecture/difference_between_1.0_and_0.x.md b/versioned_docs/version-1.1.2/architecture/difference-between-1.0-and-0.x.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/difference_between_1.0_and_0.x.md
rename to versioned_docs/version-1.1.2/architecture/difference-between-1.0-and-0.x.md
diff --git a/versioned_docs/version-1.1.2/architecture/overview.md b/versioned_docs/version-1.1.2/architecture/overview.md
index 3a45df32c6..e3efc03e13 100644
--- a/versioned_docs/version-1.1.2/architecture/overview.md
+++ b/versioned_docs/version-1.1.2/architecture/overview.md
@@ -15,7 +15,7 @@ The specific responsibilities of each category are as follows:
The following is a directory listing of Linkis1.0 architecture documents:
-1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference_between_1.0_and_0.x.md).
+1. The characteristics of Linkis1.0's architecture , please read [The difference between Linkis1.0 and Linkis0.x](difference-between-1.0-and-0.x.md).
2. Linkis 1.0 public enhancement service related documents, please read [Public Enhancement Service](public_enhancement_services/overview.md).
3. Linkis 1.0 microservice governance related documents, please read [Microservice Governance](microservice_governance_services/overview.md).
4. Linkis 1.0 computing governance service related documents, please read [Computation Governance Service](computation_governance_services/overview.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/bml/engine_bml_dissect.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/bml/engine-bml-dissect.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/bml/engine_bml_dissect.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/bml/engine-bml-dissect.md
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_cache.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-cache.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_cache.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-cache.md
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_client.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-client.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_client.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-client.md
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_highavailable.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-highavailable.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_highavailable.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-highavailable.md
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_listener.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-listener.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_listener.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-listener.md
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_persistence.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-persistence.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_persistence.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-persistence.md
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_search.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-search.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service_search.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service-search.md
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context_service.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/context-service.md
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/overview.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/overview.md
index 4fae9dfbab..d44f182f29 100644
--- a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/overview.md
+++ b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/context_service/overview.md
@@ -101,28 +101,28 @@ The runtime workflow is mainly used by Linkis.
### 1. Client
The entrance of external access to CS, Client module provides HA function;
-[Enter Client Architecture Design](context_service_client.md)
+[Enter Client Architecture Design](context-service-client.md)
### 2. Service Module
Provide a Restful interface to encapsulate and process CS requests submitted by the client;
-[Enter Service Architecture Design](context_service.md)
+[Enter Service Architecture Design](context-service.md)
### 3. ContextSearch
The context query module provides rich and powerful query capabilities for the client to find the key-value key-value pairs of the context;
-[Enter ContextSearch architecture design](context_service_search.md)
+[Enter ContextSearch architecture design](context-service-search.md)
### 4. Listener
The CS listener module provides synchronous and asynchronous event consumption capabilities, and has the ability to notify the Client in real time once the Zookeeper-like Key-Value is updated;
-[Enter Listener architecture design](context_service_listener.md)
+[Enter Listener architecture design](context-service-listener.md)
### 5. ContextCache
The context memory cache module provides the ability to quickly retrieve the context and the ability to monitor and clean up JVM memory usage;
-[Enter ContextCache architecture design](context_service_cache.md)
+[Enter ContextCache architecture design](context-service-cache.md)
### 6. HighAvailable
Provide CS high availability capability;
-[Enter HighAvailable architecture design](context_service_highavailable.md)
+[Enter HighAvailable architecture design](context-service-highavailable.md)
### 7. Persistence
The persistence function of CS;
-[Enter Persistence architecture design](context_service_persistence.md)
\ No newline at end of file
+[Enter Persistence architecture design](context-service-persistence.md)
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/datasource_manager.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/datasource-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/datasource_manager.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/datasource-manager.md
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/metadata_manager.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/metadata-manager.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/metadata_manager.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/metadata-manager.md
diff --git a/versioned_docs/version-1.1.2/architecture/public_enhancement_services/public_service.md b/versioned_docs/version-1.1.2/architecture/public_enhancement_services/public-service.md
similarity index 100%
rename from versioned_docs/version-1.1.2/architecture/public_enhancement_services/public_service.md
rename to versioned_docs/version-1.1.2/architecture/public_enhancement_services/public-service.md
diff --git a/versioned_docs/version-1.1.2/deployment/cluster_deployment.md b/versioned_docs/version-1.1.2/deployment/cluster-deployment.md
similarity index 100%
rename from versioned_docs/version-1.1.2/deployment/cluster_deployment.md
rename to versioned_docs/version-1.1.2/deployment/cluster-deployment.md
diff --git a/versioned_docs/version-1.1.2/deployment/deploy_linkis_without_hdfs.md b/versioned_docs/version-1.1.2/deployment/deploy-linkis-without-hdfs.md
similarity index 100%
rename from versioned_docs/version-1.1.2/deployment/deploy_linkis_without_hdfs.md
rename to versioned_docs/version-1.1.2/deployment/deploy-linkis-without-hdfs.md
diff --git a/versioned_docs/version-1.1.2/deployment/engine_conn_plugin_installation.md b/versioned_docs/version-1.1.2/deployment/engine-conn-plugin-installation.md
similarity index 100%
rename from versioned_docs/version-1.1.2/deployment/engine_conn_plugin_installation.md
rename to versioned_docs/version-1.1.2/deployment/engine-conn-plugin-installation.md
diff --git a/versioned_docs/version-1.1.2/deployment/installation_hierarchical_structure.md b/versioned_docs/version-1.1.2/deployment/installation-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.1.2/deployment/installation_hierarchical_structure.md
rename to versioned_docs/version-1.1.2/deployment/installation-hierarchical-structure.md
diff --git a/versioned_docs/version-1.1.2/deployment/involve_skywalking_into_linkis.md b/versioned_docs/version-1.1.2/deployment/involve-skywalking-into-linkis.md
similarity index 100%
rename from versioned_docs/version-1.1.2/deployment/involve_skywalking_into_linkis.md
rename to versioned_docs/version-1.1.2/deployment/involve-skywalking-into-linkis.md
diff --git a/versioned_docs/version-1.1.1/deployment/linkis_scriptis_install.md b/versioned_docs/version-1.1.2/deployment/linkis-scriptis-install.md
similarity index 99%
rename from versioned_docs/version-1.1.1/deployment/linkis_scriptis_install.md
rename to versioned_docs/version-1.1.2/deployment/linkis-scriptis-install.md
index d86b292cf1..b2a991fe93 100644
--- a/versioned_docs/version-1.1.1/deployment/linkis_scriptis_install.md
+++ b/versioned_docs/version-1.1.2/deployment/linkis-scriptis-install.md
@@ -7,7 +7,7 @@ sidebar_position: 10
> On linkis1.0 and DSS 1.1 After X, scriptpis can be deployed separately to integrate with linkis. Using the interactive analysis function of scriptis, you can write SQL, pyspark, hiveql and other scripts online on the web page, submit them to linkis for execution, and support UDF, functions, resource control, user-defined variables and other features. This article will introduce how to deploy the web component scriptis separately, and use linkis through such a web page as scriptis.
:::caution be careful
-Premise: the linkis service (back-end and management console services) has been successfully installed and can be used normally. See [rapid deployment of linkis] (deployment/quick_deploy) for the deployment process of linkis
+Premise: the linkis service (back-end and management console services) has been successfully installed and can be used normally. See [rapid deployment of linkis] (deployment/quick-deploy) for the deployment process of linkis
Example description:
- The address of the linkis gateway service is 10.10.10.10 and the port is 9001
- The management console nginx of linkis is deployed on port 8080 of 10.10.10.10
diff --git a/versioned_docs/version-1.1.2/deployment/quick_deploy.md b/versioned_docs/version-1.1.2/deployment/quick-deploy.md
similarity index 99%
rename from versioned_docs/version-1.1.2/deployment/quick_deploy.md
rename to versioned_docs/version-1.1.2/deployment/quick-deploy.md
index d6d39c25b3..cbe0b15760 100644
--- a/versioned_docs/version-1.1.2/deployment/quick_deploy.md
+++ b/versioned_docs/version-1.1.2/deployment/quick-deploy.md
@@ -8,7 +8,7 @@ sidebar_position: 1
Because the mysql-connector-java driver is under the GPL2.0 agreement and does not meet the license policy of the Apache open source agreement, starting from version 1.0.3, the official deployment package of the Apache version is provided. The default is no mysql-connector-java-x.x.x.jar dependency package. You need to add dependencies to the corresponding lib package during installation and deployment.
</font>
-If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md).
+If you are new to Linkis, you can ignore this chapter, however, if you are already a Linkis user, we recommend you reading the following article before installing or upgrading: [Brief introduction of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md).
Please note: Apart from the four EngineConnPlugins included in the Linkis 1.0 installation package by default: Python/Shell/Hive/Spark. You can manually install other types of engines such as JDBC depending on your own needs. For details, please refer to EngineConnPlugin installation documents.
diff --git a/versioned_docs/version-1.1.2/deployment/sourcecode_hierarchical_structure.md b/versioned_docs/version-1.1.2/deployment/sourcecode-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.1.2/deployment/sourcecode_hierarchical_structure.md
rename to versioned_docs/version-1.1.2/deployment/sourcecode-hierarchical-structure.md
diff --git a/versioned_docs/version-1.1.2/deployment/start_metadatasource.md b/versioned_docs/version-1.1.2/deployment/start-metadatasource.md
similarity index 100%
rename from versioned_docs/version-1.1.2/deployment/start_metadatasource.md
rename to versioned_docs/version-1.1.2/deployment/start-metadatasource.md
diff --git a/versioned_docs/version-1.1.2/deployment/unpack_hierarchical_structure.md b/versioned_docs/version-1.1.2/deployment/unpack-hierarchical-structure.md
similarity index 100%
rename from versioned_docs/version-1.1.2/deployment/unpack_hierarchical_structure.md
rename to versioned_docs/version-1.1.2/deployment/unpack-hierarchical-structure.md
diff --git a/versioned_docs/version-1.0.3/deployment/web_install.md b/versioned_docs/version-1.1.2/deployment/web-install.md
similarity index 99%
rename from versioned_docs/version-1.0.3/deployment/web_install.md
rename to versioned_docs/version-1.1.2/deployment/web-install.md
index 38f9e471be..6e91d7ef11 100644
--- a/versioned_docs/version-1.0.3/deployment/web_install.md
+++ b/versioned_docs/version-1.1.2/deployment/web-install.md
@@ -3,7 +3,7 @@ title: Linkis Console Deployment
sidebar_position: 6
---
-Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick_deploy.md)
+Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick-deploy.md)
## 1. Preparation
diff --git a/versioned_docs/version-1.1.2/deployment/web_install.md b/versioned_docs/version-1.1.2/deployment/web_install.md
deleted file mode 100644
index 38f9e471be..0000000000
--- a/versioned_docs/version-1.1.2/deployment/web_install.md
+++ /dev/null
@@ -1,115 +0,0 @@
----
-title: Linkis Console Deployment
-sidebar_position: 6
----
-
-Linkis 1.0 provides a Linkis Console, which provides functions such as displaying Linkis' global history, modifying user parameters, managing ECM and microservices, etc. Before deploying the front-end management console, you need to deploy the Linkis back-end. Linkis deployment manual See: [Linkis Deployment Manual](deployment/quick_deploy.md)
-
-## 1. Preparation
-
-1. Download the web installation package from the release page of Linkis ([click here to enter the download page](https://linkis.apache.org/download/main/)), apache-linkis-xxx-incubating-web-bin. tar.gz
-Manually decompress: tar -xvf apache-linkis-x.x.x-incubating-web-bin.tar.gz, the decompressed directory is:
-```
-config.sh
-dist
-install.sh
-....
-```
-
-## 2. Deployment
- There are two deployment methods, automated deployment and manual deployment
-
-### 2.1 Automated deployment
- Enter the unzipped front-end directory, and edit ```vi config.sh ``` in the directory
-Change the front-end port and back-end interface address, the back-end interface address is the gateway address of Linkis.
-
-```$xslt
-#Configuring front-end ports
-linkis_port="8088"
-
-#URL of the backend linkis gateway
-linkis_url="http://localhost:9001"
-
-#linkis ip address
-linkis_ipaddr=$(ip addr | awk'/^[0-9]+: / {}; /inet.*global/ {print gensub(/(.*)\/(.*)/, "\\1" , "g", $2)}')
-```
-
-After the modification is executed in this directory, you need to use sudo to execute: ```sudo sh install.sh ```
-
-After execution, you can directly access it in Google browser: ```http://linkis_ipaddr:linkis_port``` where linkis_port is the port configured in config.sh, and linkis_ipaddr is the IP of the installation machine
-
-If the access fails: You can check the installation log which step went wrong
-
-### 2.2 Manual deployment
-1. Install Nginx: ```sudo yum install nginx -y```
-
-2. Modify the configuration file: sudo vi /etc/nginx/conf.d/linkis.conf
-Add the following content:
-```
-server {
- listen 8080;# access port
- server_name localhost;
- #charset koi8-r;
- #access_log /var/log/nginx/host.access.log main;
- location / {
- root /appcom/Install/linkis/dist; # The directory where the front-end package is decompressed
- index index.html index.html;
- }
-
- location /api {
- proxy_pass http://192.168.xxx.xxx:9001; # ip port of linkis-gateway service
- proxy_set_header Host $host;
- proxy_set_header X-Real-IP $remote_addr;
- proxy_set_header x_real_ipP $remote_addr;
- proxy_set_header remote_addr $remote_addr;
- proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
- proxy_http_version 1.1;
- proxy_connect_timeout 4s;
- proxy_read_timeout 600s;
- proxy_send_timeout 12s;
- proxy_set_header Upgrade $http_upgrade;
- proxy_set_header Connection upgrade;
- }
- #error_page 404 /404.html;
- # redirect server error pages to the static page /50x.html
- #
- error_page 500 502 503 504 /50x.html;
- location = /50x.html {
- root /usr/share/nginx/html;
- }
- }
-
-```
-
-3. Copy the front-end package to the corresponding directory: ```/appcom/Install/linkis/dist; # The directory where the front-end package is decompressed ```
-
-4. Start the service ```sudo systemctl restart nginx```
-
-5. After execution, you can directly access it in Google browser: ```http://nginx_ip:nginx_port```
-
-## 3. Common problems
-
-(1) Upload file size limit
-
-```
-sudo vi /etc/nginx/nginx.conf
-```
-
-Change upload size
-
-```
-client_max_body_size 200m
-```
-
- (2) Interface timeout
-
-```
-sudo vi /etc/nginx/conf.d/linkis.conf
-```
-
-
-Change interface timeout
-
-```
-proxy_read_timeout 600s
-```
\ No newline at end of file
diff --git a/versioned_docs/version-1.0.3/development/linkis_compile_and_package.md b/versioned_docs/version-1.1.2/development/linkis-compile-and-package.md
similarity index 98%
rename from versioned_docs/version-1.0.3/development/linkis_compile_and_package.md
rename to versioned_docs/version-1.1.2/development/linkis-compile-and-package.md
index f90db5fd2f..50c1a4a279 100644
--- a/versioned_docs/version-1.0.3/development/linkis_compile_and_package.md
+++ b/versioned_docs/version-1.1.2/development/linkis-compile-and-package.md
@@ -108,7 +108,7 @@ Get the installation package, there will be a compiled package in the ->target d
incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/linkis-engineplugin-spark-x.x.x.jar
```
-How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine_conn_plugin_installation)
+How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine-conn-plugin-installation)
## 5. How to modify the Hadoop, Hive, and Spark versions that Linkis depends on
diff --git a/versioned_docs/version-1.1.2/development/linkis_config.md b/versioned_docs/version-1.1.2/development/linkis-config.md
similarity index 100%
rename from versioned_docs/version-1.1.2/development/linkis_config.md
rename to versioned_docs/version-1.1.2/development/linkis-config.md
diff --git a/versioned_docs/version-1.1.2/development/linkis_debug_in_mac.md b/versioned_docs/version-1.1.2/development/linkis-debug-in-mac.md
similarity index 100%
rename from versioned_docs/version-1.1.2/development/linkis_debug_in_mac.md
rename to versioned_docs/version-1.1.2/development/linkis-debug-in-mac.md
diff --git a/versioned_docs/version-1.1.2/development/linkis_debug.md b/versioned_docs/version-1.1.2/development/linkis-debug.md
similarity index 100%
rename from versioned_docs/version-1.1.2/development/linkis_debug.md
rename to versioned_docs/version-1.1.2/development/linkis-debug.md
diff --git a/versioned_docs/version-1.1.2/development/linkis_compile_and_package.md b/versioned_docs/version-1.1.2/development/linkis_compile_and_package.md
deleted file mode 100644
index f90db5fd2f..0000000000
--- a/versioned_docs/version-1.1.2/development/linkis_compile_and_package.md
+++ /dev/null
@@ -1,177 +0,0 @@
----
-title: Compile And Package
-sidebar_position: 1
----
-
-## 1. Preparation
-**Environment requirements:** Version of JDK must be higher then **JDK8**, **Oracle/Sun** and **OpenJDK** are both supported.
-
-After obtaining the project code from [github repository](https://github.com/apache/incubator-linkis) https://github.com/apache/incubator-linkis, use maven to compile the project installation package.
-
-### 1.1 Source code acquisition
-
-- Method 1: Obtain the source code of the project from [github repository](https://github.com/apache/incubator-linkis) https://github.com/apache/incubator-linkis.
-- Method 2: Download the source code package of the required version from the [linkis official download page](https://linkis.apache.org/download/main) https://linkis.apache.org/download/main.
-
-**Notice** : The official recommended versions for compiling Linkis are hadoop-2.7.2, hive-1.2.1, spark-2.4.3, and Scala-2.11.12.
-
-If you want to compile Linkis with another version of Hadoop, Hive, Spark, please refer to: [How to Modify Linkis dependency of Hadoop, Hive, Spark](#5 How to Modify Linkis dependency versionof Hadoop, Hive, Spark)
-
-### <font color="red">1.2 Modify dependency configuration</font>
-:::caution Note
-Because the mysql-connector-java driver is under the GPL2.0 agreement and does not meet the license policy of the Apache open source agreement, starting from version 1.0.3, the scope of the dependency on mysql-connector-java is test by default. If you compile by yourself , You can modify the scope scope that the mysql-connector-java of the top-level pom.xml depends on (just comment it out)
-:::
-```xml
-<dependency>
- <groupId>mysql</groupId>
- <artifactId>mysql-connector-java</artifactId>
- <version>${mysql.connector.version}</version>
- <!--<scope>test</scope>-->
-</dependency>
-```
-
-## 2. Fully compile Linkis
-
-
-
-### step1 Compile for the first time (not the first time you can skip this step)
-
-**If you are compiling and using it locally for the first time, you must first execute the following command in the root directory of the Linkis source code package**:
-```bash
- cd incubator-linkis-x.x.x
- mvn -N install
-```
-
-### step2 Execute compilation
-Execute the following commands in the root directory of the Linkis source code package:
-
-```bash
- cd incubator-linkis-x.x.x
- mvn clean install
-
-```
-
-### step3 Obtain the installation package
-The compiled complete installation package is in the assembly-combined-package->target directory of the project:
-
-```bash
- #Detailed path is as follows
- incubator-linkis-x.x.x/assembly-combined-package/target/apache-linkis-x.x.x-incubating-bin.tar.gz
-```
-
-## 3. Compile a single module
-
-### step1 Compile for the first time (skip this step for non-first time)
-**If you are compiling and using it locally for the first time, you must first execute the following command in the root directory of the Linkis source code package**:
-
-```bash
- cd incubator-linkis-x.x.x
- mvn -N install
-```
-### step2 Enter the corresponding module to compile
-Enter the corresponding module to compile, for example, if you want to recompile Entrance, the command is as follows:
-
-```bash
- cd incubator-linkis-x.x.x/linkis-computation-governance/linkis-entrance
- mvn clean install
-```
-
-### step3 Obtain the installation package
-Get the installation package, there will be a compiled package in the ->target directory of the corresponding module:
-
-```
- incubator-linkis-x.x.x/linkis-computation-governance/linkis-entrance/target/linkis-entrance.x.x.x.jar
-```
-
-## 4. Compile an engine
-
-Here's an example of the Spark engine that builds Linkis:
-
-### step1 Compile for the first time (skip this step for non-first time)
-**If you are using it locally for the first time, you must first execute the following command in the root directory of the Linkis source code package**:
-
-```bash
- cd incubator-linkis-x.x.x
- mvn -N install
-```
-### step2 Enter the corresponding module to compile
-Enter the directory where the Spark engine is located to compile and package, the command is as follows:
-
-```bash
- cd incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark
- mvn clean install
-```
-### step3 Obtain the installation package
-Get the installation package, there will be a compiled package in the ->target directory of the corresponding module:
-
-```
- incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark/target/linkis-engineplugin-spark-x.x.x.jar
-```
-
-How to install Spark engine separately? Please refer to [Linkis Engine Plugin Installation Document](../deployment/engine_conn_plugin_installation)
-
-## 5. How to modify the Hadoop, Hive, and Spark versions that Linkis depends on
-
-Please note: Hadoop is a big data basic service, Linkis must rely on Hadoop for compilation;
-If you don't want to use an engine, you don't need to set the version of the engine or compile the engine plug-in.
-
-Specifically, the version of Hadoop can be modified in a different way than Spark, Hive, and other computing engines, as described below:
-
-### 5.1 How to modify the Hadoop version that Linkis depends on
-
-Enter the source package root directory of Linkis, and manually modify the Hadoop version information of the pom.xml file, as follows:
-
-```bash
- cd incubator-linkis-x.x.x
- vim pom.xml
-```
-
-```xml
- <properties>
-
- <hadoop.version>2.7.2</hadoop.version> <!--> Modify the Hadoop version number here <-->
- <scala.version>2.11.12</scala.version>
- <jdk.compile.version>1.8</jdk.compile.version>
-
- </properties>
-```
-
-**Please note: If your hadoop version is hadoop3, you need to modify the pom file of linkis-hadoop-common**
-Because under hadoop2.8, hdfs-related classes are in the hadoop-hdfs module, but in hadoop 3.X the corresponding classes are moved to the module hadoop-hdfs-client, you need to modify this file:
-pom:Linkis/linkis-commons/linkis-hadoop-common/pom.xml
-Modify the dependency hadoop-hdfs to hadoop-hdfs-client:
-```
- <dependency>
- <groupId>org.apache.hadoop</groupId>
- <artifactId>hadoop-hdfs</artifactId> <!-- Just replace this line with <artifactId>hadoop-hdfs-client</artifactId>-->
- <version>${hadoop.version}</version>
-</dependency>
- Modify hadoop-hdfs to:
- <dependency>
- <groupId>org.apache.hadoop</groupId>
- <artifactId>hadoop-hdfs-client</artifactId>
- <version>${hadoop.version}</version>
-</dependency>
-```
-
-### 5.2 How to modify the Spark and Hive versions that Linkis depends on
-
-Here's an example of changing the version of Spark. Go to the directory where the Spark engine is located and manually modify the Spark version information of the pom.xml file as follows:
-
-```bash
- cd incubator-linkis-x.x.x/linkis-engineconn-plugins/engineconn-plugins/spark
- vim pom.xml
-```
-
-```xml
- <properties>
- <spark.version>2.4.3</spark.version> <!--> Modify the Spark version number here <-->
- </properties>
-```
-
-Modifying the version of other engines is similar to modifying the Spark version. First, enter the directory where the relevant engine is located, and manually modify the engine version information in the pom.xml file.
-
-Then please refer to [4. Compile an engine](#4-compile-an-engine)
-
-
-
diff --git a/versioned_docs/version-1.1.2/development/new_engine_conn.md b/versioned_docs/version-1.1.2/development/new-engine-conn.md
similarity index 100%
rename from versioned_docs/version-1.1.2/development/new_engine_conn.md
rename to versioned_docs/version-1.1.2/development/new-engine-conn.md
diff --git a/versioned_docs/version-1.1.2/development/web_build.md b/versioned_docs/version-1.1.2/development/web-build.md
similarity index 100%
rename from versioned_docs/version-1.1.2/development/web_build.md
rename to versioned_docs/version-1.1.2/development/web-build.md
diff --git a/versioned_docs/version-1.1.2/engine_usage/flink.md b/versioned_docs/version-1.1.2/engine_usage/flink.md
index 2e61249144..535264d7ba 100644
--- a/versioned_docs/version-1.1.2/engine_usage/flink.md
+++ b/versioned_docs/version-1.1.2/engine_usage/flink.md
@@ -56,13 +56,13 @@ cd ${LINKIS_HOME}/sbin
sh linkis-daemon restart cg-engineplugin
```
A more detailed introduction to engineplugin can be found in the following article.
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Flink engine tags
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. The use of Flink engine
@@ -115,7 +115,7 @@ After Linkis 1.0, a cli method is provided to submit tasks. We only need to spec
sh ./bin/linkis-cli -engineType flink-1.12.2 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-For specific usage, please refer to: [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+For specific usage, please refer to: [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 OnceEngineConn method
diff --git a/versioned_docs/version-1.1.2/engine_usage/hive.md b/versioned_docs/version-1.1.2/engine_usage/hive.md
index bc52ab4846..b685701af7 100644
--- a/versioned_docs/version-1.1.2/engine_usage/hive.md
+++ b/versioned_docs/version-1.1.2/engine_usage/hive.md
@@ -32,13 +32,13 @@ Other hive operating modes are similar, just copy the corresponding dependencies
If you have already compiled your hive engineConn plug-in has been compiled, then you need to put the new plug-in in the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 Linkis adds Hive console parameters(optional)
Linkis can configure the corresponding EngineConn parameters on the management console. If your newly added EngineConn needs this feature, you can refer to the following documents:
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of hive engineConn
@@ -54,7 +54,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call hive tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -69,7 +69,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.2/engine_usage/jdbc.md b/versioned_docs/version-1.1.2/engine_usage/jdbc.md
index 1db1d63951..47d84a6aab 100644
--- a/versioned_docs/version-1.1.2/engine_usage/jdbc.md
+++ b/versioned_docs/version-1.1.2/engine_usage/jdbc.md
@@ -43,7 +43,7 @@ wds.linkis.jdbc.password
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call jdbc tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -58,7 +58,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType jdbc-4 -codeType jdbc -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.2/engine_usage/openlookeng.md b/versioned_docs/version-1.1.2/engine_usage/openlookeng.md
index 80586220b8..c6f0898347 100644
--- a/versioned_docs/version-1.1.2/engine_usage/openlookeng.md
+++ b/versioned_docs/version-1.1.2/engine_usage/openlookeng.md
@@ -47,7 +47,7 @@ sh linkis-daemon restart cg-engineplugin
Linkis1.X is done through tags, so we need to insert data into our database, and the insertion method is as follows.
-[EngineConnPlugin engine plugin installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin engine plugin installation](../deployment/engine-conn-plugin-installation)
## 3 The use of the engine
@@ -84,7 +84,7 @@ Example of http request parameters
### 3.1 Using Linkis SDK
-Linkis provides Java and Scala SDKs to submit tasks to the Linkis server. For details, please refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides Java and Scala SDKs to submit tasks to the Linkis server. For details, please refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
For the openlookeng task, you only need to modify the EngineConnType and CodeType parameters in the Demo:
````java
@@ -100,4 +100,4 @@ After Linkis 1.0, the cli method is provided to submit tasks. We only need to sp
```shell
sh ./bin/linkis-cli -engineType openlookeng-1.5.0 -codeType sql -code 'show databases;' -submitUser hadoop -proxyUser hadoop
````
-For specific usage, please refer to: [Linkis CLI Manual](user_guide/linkiscli_manual.md).
\ No newline at end of file
+For specific usage, please refer to: [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.2/engine_usage/pipeline.md b/versioned_docs/version-1.1.2/engine_usage/pipeline.md
index 5a3710bcf5..284ffc937a 100644
--- a/versioned_docs/version-1.1.2/engine_usage/pipeline.md
+++ b/versioned_docs/version-1.1.2/engine_usage/pipeline.md
@@ -62,7 +62,7 @@ select * from linkis_cg_engine_conn_plugin_bml_resources
Linkis1.XIt is carried out through labels, so it is necessary to insert data into our database. The insertion method is shown below.
-[EngineConnPlugin Engine plug-in installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Engine plug-in installation](../deployment/engine-conn-plugin-installation)
## 2 Use of engine
@@ -76,7 +76,7 @@ sh bin/linkis-cli -submitUser hadoop -engineType pipeline-1 -codeType pipelin
```
from hdfs:///000/000/000/A.dolphin to file:///000/000/000/B.csv 3.3 Explained
-For specific use, please refer to： [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+For specific use, please refer to： [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
because`pipeline`The engine is mainly used to import and export files. Now let's assume that importing files from a to B is the most introduced case
diff --git a/versioned_docs/version-1.1.2/engine_usage/python.md b/versioned_docs/version-1.1.2/engine_usage/python.md
index 97ee168c13..5cc6fb2418 100644
--- a/versioned_docs/version-1.1.2/engine_usage/python.md
+++ b/versioned_docs/version-1.1.2/engine_usage/python.md
@@ -39,7 +39,7 @@ Before submitting python on linkis, you only need to make sure that there is pyt
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call python tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -54,7 +54,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType python-python2 -codeType python -code "print(\"hello\")" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.2/engine_usage/shell.md b/versioned_docs/version-1.1.2/engine_usage/shell.md
index d99a4ca96e..3296981943 100644
--- a/versioned_docs/version-1.1.2/engine_usage/shell.md
+++ b/versioned_docs/version-1.1.2/engine_usage/shell.md
@@ -37,7 +37,7 @@ Before submitting the shell on linkis, you only need to ensure that there is the
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call shell tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -52,7 +52,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
```shell
sh ./bin/linkis-cli -engineType shell-1 -codeType shell -code "echo \"hello\" " -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.2/engine_usage/spark.md b/versioned_docs/version-1.1.2/engine_usage/spark.md
index 106ebce8f7..5bde17587c 100644
--- a/versioned_docs/version-1.1.2/engine_usage/spark.md
+++ b/versioned_docs/version-1.1.2/engine_usage/spark.md
@@ -34,13 +34,13 @@ In theory, Linkis1.0 supports all versions of spark2.x and above. Spark 2.4.3 is
If you have already compiled your spark EngineConn plug-in has been compiled, then you need to put the new plug-in to the specified location to load, you can refer to the following article for details
-[EngineConnPlugin Installation](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation](../deployment/engine-conn-plugin-installation)
### 2.3 tags of spark EngineConn
Linkis1.0 is done through tags, so we need to insert data in our database, the way of inserting is shown below.
-[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine_conn_plugin_installation)
+[EngineConnPlugin Installation > 2.2 Configuration modification of management console (optional)](../deployment/engine-conn-plugin-installation)
## 3. Use of spark EngineConn
@@ -56,7 +56,7 @@ You can also add the queue value in the StartUpMap of the submission parameter:
### 3.1 How to use Linkis SDK
-Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](user_guide/sdk_manual.md).
+Linkis provides a client method to call Spark tasks. The call method is through the SDK provided by LinkisClient. We provide java and scala two ways to call, the specific usage can refer to [JAVA SDK Manual](../user_guide/sdk-manual.md).
If you use Hive, you only need to make the following changes:
```java
Map<String, Object> labels = new HashMap<String, Object>();
@@ -72,7 +72,7 @@ After Linkis 1.0, you can submit tasks through cli. We only need to specify the
## codeType py-->pyspark sql-->sparkSQL scala-->Spark scala
sh ./bin/linkis-cli -engineType spark-2.4.3 -codeType sql -code "show tables" -submitUser hadoop -proxyUser hadoop
```
-The specific usage can refer to [Linkis CLI Manual](user_guide/linkiscli_manual.md).
+The specific usage can refer to [Linkis CLI Manual](../user_guide/linkiscli-manual.md).
### 3.3 How to use Scriptis
diff --git a/versioned_docs/version-1.1.2/engine_usage/sqoop.md b/versioned_docs/version-1.1.2/engine_usage/sqoop.md
index ece1612c76..f8b062d363 100644
--- a/versioned_docs/version-1.1.2/engine_usage/sqoop.md
+++ b/versioned_docs/version-1.1.2/engine_usage/sqoop.md
@@ -60,7 +60,7 @@ cd ${LINKIS_HOME}/sbin
sh linkis-daemon.sh restart cg-engineplugin
```
More engineplugin details can be found in the following article.
-https://linkis.apache.org/zh-CN/docs/1.1.1/deployment/engine_conn_plugin_installation
+https://linkis.apache.org/zh-CN/docs/1.1.1/deployment/engine-conn-plugin-installation
## 3.Sqoop Engine Usage
diff --git a/versioned_docs/version-1.1.2/introduction.md b/versioned_docs/version-1.1.2/introduction.md
index e72932ac7c..443fd72bbf 100644
--- a/versioned_docs/version-1.1.2/introduction.md
+++ b/versioned_docs/version-1.1.2/introduction.md
@@ -51,8 +51,8 @@ Since the first release of Linkis in 2019, it has accumulated more than **700**
Please go to the [Linkis releases page](https://github.com/apache/incubator-linkis/releases) to download a compiled distribution or a source code package of Linkis.
## Compile and deploy
-Please follow [Compile Guide](development/linkis_compile_and_package.md) to compile Linkis from source code.
-Please refer to [Deployment_Documents](deployment/quick_deploy.md) to do the deployment.
+Please follow [Compile Guide](development/linkis-compile-and-package.md) to compile Linkis from source code.
+Please refer to [Deployment_Documents](deployment/quick-deploy.md) to do the deployment.
## Examples and Guidance
You can find examples and guidance for how to use and manage Linkis in [User_Manual](user_guide/overview.md), [Engine_Usage_Documents](engine_usage/overview.md) and [API_Documents](api/overview.md).
diff --git a/versioned_docs/version-1.1.2/release.md b/versioned_docs/version-1.1.2/release.md
index 902ddeb713..c640384a34 100644
--- a/versioned_docs/version-1.1.2/release.md
+++ b/versioned_docs/version-1.1.2/release.md
@@ -3,10 +3,10 @@ title: Version Overview
sidebar_position: 0.1
---
-- [Lite Deployment Without HDFS Mode](/deployment/deploy_linkis_without_hdfs.md)
+- [Lite Deployment Without HDFS Mode](/deployment/deploy-linkis-without-hdfs.md)
- [Sqoop Engine Usage](/engine_usage/sqoop.md)
- [History Task Query HTTP Interface](/api/http/linkis-ps-publicservice-api/jobhistory-api.md)
-- [Installation And Deployment of Tool Scriptis](/deployment/linkis_scriptis_install.md)
+- [Installation And Deployment of Tool Scriptis](/deployment/linkis-scriptis-install.md)
- [Release-Notes](/download/release-notes-1.1.2)
## Configuration Item
diff --git a/versioned_docs/version-1.1.2/tuning_and_troubleshooting/overview.md b/versioned_docs/version-1.1.2/tuning_and_troubleshooting/overview.md
index 1211422047..3d2ba065a5 100644
--- a/versioned_docs/version-1.1.2/tuning_and_troubleshooting/overview.md
+++ b/versioned_docs/version-1.1.2/tuning_and_troubleshooting/overview.md
@@ -100,4 +100,4 @@ For problems that cannot be resolved according to the above process positioning
### Ⅵ. locate the source code by remote debug
-Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode_hierarchical_structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
+Under normal circumstances, remote debugging of source code is the most effective way to locate problems, but compared to document review, users need to have a certain understanding of the source code structure. It is recommended that you check the [Linkis source code level detailed structure](deployment/sourcecode-hierarchical-structure.md) in the Linkis WIKI before remote debugging.After having a certain degree of familiarity to the the source code structure of the project, after a cer [...]
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.0/upgrade/upgrade_from_0.X_to_1.0_guide.md b/versioned_docs/version-1.1.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
similarity index 95%
rename from versioned_docs/version-1.1.0/upgrade/upgrade_from_0.X_to_1.0_guide.md
rename to versioned_docs/version-1.1.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
index 447bc141b1..60c1bed5a9 100644
--- a/versioned_docs/version-1.1.0/upgrade/upgrade_from_0.X_to_1.0_guide.md
+++ b/versioned_docs/version-1.1.2/upgrade/upgrade-from-0.X-to-1.0-guide.md
@@ -7,7 +7,7 @@ sidebar_position: 1
## 1.Precautions
- **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference_between_1.0_and_0.x.md)**.
+ **If you are using Linkis for the first time, you can ignore this chapter; if you are already a user of Linkis, it is recommended to read it before installing or upgrading：[Brief description of the difference between Linkis1.0 and Linkis0.X](architecture/difference-between-1.0-and-0.x.md)**.
## 2. Service upgrade installation
@@ -15,7 +15,7 @@ sidebar_position: 1
If you need to keep 0.X data during the upgrade, you must select 1 to skip the table building statement (see the code below).
- For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ For the installation of Linkis1.0, please refer to [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
```
Do you want to clear Linkis table information in the database?
@@ -75,4 +75,4 @@ source linkis_configuration_dml.sql
## 4. Installation and startup Linkis1.0
- Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick_deploy.md)
+ Start Linkis 1.0 to verify whether the service has been started normally and provide external services. For details, please refer to: [Quick Deployment Linkis1.0](deployment/quick-deploy.md)
diff --git a/versioned_docs/version-1.1.2/upgrade/upgrade_guide.md b/versioned_docs/version-1.1.2/upgrade/upgrade-guide.md
similarity index 98%
rename from versioned_docs/version-1.1.2/upgrade/upgrade_guide.md
rename to versioned_docs/version-1.1.2/upgrade/upgrade-guide.md
index eaa72e78a3..230c516eba 100644
--- a/versioned_docs/version-1.1.2/upgrade/upgrade_guide.md
+++ b/versioned_docs/version-1.1.2/upgrade/upgrade-guide.md
@@ -18,7 +18,7 @@ sidebar_position: 2
## 2 Service upgrade installation
-Press [Deployment guide document](../deployment/quick_deploy) (the installation of the management console in the document can be skipped) to install the new version.
+Press [Deployment guide document](../deployment/quick-deploy) (the installation of the management console in the document can be skipped) to install the new version.
When installing the service, if the historical data is retained, please retain the historical data, if you do not need to retain the data, just reinstall it directly
```shell script
diff --git a/versioned_docs/version-1.1.2/user_guide/console_manual.md b/versioned_docs/version-1.1.2/user_guide/console-manual.md
similarity index 100%
rename from versioned_docs/version-1.1.2/user_guide/console_manual.md
rename to versioned_docs/version-1.1.2/user_guide/console-manual.md
diff --git a/docs/user_guide/how_to_use.md b/versioned_docs/version-1.1.2/user_guide/how-to-use.md
similarity index 94%
rename from docs/user_guide/how_to_use.md
rename to versioned_docs/version-1.1.2/user_guide/how-to-use.md
index a7654d58ce..8d84c4ec80 100644
--- a/docs/user_guide/how_to_use.md
+++ b/versioned_docs/version-1.1.2/user_guide/how-to-use.md
@@ -10,9 +10,9 @@ sidebar_position: 1
## 1. Client side usage
If you need to connect to other applications on the basis of Linkis, you need to develop the interface provided by Linkis. Linkis provides a variety of client access interfaces. For detailed usage introduction, please refer to the following:
-- [**Restful API Usage**](api/linkis_task_operator.md)
-- [**JDBC API Usage**](api/jdbc_api.md)
-- [**How to use Java SDK**](user_guide/sdk_manual.md)
+- [**Restful API Usage**](api/linkis-task-operator.md)
+- [**JDBC API Usage**](api/jdbc-api.md)
+- [**How to use Java SDK**](../user_guide/sdk-manual.md)
## 2. Scriptis uses Linkis
diff --git a/versioned_docs/version-1.1.2/user_guide/how_to_use.md b/versioned_docs/version-1.1.2/user_guide/how_to_use.md
deleted file mode 100644
index a7654d58ce..0000000000
--- a/versioned_docs/version-1.1.2/user_guide/how_to_use.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: How to Use
-sidebar_position: 1
----
-
-# How to use Linkis?
-
- In order to meet the needs of different usage scenarios, Linkis provides a variety of usage and access methods, which can be summarized into three categories, namely Client-side use, Scriptis-side use, and DataSphere It is used on the Studio side, among which Scriptis and DataSphere Studio are the open source data analysis platforms of the WeBank Big Data Platform Room. Since these two projects are essentially compatible with Linkis, it is [...]
-
-## 1. Client side usage
-
- If you need to connect to other applications on the basis of Linkis, you need to develop the interface provided by Linkis. Linkis provides a variety of client access interfaces. For detailed usage introduction, please refer to the following:
-- [**Restful API Usage**](api/linkis_task_operator.md)
-- [**JDBC API Usage**](api/jdbc_api.md)
-- [**How to use Java SDK**](user_guide/sdk_manual.md)
-
-## 2. Scriptis uses Linkis
-
- If you need to use Linkis to complete interactive online analysis and processing, and you do not need data analysis application tools such as workflow development, workflow scheduling, data services, etc., you can Install [**Scriptis**](https://github.com/WeBankFinTech/Scriptis) separately. For detailed installation tutorial, please refer to its corresponding installation and deployment documents.
-
-## 2.1. Use Scriptis to execute scripts
-
- Currently Scriptis supports submitting a variety of task types to Linkis, including Spark SQL, Hive SQL, Scala, PythonSpark, etc. In order to meet the needs of data analysis, the left side of Scriptis, Provides viewing user workspace information, user database and table information, user-defined functions, and HDFS directories. It also supports uploading and downloading, result set exporting and other functions. Scriptis is very simple to u [...]
-
-
-## 2.2. Scriptis Management Console
-
- Linkis provides an interface for resource configuration and management. If you want to configure and manage task resources, you can set it on the Scriptis management console interface, including queue settings and resource configuration , The number of engine instances, etc. Through the management console, you can easily configure the resources for submitting tasks to Linkis, making it more convenient and faster.
-
-
-## 3. DataSphere Studio uses Linkis
-
- [**DataSphere Studio**](https://github.com/WeBankFinTech/DataSphereStudio), referred to as DSS, is an open source part of WeBank’s big data platform Station-type data analysis and processing platform, the DSS interactive analysis module integrates Scriptis. Using DSS for interactive analysis is the same as Scriptis. In addition to providing the basic functions of Scriptis, DSS provides and integrates richer and more powerful data analysis f [...]
-
\ No newline at end of file
diff --git a/versioned_docs/version-1.1.2/user_guide/linkiscli_manual.md b/versioned_docs/version-1.1.2/user_guide/linkiscli-manual.md
similarity index 100%
rename from versioned_docs/version-1.1.2/user_guide/linkiscli_manual.md
rename to versioned_docs/version-1.1.2/user_guide/linkiscli-manual.md
diff --git a/versioned_docs/version-1.1.2/user_guide/overview.md b/versioned_docs/version-1.1.2/user_guide/overview.md
index 2a6d4b1b9b..3aa5f4450a 100644
--- a/versioned_docs/version-1.1.2/user_guide/overview.md
+++ b/versioned_docs/version-1.1.2/user_guide/overview.md
@@ -7,7 +7,7 @@ sidebar_position: 0
Linkis considered the scalability of the access method at the beginning of the design. For different access scenarios, Linkis provides front-end access and SDK access. HTTP and WebSocket interfaces are also provided on the basis of front-end interfaces. If you are interested in accessing and using Linkis, you can refer to the following documents:
-- [How to Use Links](how_to_use.md)
-- [Linkis Management Console Manual](console_manual.md)
-- [Linkis1.0 SDK Manual](sdk_manual.md)
-- [Linkis-Cli Manual](linkiscli_manual.md)
+- [How to Use Links](how-to-use.md)
+- [Linkis Management Console Manual](console-manual.md)
+- [Linkis1.0 SDK Manual](sdk-manual.md)
+- [Linkis-Cli Manual](linkiscli-manual.md)
diff --git a/versioned_docs/version-1.1.2/user_guide/sdk_manual.md b/versioned_docs/version-1.1.2/user_guide/sdk-manual.md
similarity index 100%
rename from versioned_docs/version-1.1.2/user_guide/sdk_manual.md
rename to versioned_docs/version-1.1.2/user_guide/sdk-manual.md
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@linkis.apache.org
For additional commands, e-mail: commits-help@linkis.apache.org