From e361f93136ae085aec7ff54b92d39c4f9c45a5cc Mon Sep 17 00:00:00 2001 From: yikeke Date: Wed, 8 Aug 2018 19:22:43 +0800 Subject: [PATCH] op-guide, sql, tool: fix comma misuse To change the Chinese commas into the English commas in three English documents --- op-guide/tune-tikv.md | 8 ++++---- sql/tidb-specific.md | 6 +++--- tools/syncer.md | 4 ++-- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/op-guide/tune-tikv.md b/op-guide/tune-tikv.md index 9214152eaf2ce..f4ba72b72646b 100644 --- a/op-guide/tune-tikv.md +++ b/op-guide/tune-tikv.md @@ -78,7 +78,7 @@ address = "" job = "tikv" [raftstore] -# The default value is true，which means writing the data on the disk compulsorily. If it is not in a business scenario +# The default value is true, which means writing the data on the disk compulsorily. If it is not in a business scenario # of the financial security level, it is recommended to set the value to false to achieve better performance. sync-log = true @@ -90,14 +90,14 @@ region-max-size = "384MB" # The threshold value of Region split region-split-size = "256MB" # When the data size in a Region is larger than the threshold value, TiKV checks whether this Region needs split. -# To reduce the costs of scanning data in the checking process，set the value to 32MB during checking and set it to +# To reduce the costs of scanning data in the checking process, set the value to 32MB during checking and set it to # the default value in normal operation. region-split-check-diff = "32MB" [rocksdb] # The maximum number of threads of RocksDB background tasks. The background tasks include compaction and flush. # For detailed information why RocksDB needs to implement compaction, see RocksDB-related materials. When write -# traffic (like the importing data size) is big，it is recommended to enable more threads. But set the number of the enabled +# traffic (like the importing data size) is big, it is recommended to enable more threads. But set the number of the enabled # threads smaller than that of CPU cores. For example, when importing data, for a machine with a 32-core CPU, # set the value to 28. # max-background-jobs = 8 @@ -236,7 +236,7 @@ min-write-buffer-number-to-merge = 1 max-bytes-for-level-base = "512MB" target-file-size-base = "32MB" -# Generally，you can set it from 256MB to 2GB. In most cases, you can use the default value. But if the system +# Generally, you can set it from 256MB to 2GB. In most cases, you can use the default value. But if the system # resources are adequate, you can set it higher. block-cache-size = "256MB" ``` diff --git a/sql/tidb-specific.md b/sql/tidb-specific.md index e60df8f20af59..5ecbb627d6856 100644 --- a/sql/tidb-specific.md +++ b/sql/tidb-specific.md @@ -245,19 +245,19 @@ The `Hint` syntax is included in comments like `/*+ xxx */`, and in MySQL client ### TIDB_SMJ(t1, t2) -```SELECT /*+ TIDB_SMJ(t1, t2) */ * from t1，t2 where t1.id = t2.id``` +```SELECT /*+ TIDB_SMJ(t1, t2) */ * from t1, t2 where t1.id = t2.id``` This variable is used to remind the optimizer to use the `Sort Merge Join` algorithm. This algorithm takes up less memory, but takes longer to execute. It is recommended if the data size is too large, or there’s insufficient system memory. ### TIDB_INLJ(t1, t2) -```SELECT /*+ TIDB_INLJ(t1, t2) */ * from t1，t2 where t1.id = t2.id``` +```SELECT /*+ TIDB_INLJ(t1, t2) */ * from t1, t2 where t1.id = t2.id``` This variable is used to remind the optimizer to use the `Index Nested Loop Join` algorithm. In some scenarios, this algorithm runs faster and takes up fewer system resources, but may be slower and takes up more system resources in some other scenarios. You can try to use this algorithm in scenarios where the result-set is less than 10,000 rows after the outer table is filtered by the WHERE condition. The parameter in `TIDB_INLJ()` is the candidate table for the driving table (external table) when generating the query plan. That means, `TIDB_INLJ (t1)` will only consider using t1 as the driving table to create a query plan. ### TIDB_HJ(t1, t2) -```SELECT /*+ TIDB_HJ(t1, t2) */ * from t1，t2 where t1.id = t2.id``` +```SELECT /*+ TIDB_HJ(t1, t2) */ * from t1, t2 where t1.id = t2.id``` This variable is used to remind the optimizer to use the `Hash Join` algorithm. This algorithm executes threads concurrently. It runs faster but takes up more memory. diff --git a/tools/syncer.md b/tools/syncer.md index 130cd0dfeee06..7e0823c6c91ad 100644 --- a/tools/syncer.md +++ b/tools/syncer.md @@ -127,7 +127,7 @@ status-addr = "127.0.0.1:10086" # replicate-do-db = ["~^b.*","s1"] # Specify the db.table to be synchronized. -# db-name and tbl-name do not support the `db-name ="dbname，dbname2"` format. +# db-name and tbl-name do not support the `db-name ="dbname, dbname2"` format. # [[replicate-do-table]] # db-name ="dbname" # tbl-name = "table-name" @@ -145,7 +145,7 @@ status-addr = "127.0.0.1:10086" # replicate-ignore-db = ["~^b.*","s1"] # Specify the database table you want to ignore in synchronization. -# db-name and tbl-name do not support the `db-name ="dbname，dbname2"` format. +# db-name and tbl-name do not support the `db-name ="dbname, dbname2"` format. # [[replicate-ignore-table]] # db-name = "your_db" # tbl-name = "your_table"