Copilot commented on code in PR #3408:
URL: https://github.com/apache/doris-website/pull/3408#discussion_r2850448809
##########
i18n/zh-CN/docusaurus-plugin-content-docs/version-4.x/data-operate/import/complex-types/bitmap.md:
##########
@@ -2,11 +2,11 @@
{
"title": "Bitmap",
"language": "zh-CN",
- "description": "BITMAP 类型可以在 Duplicate 表、Unique 表、Aggregate 表中使用，只能作为 Key
类，无法作为 Value 列使用。在 Aggregate 表中使用 BITMAP 类型，其建表时必须使用聚合类型
BITMAPUNION。用户不需要指定长度和默认值。"
+ "description": "BITMAP 类型可以在 Duplicate 表、Unique 表、Aggregate 表中使用，只能作为
Value 列，无法作为 Key 列使用。在 Aggregate 表中使用 BITMAP 类型，其建表时必须使用聚合类型
BITMAPUNION。用户不需要指定长度和默认值。"
Review Comment:
In the frontmatter description, the aggregate type is written as
“BITMAPUNION”, but the rest of the doc (and the SQL manual) uses
“BITMAP_UNION”. Please align the frontmatter to “BITMAP_UNION” to avoid
confusing readers/search results.
```suggestion
"description": "BITMAP 类型可以在 Duplicate 表、Unique 表、Aggregate 表中使用，只能作为
Value 列，无法作为 Key 列使用。在 Aggregate 表中使用 BITMAP 类型，其建表时必须使用聚合类型
BITMAP_UNION。用户不需要指定长度和默认值。"
```
##########
versioned_docs/version-3.x/data-operate/import/complex-types/bitmap.md:
##########
@@ -2,11 +2,11 @@
{
"title": "Bitmap",
"language": "en",
- "description": "The BITMAP type can be used in Duplicate tables, Unique
tables, and Aggregate tables, and can only be used as a Key type, not as a
Value column."
+ "description": "The BITMAP type can be used in Duplicate tables, Unique
tables, and Aggregate tables, and can only be used as a Value type, not as a
Key type."
}
---
-The BITMAP type can be used in Duplicate tables, Unique tables, and Aggregate
tables, and can only be used as a Key type, not as a Value column. When using
the BITMAP type in an Aggregate table, the table must be created with the
aggregate type BITMAP_UNION. Users do not need to specify length and default
values. The length is controlled by the system based on the degree of data
aggregation. For more documentation, refer to
[Bitmap](../../../sql-manual/basic-element/sql-data-types/aggregate/BITMAP).
+The BITMAP type can be used in Duplicate tables, Unique tables, and Aggregate
tables, and can only be used as a Value type, not as a Key type. When using the
BITMAP type in an Aggregate table, the table must be created with the aggregate
type BITMAP_UNION. Users do not need to specify length and default values. The
length is controlled by the system based on the degree of data aggregation. For
more documentation, refer to
[Bitmap](../../../sql-manual/basic-element/sql-data-types/aggregate/BITMAP).
Review Comment:
The term “Value type / Key type” here is inconsistent with the terminology
used elsewhere in the docs (e.g., SQL manual describes BITMAP as a “non-key
column”). Consider rewording to “can only be used as a non-key column (value
column), not as a key column” for clarity and consistency (update both the
frontmatter description and the first paragraph).
##########
i18n/zh-CN/docusaurus-plugin-content-docs/current/data-operate/import/complex-types/bitmap.md:
##########
@@ -2,11 +2,11 @@
{
"title": "Bitmap",
"language": "zh-CN",
- "description": "BITMAP 类型可以在 Duplicate 表、Unique 表、Aggregate 表中使用，只能作为 Key
类，无法作为 Value 列使用。在 Aggregate 表中使用 BITMAP 类型，其建表时必须使用聚合类型
BITMAPUNION。用户不需要指定长度和默认值。"
+ "description": "BITMAP 类型可以在 Duplicate 表、Unique 表、Aggregate 表中使用，只能作为
Value 列，无法作为 Key 列使用。在 Aggregate 表中使用 BITMAP 类型，其建表时必须使用聚合类型
BITMAPUNION。用户不需要指定长度和默认值。"
Review Comment:
In the frontmatter description, the aggregate type is written as
“BITMAPUNION”, but the rest of the doc (and the SQL manual) uses
“BITMAP_UNION”. Please align the frontmatter to “BITMAP_UNION” to avoid
confusing readers/search results.
```suggestion
"description": "BITMAP 类型可以在 Duplicate 表、Unique 表、Aggregate 表中使用，只能作为
Value 列，无法作为 Key 列使用。在 Aggregate 表中使用 BITMAP 类型，其建表时必须使用聚合类型
BITMAP_UNION。用户不需要指定长度和默认值。"
```
##########
i18n/zh-CN/docusaurus-plugin-content-docs/version-2.1/data-operate/import/complex-types/bitmap.md:
##########
@@ -2,11 +2,11 @@
{
"title": "Bitmap",
"language": "zh-CN",
- "description": "BITMAP 类型可以在 Duplicate 表、Unique 表、Aggregate 表中使用，只能作为 Key
类，无法作为 Value 列使用。在 Aggregate 表中使用 BITMAP 类型，其建表时必须使用聚合类型
BITMAPUNION。用户不需要指定长度和默认值。"
+ "description": "BITMAP 类型可以在 Duplicate 表、Unique 表、Aggregate 表中使用，只能作为
Value 列，无法作为 Key 列使用。在 Aggregate 表中使用 BITMAP 类型，其建表时必须使用聚合类型
BITMAPUNION。用户不需要指定长度和默认值。"
Review Comment:
In the frontmatter description, the aggregate type is written as
“BITMAPUNION”, but the rest of the doc (and the SQL manual) uses
“BITMAP_UNION”. Please align the frontmatter to “BITMAP_UNION” to avoid
confusing readers/search results.
```suggestion
"description": "BITMAP 类型可以在 Duplicate 表、Unique 表、Aggregate 表中使用，只能作为
Value 列，无法作为 Key 列使用。在 Aggregate 表中使用 BITMAP 类型，其建表时必须使用聚合类型
BITMAP_UNION。用户不需要指定长度和默认值。"
```
##########
docs/data-operate/import/complex-types/bitmap.md:
##########
@@ -2,11 +2,11 @@
{
"title": "Bitmap",
"language": "en",
- "description": "The BITMAP type can be used in Duplicate tables, Unique
tables, and Aggregate tables, and can only be used as a Key type, not as a
Value column."
+ "description": "The BITMAP type can be used in Duplicate tables, Unique
tables, and Aggregate tables, and can only be used as a Value type, not as a
Key type."
}
---
-The BITMAP type can be used in Duplicate tables, Unique tables, and Aggregate
tables, and can only be used as a Key type, not as a Value column. When using
the BITMAP type in an Aggregate table, the table must be created with the
aggregate type BITMAP_UNION. Users do not need to specify length and default
values. The length is controlled by the system based on the degree of data
aggregation. For more documentation, refer to
[Bitmap](../../../sql-manual/basic-element/sql-data-types/aggregate/BITMAP).
+The BITMAP type can be used in Duplicate tables, Unique tables, and Aggregate
tables, and can only be used as a Value type, not as a Key type. When using the
BITMAP type in an Aggregate table, the table must be created with the aggregate
type BITMAP_UNION. Users do not need to specify length and default values. The
length is controlled by the system based on the degree of data aggregation. For
more documentation, refer to
[Bitmap](../../../sql-manual/basic-element/sql-data-types/aggregate/BITMAP).
Review Comment:
The term “Value type / Key type” here is inconsistent with the terminology
used elsewhere in the docs (e.g., SQL manual describes BITMAP as a “non-key
column”). Consider rewording to “can only be used as a non-key column (value
column), not as a key column” for clarity and consistency (update both the
frontmatter description and the first paragraph).
##########
versioned_docs/version-4.x/data-operate/import/complex-types/bitmap.md:
##########
@@ -2,11 +2,11 @@
{
"title": "Bitmap",
"language": "en",
- "description": "The BITMAP type can be used in Duplicate tables, Unique
tables, and Aggregate tables, and can only be used as a Key type, not as a
Value column."
+ "description": "The BITMAP type can be used in Duplicate tables, Unique
tables, and Aggregate tables, and can only be used as a Value type, not as a
Key type."
}
---
-The BITMAP type can be used in Duplicate tables, Unique tables, and Aggregate
tables, and can only be used as a Key type, not as a Value column. When using
the BITMAP type in an Aggregate table, the table must be created with the
aggregate type BITMAP_UNION. Users do not need to specify length and default
values. The length is controlled by the system based on the degree of data
aggregation. For more documentation, refer to
[Bitmap](../../../sql-manual/basic-element/sql-data-types/aggregate/BITMAP).
+The BITMAP type can be used in Duplicate tables, Unique tables, and Aggregate
tables, and can only be used as a Value type, not as a Key type. When using the
BITMAP type in an Aggregate table, the table must be created with the aggregate
type BITMAP_UNION. Users do not need to specify length and default values. The
length is controlled by the system based on the degree of data aggregation. For
more documentation, refer to
[Bitmap](../../../sql-manual/basic-element/sql-data-types/aggregate/BITMAP).
Review Comment:
The term “Value type / Key type” here is inconsistent with the terminology
used elsewhere in the docs (e.g., SQL manual describes BITMAP as a “non-key
column”). Consider rewording to “can only be used as a non-key column (value
column), not as a key column” for clarity and consistency (update both the
frontmatter description and the first paragraph).
##########
versioned_docs/version-2.1/data-operate/import/complex-types/bitmap.md:
##########
@@ -2,11 +2,11 @@
{
"title": "Bitmap",
"language": "en",
- "description": "The BITMAP type can be used in Duplicate tables, Unique
tables, and Aggregate tables, and can only be used as a Key type, not as a
Value column."
+ "description": "The BITMAP type can be used in Duplicate tables, Unique
tables, and Aggregate tables, and can only be used as a Value type, not as a
Key type."
}
---
-The BITMAP type can be used in Duplicate tables, Unique tables, and Aggregate
tables, and can only be used as a Key type, not as a Value column. When using
the BITMAP type in an Aggregate table, the table must be created with the
aggregate type BITMAP_UNION. Users do not need to specify length and default
values. The length is controlled by the system based on the degree of data
aggregation. For more documentation, refer to
[Bitmap](../../../sql-manual/basic-element/sql-data-types/aggregate/BITMAP).
+The BITMAP type can be used in Duplicate tables, Unique tables, and Aggregate
tables, and can only be used as a Value type, not as a Key type. When using the
BITMAP type in an Aggregate table, the table must be created with the aggregate
type BITMAP_UNION. Users do not need to specify length and default values. The
length is controlled by the system based on the degree of data aggregation. For
more documentation, refer to
[Bitmap](../../../sql-manual/basic-element/sql-data-types/aggregate/BITMAP).
Review Comment:
The term “Value type / Key type” here is inconsistent with the terminology
used elsewhere in the docs (e.g., SQL manual describes BITMAP as a “non-key
column”). Consider rewording to “can only be used as a non-key column (value
column), not as a key column” for clarity and consistency (update both the
frontmatter description and the first paragraph).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
