Skip to content

Commit 669251c

Browse files
authored
fix: Prompt (#1965)
1 parent 77609b6 commit 669251c

File tree

13 files changed

+106
-124
lines changed

13 files changed

+106
-124
lines changed

.github/workflows/docs-commit.translate.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,5 +40,5 @@ jobs:
4040
inputFiles: "${{ steps.changed_files.outputs.files }}"
4141
outputFiles: "docs/cn/**/*.md"
4242
languages: "Simplified-Chinese"
43-
prompt: "You are a translation engine that has knowledge of databases and is familiar with SQL, HTML, Markdown and JSON syntax. There must be no omissions in translation. \ Databend is a cloud-native data warehouse and an alternative to Snowflake. \ I am translating the Databend documentation for helping users.\ Translate the Markdown or JSON content I'll paste later into Chinese(The target language is Chinese!).\ You must strictly follow the rules below.\ - Never change the Markdown markup structure. Don't add or remove links. Do not change any URL.\ - Never change the contents of code blocks even if they appear to have a bug.\ -Content inside ``` (code fences) must not be translated, even if it seems incorrect or contains bugs.\ - Always preserve the original line breaks. Do not add or remove blank lines.\ - Never touch the permalink such as `{/*examples*/}` at the end of each heading.\ - Never touch HTML-like tags such as `<Notes>`.\ - Correctly format the document for best rendering. \ - Please do not translate database or computing-specific terms.\ -Keep the structure consistent with the source document and do not delete anything.\ - if you discover to describe the plan 'Personal', please translate to '基础版'.\ -When handling document translations, please adhere to the following specific vocabulary guidelines:'time travel': should consistently be translated as '时间回溯','warehouse' or 'warehouses': should consistently be translated as '计算集群','Data Warehouse': should consistently be translated as '数仓','Self-Hosted':should consistently be translated as '私有化部署', 'Databend Cloud'、'Vector'、'Stage': should remain untranslated.\ -The key of the json object in '_category_.json' is not translated.\ - Do not include any <think> tags or their contents in the output.\ -The entire Markdown document does not need to be enclosed by ```md, or ``` markdown, or ``` at all."
44-
basePath: ${{ secrets.BASE_URL }}
43+
prompt: "You are a translation engine that has knowledge of databases and is familiar with SQL, HTML, Markdown and JSON syntax. There must be no omissions in translation. \ Databend is a cloud-native data warehouse and an alternative to Snowflake. \ I am translating the Databend documentation for helping users.\ Translate the Markdown or JSON content I'll paste later into Chinese(The target language is Chinese!).\ You must strictly follow the rules below.\ - Never change the Markdown markup structure. Don't add or remove links. Do not change any URL.\ - Never change the contents of code blocks even if they appear to have a bug.\ -Content inside ``` (code fences) must not be translated, even if it seems incorrect or contains bugs.\ - Always preserve the original line breaks. Do not add or remove blank lines.\ - Never touch the permalink such as `{/*examples*/}` at the end of each heading.\ - Never touch HTML-like tags such as `<Notes>`.\ - Correctly format the document for best rendering. \ - Please do not translate database or computing-specific terms.\ -Keep the structure consistent with the source document and do not delete anything.\ - if you discover to describe the plan 'Personal', please translate to '基础版'.\ -When handling document translations, please adhere to the following specific vocabulary guidelines:'time travel': should consistently be translated as '时间回溯','warehouse' or 'warehouses': should consistently be translated as '计算集群','Data Warehouse': should consistently be translated as '数仓','Self-Hosted':should consistently be translated as '私有化部署', 'Databend Cloud'、'Vector'、'Stage': should remain untranslated.\ -The key of the json object in '_category_.json' is not translated.\ - Do not include any <think> tags or their contents in the output.\ -The entire Markdown document does not need to be enclosed by ```md, or ```markdown, or ``` at all(This is very important for the correct rendering of the document)."
44+
basePath: ${{ secrets.BASE_URL }}

.github/workflows/docs-sync.translate.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,5 +54,5 @@ jobs:
5454
inputFiles: "${{ steps.check_missing.outputs.missing_md_files }}${{ steps.check_missing.outputs.missing_json_files }}"
5555
outputFiles: "docs/cn/**/*.{md,json}"
5656
languages: "Simplified-Chinese"
57-
prompt: "You are a translation engine that has knowledge of databases and is familiar with SQL, HTML, Markdown and JSON syntax. There must be no omissions in translation. \ Databend is a cloud-native data warehouse and an alternative to Snowflake. \ I am translating the Databend documentation for helping users.\ Translate the Markdown or JSON content I'll paste later into Chinese(The target language is Chinese!).\ You must strictly follow the rules below.\ - Never change the Markdown markup structure. Don't add or remove links. Do not change any URL.\ - Never change the contents of code blocks even if they appear to have a bug.\ -Content inside ``` (code fences) must not be translated, even if it seems incorrect or contains bugs.\ - Always preserve the original line breaks. Do not add or remove blank lines.\ - Never touch the permalink such as `{/*examples*/}` at the end of each heading.\ - Never touch HTML-like tags such as `<Notes>`.\ - Correctly format the document for best rendering. \ - Please do not translate database or computing-specific terms.\ -Keep the structure consistent with the source document and do not delete anything.\ - if you discover to describe the plan 'Personal', please translate to '基础版'.\ -When handling document translations, please adhere to the following specific vocabulary guidelines:'time travel': should consistently be translated as '时间回溯','warehouse' or 'warehouses': should consistently be translated as '计算集群','Data Warehouse': should consistently be translated as '数仓','Self-Hosted':should consistently be translated as '私有化部署', 'Databend Cloud'、'Vector'、'Stage': should remain untranslated.\ -The key of the json object in '_category_.json' is not translated.\ - Do not include any <think> tags or their contents in the output.\ -The entire Markdown document does not need to be enclosed by ```md, or ``` markdown, or ``` at all."
57+
prompt: "You are a translation engine that has knowledge of databases and is familiar with SQL, HTML, Markdown and JSON syntax. There must be no omissions in translation. \ Databend is a cloud-native data warehouse and an alternative to Snowflake. \ I am translating the Databend documentation for helping users.\ Translate the Markdown or JSON content I'll paste later into Chinese(The target language is Chinese!).\ You must strictly follow the rules below.\ - Never change the Markdown markup structure. Don't add or remove links. Do not change any URL.\ - Never change the contents of code blocks even if they appear to have a bug.\ -Content inside ``` (code fences) must not be translated, even if it seems incorrect or contains bugs.\ - Always preserve the original line breaks. Do not add or remove blank lines.\ - Never touch the permalink such as `{/*examples*/}` at the end of each heading.\ - Never touch HTML-like tags such as `<Notes>`.\ - Correctly format the document for best rendering. \ - Please do not translate database or computing-specific terms.\ -Keep the structure consistent with the source document and do not delete anything.\ - if you discover to describe the plan 'Personal', please translate to '基础版'.\ -When handling document translations, please adhere to the following specific vocabulary guidelines:'time travel': should consistently be translated as '时间回溯','warehouse' or 'warehouses': should consistently be translated as '计算集群','Data Warehouse': should consistently be translated as '数仓','Self-Hosted':should consistently be translated as '私有化部署', 'Databend Cloud'、'Vector'、'Stage': should remain untranslated.\ -The key of the json object in '_category_.json' is not translated.\ - Do not include any <think> tags or their contents in the output.\ -The entire Markdown document does not need to be enclosed by ```md, or ```markdown, or ``` at all(This is very important for the correct rendering of the document)."
5858
basePath: ${{ secrets.BASE_URL }}

.github/workflows/docs.translate.dir.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,5 +54,5 @@ jobs:
5454
inputFiles: "${{ steps.check_missing.outputs.missing_md_files }}${{ steps.check_missing.outputs.missing_json_files }}"
5555
outputFiles: "docs/cn/**/*.{md,json}"
5656
languages: "Simplified-Chinese"
57-
prompt: "You are a translation engine that has knowledge of databases and is familiar with SQL, HTML, Markdown and JSON syntax. There must be no omissions in translation. \ Databend is a cloud-native data warehouse and an alternative to Snowflake. \ I am translating the Databend documentation for helping users.\ Translate the Markdown or JSON content I'll paste later into Chinese(The target language is Chinese!).\ You must strictly follow the rules below.\ - Never change the Markdown markup structure. Don't add or remove links. Do not change any URL.\ - Never change the contents of code blocks even if they appear to have a bug.\ -Content inside ``` (code fences) must not be translated, even if it seems incorrect or contains bugs.\ - Always preserve the original line breaks. Do not add or remove blank lines.\ - Never touch the permalink such as `{/*examples*/}` at the end of each heading.\ - Never touch HTML-like tags such as `<Notes>`.\ - Correctly format the document for best rendering. \ - Please do not translate database or computing-specific terms.\ -Keep the structure consistent with the source document and do not delete anything.\ - if you discover to describe the plan 'Personal', please translate to '基础版'.\ -When handling document translations, please adhere to the following specific vocabulary guidelines:'time travel': should consistently be translated as '时间回溯','warehouse' or 'warehouses': should consistently be translated as '计算集群','Data Warehouse': should consistently be translated as '数仓','Self-Hosted':should consistently be translated as '私有化部署', 'Databend Cloud'、'Vector'、'Stage': should remain untranslated.\ -The key of the json object in '_category_.json' is not translated.\ - Do not include any <think> tags or their contents in the output.\ -The entire Markdown document does not need to be enclosed by ```md, or ``` markdown, or ``` at all."
57+
prompt: "You are a translation engine that has knowledge of databases and is familiar with SQL, HTML, Markdown and JSON syntax. There must be no omissions in translation. \ Databend is a cloud-native data warehouse and an alternative to Snowflake. \ I am translating the Databend documentation for helping users.\ Translate the Markdown or JSON content I'll paste later into Chinese(The target language is Chinese!).\ You must strictly follow the rules below.\ - Never change the Markdown markup structure. Don't add or remove links. Do not change any URL.\ - Never change the contents of code blocks even if they appear to have a bug.\ -Content inside ``` (code fences) must not be translated, even if it seems incorrect or contains bugs.\ - Always preserve the original line breaks. Do not add or remove blank lines.\ - Never touch the permalink such as `{/*examples*/}` at the end of each heading.\ - Never touch HTML-like tags such as `<Notes>`.\ - Correctly format the document for best rendering. \ - Please do not translate database or computing-specific terms.\ -Keep the structure consistent with the source document and do not delete anything.\ - if you discover to describe the plan 'Personal', please translate to '基础版'.\ -When handling document translations, please adhere to the following specific vocabulary guidelines:'time travel': should consistently be translated as '时间回溯','warehouse' or 'warehouses': should consistently be translated as '计算集群','Data Warehouse': should consistently be translated as '数仓','Self-Hosted':should consistently be translated as '私有化部署', 'Databend Cloud'、'Vector'、'Stage': should remain untranslated.\ -The key of the json object in '_category_.json' is not translated.\ - Do not include any <think> tags or their contents in the output.\ -The entire Markdown document does not need to be enclosed by ```md, or ```markdown, or ``` at all(This is very important for the correct rendering of the document)."
5858
basePath: ${{ secrets.BASE_URL }}

.github/workflows/docs.translate.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,5 +18,5 @@ jobs:
1818
with:
1919
apikey: ${{ secrets.API_KEY }}
2020
model: ${{ secrets.LLM_MODEL }}
21-
prompt: "You are a translation engine that has knowledge of databases and is familiar with SQL, HTML, Markdown and JSON syntax. There must be no omissions in translation. \ Databend is a cloud-native data warehouse and an alternative to Snowflake. \ I am translating the Databend documentation for helping users.\ Translate the Markdown or JSON content I'll paste later into Chinese(The target language is Chinese!).\ You must strictly follow the rules below.\ - Never change the Markdown markup structure. Don't add or remove links. Do not change any URL.\ - Never change the contents of code blocks even if they appear to have a bug.\ -Content inside ``` (code fences) must not be translated, even if it seems incorrect or contains bugs.\ - Always preserve the original line breaks. Do not add or remove blank lines.\ - Never touch the permalink such as `{/*examples*/}` at the end of each heading.\ - Never touch HTML-like tags such as `<Notes>`.\ - Correctly format the document for best rendering. \ - Please do not translate database or computing-specific terms.\ -Keep the structure consistent with the source document and do not delete anything.\ - if you discover to describe the plan 'Personal', please translate to '基础版'.\ -When handling document translations, please adhere to the following specific vocabulary guidelines:'time travel': should consistently be translated as '时间回溯','warehouse' or 'warehouses': should consistently be translated as '计算集群','Data Warehouse': should consistently be translated as '数仓','Self-Hosted':should consistently be translated as '私有化部署', 'Databend Cloud'、'Vector'、'Stage': should remain untranslated.\ -The key of the json object in '_category_.json' is not translated.\ - Do not include any <think> tags or their contents in the output.\ -The entire Markdown document does not need to be enclosed by ```md, or ``` markdown, or ``` at all."
21+
prompt: "You are a translation engine that has knowledge of databases and is familiar with SQL, HTML, Markdown and JSON syntax. There must be no omissions in translation. \ Databend is a cloud-native data warehouse and an alternative to Snowflake. \ I am translating the Databend documentation for helping users.\ Translate the Markdown or JSON content I'll paste later into Chinese(The target language is Chinese!).\ You must strictly follow the rules below.\ - Never change the Markdown markup structure. Don't add or remove links. Do not change any URL.\ - Never change the contents of code blocks even if they appear to have a bug.\ -Content inside ``` (code fences) must not be translated, even if it seems incorrect or contains bugs.\ - Always preserve the original line breaks. Do not add or remove blank lines.\ - Never touch the permalink such as `{/*examples*/}` at the end of each heading.\ - Never touch HTML-like tags such as `<Notes>`.\ - Correctly format the document for best rendering. \ - Please do not translate database or computing-specific terms.\ -Keep the structure consistent with the source document and do not delete anything.\ - if you discover to describe the plan 'Personal', please translate to '基础版'.\ -When handling document translations, please adhere to the following specific vocabulary guidelines:'time travel': should consistently be translated as '时间回溯','warehouse' or 'warehouses': should consistently be translated as '计算集群','Data Warehouse': should consistently be translated as '数仓','Self-Hosted':should consistently be translated as '私有化部署', 'Databend Cloud'、'Vector'、'Stage': should remain untranslated.\ -The key of the json object in '_category_.json' is not translated.\ - Do not include any <think> tags or their contents in the output.\ -The entire Markdown document does not need to be enclosed by ```md, or ```markdown, or ``` at all(This is very important for the correct rendering of the document)."
2222
basePath: ${{ secrets.BASE_URL }}

docs/cn/dev/10-policies/notice.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,4 +25,4 @@ title: 声明
2525
KIND, either express or implied. See the License for the
2626
specific language governing permissions and limitations
2727
under the License.
28-
```
28+
```

docs/cn/developer/20-community/00-contributor/02-how-to-write-scalar-functions.md

Lines changed: 7 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
```md
21
---
32
title: 如何编写标量函数
43
sidebar_label: 如何编写标量函数
@@ -96,12 +95,12 @@ pub struct FunctionRegistry {
9695
此外,根据所需的功能,有不同级别的注册 API。
9796

9897
| | 自动向量化 | 访问输出列构建器 | 自动 Null 传递 | 自动合并 Null | 自动向下转换 | 抛出运行时错误 | 变长参数 | 元组 |
99-
| ----------------------------------- | -------- | -------------- | ---------- | --------- | -------- | -------- | ---- | -- |
100-
| register_n_arg | ✔️ || ✔️ || ✔️ | ✔️ |||
101-
| register_passthrough_nullable_n_arg || ✔️ | ✔️ || ✔️ | ✔️ |||
102-
| register_combine_nullable_n_arg || ✔️ | ✔️ | ✔️ | ✔️ | ✔️ |||
103-
| register_n_arg_core || ✔️ ||| ✔️ | ✔️ |||
104-
| register_function_factory || ✔️ |||| ✔️ | ✔️ | ✔️ |
98+
| ----------------------------------- | ---------- | ---------------- | -------------- | ------------- | ------------ | -------------- | -------- | ---- |
99+
| register_n_arg | ✔️ | | ✔️ | | ✔️ | ✔️ | | |
100+
| register_passthrough_nullable_n_arg | | ✔️ | ✔️ | | ✔️ | ✔️ | | |
101+
| register_combine_nullable_n_arg | | ✔️ | ✔️ | ✔️ | ✔️ | ✔️ | | |
102+
| register_n_arg_core | | ✔️ | | | ✔️ | ✔️ | | |
103+
| register_function_factory | | ✔️ | | | | ✔️ | ✔️ | ✔️ |
105104

106105
## 函数组合
107106

@@ -246,4 +245,4 @@ registry.register_passthrough_nullable_2_arg::<StringType, StringType, BooleanTy
246245

247246
### 逻辑测试
248247

249-
函数的逻辑测试位于 [02_function](https://github.com/databendlabs/databend/tree/d5e06af03ba0f99afdd6bdc974bf2f5c1c022db8/tests/sqllogictests/suites/query/02_function) 中。
248+
函数的逻辑测试位于 [02_function](https://github.com/databendlabs/databend/tree/d5e06af03ba0f99afdd6bdc974bf2f5c1c022db8/tests/sqllogictests/suites/query/02_function) 中。

0 commit comments

Comments
 (0)