You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@doris.apache.org by ji...@apache.org on 2022/07/25 01:47:55 UTC
[doris-website] branch master updated: link
This is an automated email from the ASF dual-hosted git repository.
jiafengzheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris-website.git
The following commit(s) were added to refs/heads/master by this push:
new c072cce6004 link
c072cce6004 is described below
commit c072cce6004bf06fa3b04fcc372e8caef2952b4d
Author: jiafeng.zhang <zh...@gmail.com>
AuthorDate: Mon Jul 25 09:47:44 2022 +0800
link
---
community/developer-guide/benchmark-tool.md | 2 +-
community/developer-guide/cpp-diagnostic-code.md | 2 +-
community/developer-guide/cpp-format-code.md | 2 +-
community/developer-guide/docker-dev.md | 4 ++--
community/developer-guide/fe-vscode-dev.md | 2 +-
community/how-to-contribute/how-to-contribute.md | 10 +++++-----
docs/install/source-install/compilation.md | 4 +++-
.../current/developer-guide/benchmark-tool.md | 2 +-
.../current/developer-guide/cpp-diagnostic-code.md | 2 +-
.../current/developer-guide/docker-dev.md | 6 +++---
.../current/developer-guide/fe-vscode-dev.md | 2 +-
.../current/install/source-install/compilation.md | 4 +++-
12 files changed, 23 insertions(+), 19 deletions(-)
diff --git a/community/developer-guide/benchmark-tool.md b/community/developer-guide/benchmark-tool.md
index 4a19a44104d..7daf5fc1f73 100644
--- a/community/developer-guide/benchmark-tool.md
+++ b/community/developer-guide/benchmark-tool.md
@@ -33,7 +33,7 @@ It can be used to test the performance of some parts of the BE storage layer (fo
## Compilation
-1. To ensure that the environment has been able to successfully compile the Doris ontology, you can refer to [Installation and deployment](../../../docs/install/source-install/compilation)。
+1. To ensure that the environment has been able to successfully compile the Doris ontology, you can refer to [Installation and deployment](../../docs/install/source-install/compilation)。
2. Execute`run-be-ut.sh`
diff --git a/community/developer-guide/cpp-diagnostic-code.md b/community/developer-guide/cpp-diagnostic-code.md
index cedc1bef05d..fa1178ebb7f 100644
--- a/community/developer-guide/cpp-diagnostic-code.md
+++ b/community/developer-guide/cpp-diagnostic-code.md
@@ -27,7 +27,7 @@ under the License.
# C++ Code Diagnostic
Doris support to use [Clangd](https://clangd.llvm.org/) and [Clang-Tidy](https://clang.llvm.org/extra/clang-tidy/)
-to diagnostic code. Clangd and Clang-Tidy already has in [LDB-toolchain](../../../docs/install/source-install/compilation-with-ldb-toolchain)，also can install by self.
+to diagnostic code. Clangd and Clang-Tidy already has in [LDB-toolchain](../../docs/install/source-install/compilation-with-ldb-toolchain)，also can install by self.
### Clang-Tidy
Clang-Tidy can do some diagnostic cofig, config file `.clang-tidy` is in Doris root path. Compared with vscode-cpptools, clangd can provide more powerful and accurate code jumping for vscode, and integrates the analysis and quick-fix functions of clang-tidy.
diff --git a/community/developer-guide/cpp-format-code.md b/community/developer-guide/cpp-format-code.md
index 569eaacf018..67a6d3a2bcd 100644
--- a/community/developer-guide/cpp-format-code.md
+++ b/community/developer-guide/cpp-format-code.md
@@ -66,7 +66,7 @@ The version of clang-format installed by centos yum is too old and supports too
LDB toolchain:
-If you are using [LDB toolchain](../../../docs/install/source-install/compilation-with-ldb-toolchain),
+If you are using [LDB toolchain](../../docs/install/source-install/compilation-with-ldb-toolchain),
the latest version (>= v0.11) of [LDB toolchain](https://github.com/amosbird/ldb_toolchain_gen/releases) has already included clang-format with 13.0.1 version.
### clang-format plugin
diff --git a/community/developer-guide/docker-dev.md b/community/developer-guide/docker-dev.md
index 6d835170915..c27a5582053 100644
--- a/community/developer-guide/docker-dev.md
+++ b/community/developer-guide/docker-dev.md
@@ -29,8 +29,8 @@ under the License.
## Related detailed document navigation
-- [Developing mirror compilation using Docker](../../../docs/install/source-install/compilation)
-- [Deploying Doris](../../../docs/install/install-deploy)
+- [Developing mirror compilation using Docker](../../docs/install/source-install/compilation)
+- [Deploying Doris](../../docs/install/install-deploy)
- [VSCode Be Development Debugging](./be-vscode-dev)
## Environment preparation
diff --git a/community/developer-guide/fe-vscode-dev.md b/community/developer-guide/fe-vscode-dev.md
index 99337149f46..03d2b26cc55 100644
--- a/community/developer-guide/fe-vscode-dev.md
+++ b/community/developer-guide/fe-vscode-dev.md
@@ -72,7 +72,7 @@ example:
## Build
Other articles have already explained:
-* [Build with LDB toolchain ](../../../docs/install/source-install/compilation-with-ldb-toolchain.md)
+* [Build with LDB toolchain ](../../../docs/install/source-install/compilation-with-ldb-toolchain)
* ......
In order to debug, you need to add debugging parameters when fe starts, such as `-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005` .
diff --git a/community/how-to-contribute/how-to-contribute.md b/community/how-to-contribute/how-to-contribute.md
index dafcb98b92d..edb2c33c026 100644
--- a/community/how-to-contribute/how-to-contribute.md
+++ b/community/how-to-contribute/how-to-contribute.md
@@ -39,7 +39,7 @@ Any questions, you can contact us to get timely answers, including Wechat, Gitte
For the first time in Doris community, you can:
* Follow [Doris Github](https://github.com/apache/doris)
-* Subscribe to our [mailing list](./subscribe-mail-list.md);
+* Subscribe to our [mailing list](./subscribe-mail-list);
* Join Doris Wechat Group (add WeChat-ID: morningman-cmy, note: join Doris Group) and ask questions at any time.
* Enter Doris's [Slack](https://join.slack.com/t/apachedoriscommunity/shared_invite/zt-11jb8gesh-7IukzSrdea6mqoG0HB4gZg)
@@ -68,18 +68,18 @@ Browse the document, you can deepen your understanding of Doris, can also help y
If you are interested in improving the quality of documents, whether it is revising the address of a page, correcting a link, and writing a better introductory document, we are very welcome!
-Most of our documents are written in markdown format, and you can modify and submit document changes directly through `docs/` in [GitHub](https://github.com/apache/doris). If you submit code changes, you can refer to [Pull Request](./pull-request.md).
+Most of our documents are written in markdown format, and you can modify and submit document changes directly through `docs/` in [GitHub](https://github.com/apache/doris). If you submit code changes, you can refer to [Pull Request](./pull-request).
## If a Bug or problem is found
If a Bug or problem is found, you can directly raise a new Issue through GitHub's [Issues](https://github.com/apache/doris/issues/new/choose), and we will have someone deal with it regularly.
-You can also fix it yourself by reading the analysis code (of course, it's better to talk to us before that, maybe someone has fixed the same problem) and submit a [Pull Request](./pull-request.md).
+You can also fix it yourself by reading the analysis code (of course, it's better to talk to us before that, maybe someone has fixed the same problem) and submit a [Pull Request](./pull-request).
## Modify the code and submit PR (Pull Request)
-You can download the code, compile and install it, deploy and run it for a try (refer to the [compilation document](../../install/source-install/compilation.md)) to see if it works as you expected. If you have problems, you can contact us directly, ask questions or fix them by reading and analyzing the source code.
+You can download the code, compile and install it, deploy and run it for a try (refer to the [compilation document](../../install/source-install/compilation)) to see if it works as you expected. If you have problems, you can contact us directly, ask questions or fix them by reading and analyzing the source code.
Whether it's fixing Bugs or adding Features, we're all very welcome. If you want to submit code to Doris, you need to create a new branch for your submitted code from the fork code library on GitHub to your project space, add the source project upstream, and submit PR.
-About how to submit a PR refer to [Pull Request](./pull-request.md).
+About how to submit a PR refer to [Pull Request](./pull-request).
diff --git a/docs/install/source-install/compilation.md b/docs/install/source-install/compilation.md
index f732da45797..90e0fd8e34b 100644
--- a/docs/install/source-install/compilation.md
+++ b/docs/install/source-install/compilation.md
@@ -132,7 +132,9 @@ This document focuses on how to code Doris through source code.
>
> If you are using `build-env-for-0.15.0` or later version for the first time, use the following command when compiling:
>
- > `sh build.sh --clean --be --fe --ui`
+ > `sh build.sh --clean --be --fe --ui --broker`
+ > `build-env-for-1.0.0` and later, use the following command:
+ > `sh build --clean --be --fe --broker`
>
> This is because from build-env-for-0.15.0, we upgraded thrift (0.9 -> 0.13), you need to use the --clean command to force the use of the new version of thrift to generate code files, otherwise incompatible code will appear.
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/benchmark-tool.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/benchmark-tool.md
index 7e9b0c28ed9..1ec669b9e40 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/benchmark-tool.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/benchmark-tool.md
@@ -33,7 +33,7 @@ under the License.
## 编译
-1. 确保环境已经能顺利编译Doris本体,可以参考[编译与部署](../../../docs/install/source-install/compilation)。
+1. 确保环境已经能顺利编译Doris本体,可以参考[编译与部署](../../docs/install/source-install/compilation)。
2. 运行目录下的`run-be-ut.sh`
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/cpp-diagnostic-code.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/cpp-diagnostic-code.md
index ac5565498d4..00e725f7f89 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/cpp-diagnostic-code.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/cpp-diagnostic-code.md
@@ -26,7 +26,7 @@ under the License.
# C++ 代码分析
-Doris支持使用[Clangd](https://clangd.llvm.org/)和[Clang-Tidy](https://clang.llvm.org/extra/clang-tidy/)进行代码静态分析。Clangd和Clang-Tidy在[LDB-toolchain](../../../docs/install/source-install/compilation-with-ldb-toolchain)
+Doris支持使用[Clangd](https://clangd.llvm.org/)和[Clang-Tidy](https://clang.llvm.org/extra/clang-tidy/)进行代码静态分析。Clangd和Clang-Tidy在[LDB-toolchain](../../docs/install/source-install/compilation-with-ldb-toolchain)
中已经内置，另外也可以自己安装或者编译。
### Clang-Tidy
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/docker-dev.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/docker-dev.md
index cea025d64a1..1678be8da28 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/docker-dev.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/docker-dev.md
@@ -29,8 +29,8 @@ under the License.
## 相关详细文档导航
-- [使用 Docker 开发镜像编译](../../../docs/install/source-install/compilation)
-- [部署](../../../docs/install/install-deploy)
+- [使用 Docker 开发镜像编译](../../docs/install/source-install/compilation)
+- [部署](../../docs/install/install-deploy)
- [VSCode Be 开发调试](./be-vscode-dev)
## 环境准备
@@ -90,7 +90,7 @@ docker build -t doris .
运行镜像
-此处按需注意 [挂载的问题](../../docs/install/source-install/compilation)
+此处按需注意 [挂载的问题](../../docs/install/source-install/compilation/)
> 见链接中：建议以挂载本地 Doris 源码目录的方式运行镜像 .....
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/fe-vscode-dev.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/fe-vscode-dev.md
index 80fb8c226d7..0daefed3b3c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/fe-vscode-dev.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/developer-guide/fe-vscode-dev.md
@@ -72,7 +72,7 @@ example:
## 编译
其他文章已经介绍的比较清楚了：
-* [使用 LDB toolchain 编译](../../../docs/install/source-install/compilation-with-ldb-toolchain)
+* [使用 LDB toolchain 编译](../../docs/install/source-install/compilation-with-ldb-toolchain)
* ......
为了进行调试，需要在 fe 启动时，加上调试的参数，比如 `-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005` 。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/source-install/compilation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/source-install/compilation.md
index cc36cb66946..b9aa0d9103c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/source-install/compilation.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/install/source-install/compilation.md
@@ -131,7 +131,9 @@ under the License.
>
>如果你是第一次使用 `build-env-for-0.15.0` 或之后的版本，第一次编译的时候要使用如下命令：
>
- > `sh build.sh --clean --be --fe --ui`
+ > `sh build.sh --clean --be --fe --ui --broker`
+ > `build-env-for-1.0.0` 及之后的版本，使用如下命令：
+ > `sh build --clean --be --fe --broker`
>
> 这是因为 build-env-for-0.15.0 版本镜像升级了 thrift(0.9 -> 0.13)，需要通过 --clean 命令强制使用新版本的 thrift 生成代码文件，否则会出现不兼容的代码。
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org