database/doris
2
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

fix typo in docs (#5046)

Browse Source
This commit is contained in:
Zhengguo Yang
2020-12-10 15:10:22 +08:00
committed by GitHub
parent e278e0b3db
commit bc063ebce2
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/en/administrator-guide/load-data/batch-delete-manual.md
View File

@ -124,10 +124,10 @@ Routine load adds a mapping to the `columns` field. The mapping method is the sa
## Enable bulk delete support
There are two ways of enabling batch delete support:
1. By adding ʻenable_batch_delete_by_default=true` in the fe configuration file, all newly created tables after restarting fe support batch deletion, this option defaults to false
1. By adding `enable_batch_delete_by_default=true` in the fe configuration file, all newly created tables after restarting fe support batch deletion, this option defaults to false
2. For tables that have not changed the above fe configuration or for existing tables that do not support the bulk delete function, you can use the following statement:
ʻALTER TABLE tablename ENABLE FEATURE "BATCH_DELETE"` to enable batch delete.
`ALTER TABLE tablename ENABLE FEATURE "BATCH_DELETE"` to enable the batch delete.
If you want to determine whether a table supports batch delete, you can set a session variable to display the hidden columns `SET show_hidden_columns=true`, and then use `desc tablename`, if there is a `__DELETE_SIGN__` column in the output, it is supported, if not, it is not supported
## Note

2
docs/en/getting-started/advance-usage.md
View File

@ -86,7 +86,7 @@ For more help, see `HELP ALTER TABLE'.
## 2 Rollup
Rollup can be understood as a physical index structure of Table. ** Physicalization ** is because its data is physically stored independently, and ** indexing ** means that Rollup can adjust column order to increase the hit rate of prefix index, or reduce key column to increase data aggregation.
Rollup can be understood as a materialized index structure of Table. ** materialized ** because data is store as a concrete ("materialized") table independently, and ** indexing ** means that Rollup can adjust column order to increase the hit rate of prefix index, or reduce key column to increase data aggregation.
Examples are given below.

6
docs/en/sql-reference/sql-statements/Administration/ALTER SYSTEM.md
View File

@ -53,14 +53,14 @@ Explain:
2) heartbeat_port is the heartbeat port of the node
3) Adding and deleting nodes are synchronous operations. These two operations do not take into account the existing data on the node, the node is directly deleted from the metadata, please use cautiously.
4) Node offline operations are used to secure offline nodes. This operation is asynchronous. If successful, the node will eventually be removed from the metadata. If it fails, the offline will not be completed.
5) The downline operation of the node can be cancelled manually. See CANCEL DECOMMISSION for details
5) The offline operation of the node can be cancelled manually. See CANCEL DECOMMISSION for details
6) Load error hub:
Currently, two types of Hub are supported: Mysql and Broker. You need to specify "type" = "mysql" or "type" = "broker" in PROPERTIES.
If you need to delete the current load error hub, you can set type to null.
1) When using the Mysql type, the error information generated when importing will be inserted into the specified MySQL library table, and then the error information can be viewed directly through the show load warnings statement.
Hub of Mysql type needs to specify the following parameters:
guest guest
host：mysql host
port：mysql port
user：mysql user
password：mysql password
@ -84,7 +84,7 @@ ALTER SYSTEM ADD FREE BACKEND "host:port";
3. Delete two nodes
ALTER SYSTEM DROP BACKEND "host1:port", "host2:port";
4. Two downline nodes
4. offline two nodes
ALTER SYSTEM DECOMMISSION BACKEND "host1:port", "host2:port";
5. Add two Hdfs Broker