From 1e0b3fde6474ede724e173f3edef5f0e8b321c4b Mon Sep 17 00:00:00 2001 From: Ran Date: Wed, 19 Feb 2020 12:28:18 +0800 Subject: [PATCH 01/10] reference: add error codes WIP --- dev/reference/error-codes.md | 89 ++++++++++++++++++++++++++++++++++++ 1 file changed, 89 insertions(+) diff --git a/dev/reference/error-codes.md b/dev/reference/error-codes.md index 1de2c07270468..95e84dd39b987 100644 --- a/dev/reference/error-codes.md +++ b/dev/reference/error-codes.md @@ -19,6 +19,94 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8003 | If the data in a row is not consistent with the index when executing the `ADMIN CHECK TABLE` command, TiDB returns this error. | | 8004 | A single transaction is too large. | See [the error message `transaction too large`](/dev/faq/tidb.md#the-error-message-transaction-too-large-is-displayed) for the cause and solution. | | 8005 | Transactions in TiDB encounter write conflicts. | See [the Troubleshoot section](/dev/faq/tidb.md#troubleshoot) for the cause and solution. | +| 8018 | The plugin cannot be reloaded because it is not loaded. | +| 8019 | The reloaded plugin version is different from the previous one, so the plugin cannot be reloaded. | +| 8020 | The table is locked. | +| 8021 | The key does not exist. | +| 8022 | Transactions commit failed. You may retry the process. | +| 8023 | You cannot set an empty value. | +| 8024 | Illegal transactions. | +| 8025 | A single Key-Value pair that are being written is too large. | +| 8026 | This interface is not implemented. | +| 8027 | The version of table structure is outdated. | +| 8028 | The table structure has changed. | +| 8029 | Error value. | +| 8030 | | +| 8031 | A negative number is converted to a positive number, when being converted to an unsigned number. | +| 8032 | Illegal `year` format. | +| 8033 | Illegal `year` value. | +| 8034 | Incorrect `datetime` value. | +| 8036 | Illegal `time` format. | +| 8037 | Illegal `week` format. | +| 8038 | The field cannot access a default value. | +| 8039 | The ? of index exceeds boundary. | +| 8042 | The state of table structure is not existing. | +| 8043 | The state of column information is not existing. | +| 8044 | The state of index is not existing. | +| 8045 | Illegal table data. | +| 8046 | The state of column information is hidden. | +| 8047 | The system variable value you set is not supported. This error occurs in the warning after the user sets a variable value that is not supported in the database. +| 8048 | The user sets a database isolation level that is not supported. +| 8049 | The loading of privilege-related table failed. | +| 8050 | The privilege type you set is not supported. | +| 8051 | Unknown field type. | +| 8052 | The serial number of the packet from client is incorrect. | +| 8053 | An illegal `AUTO-INCREMENT` value is obtained. | +| 8055 | The current snapshot is too old. The data may have been garbage collected. | +| 8056 | Illegal table ID. | +| 8057 | Illegal field type. | +| 8058 | You applied an auto variable type that does not exist. | +| 8059 | The obtain of auto random amount failed. | +| 8060 | Illegal auto-increment offset. | +| 8061 | The SQL Hint is not supported. | +| 8062 | An illegal token is used in the SQL Hint. It conflicts with reserved words in Hint. | +| 8063 | The memory usage limited in SQL Hint exceeds the upper limit set by the system. The setting in SQL Hint is ignored. | +| 8064 | 解析 SQL Hint 失败 | The parsing of SQL Hint failed. | +| 8065 | Illegal integer is used in SQL Hint. | +| 8066 | The second parameter in the `JSON_OBJECTAGG` function is illegal. | +| 8101 | The format of plugin ID is incorrect. | The correct format is `[name]-【version]`, and no `-` is allowed in `name` and `version`. | +| 8102 | Unable to read the plugin definition information | +| 8103 | The plugin name is incorrect. | +| 8104 | The plugin version does not match. | +| 8105 | The plugin is repeatedly loaded. | +| 8106 | The system variable name defined by the plugin does not begin with the name of the plugin. | +| 8107 | The loaded plugin does not specify a version, or the version specified is too low. | +| 8108 | Unsupported execution plan type. | +| 8109 | The specified index cannot be found when the index is analyzed. +| 8110 | The Cartesian product operation is not allowed. | Set the `cross-join` in the configuration to `true`. | +| 8111 | When executing the `EXECUTE` statement, the corresponding `Prepare` statement cannot be found. +| 8112 | The number of parameters in the `EXECUTE` statement is not consistent with the `Prepare` statement. | +| 8113 | The table structure involved in the `Execute` statement has changed after the `Prepare` statement is executed. | +| 8114 | Unknown execution plan type. | +| 8115 | Preparing multiple lines of statements is not supported. | +| 8116 | Preparing DDL statements is not supported. | +| 8118 | Executor build failed. | +| 8120 | The `start tso` of transactions cannot be obtained. | +| 8121 | Privilege check failed. | +| 8122 | Wild cards are specified, but no corresponding table name is found. | +| 8123 | An SQL query with aggregate functions returns non-aggregated columns, which violates the `only_full_group_by` mode. | +| 8200 | The DDL syntax is not yet supported. | +| 8201 | TiDB is currently not the DDL owner. | +| 8202 | This index cannot be decoded. | +| 8203 | Illegal DDL worker. | +| 8204 | Illegal DDL job. | +| 8205 | Illegal DDL job mark. | +| 8206 | The DDL operation in `re-organize` phase timed out. +| 8207 | Illegal storage nodes. | +| 8210 | Illegal DDL state. | +| 8211 | Panic occurs during the DDL operation in `re-organize` phase. | +| 8212 | Illegal split range of Region. | +| 8213 | Illegal DDL job version | +| 8214 | The DDL operation is terminated. | +| 8215 | The `ADMIN REPAIR TABLE` command fails. | +| 8216 | Illegal auto random columns. | +| 8221 | The Key encoding is incorrect. | +| 8222 | The indexing of Key encoding is incorrect. | +| 8223 | This error occurs when detecting that the data is not consistent with the index. | +| 8224 | The DDL job cannot be found. | +| 8225 | The DDL operation is completed and cannot be canceled. | +| 8226 | The DDL operation is almost completed and cannot be canceled. | +| 8227 | Unsupported options are used when creating `Sequence`. | | 9001 | The PD request timed out. | Check the state/monitor/log of the PD server and the network between the TiDB server and the PD server. | | 9002 | The TiKV request timed out. | Check the state/monitor/log of the TiKV server and the network between the TiDB server and the TiKV server. | | 9003 | The TiKV server is busy and this usually occurs when the workload is too high. | Check the state/monitor/log of the TiKV server. | @@ -27,6 +115,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 9006 | The interval of GC Life Time is too short and the data that should be read by the long transactions might be cleared. | Extend the interval of GC Life Time. | | 9500 | A single transaction is too large. | See [the error message `transaction too large`](/dev/faq/tidb.md#the-error-message-transaction-too-large-is-displayed) for the solution. | | 9007 | Transactions in TiKV encounter write conflicts. | See [the Troubleshoot section](/dev/faq/tidb.md#troubleshoot) for the cause and solution. | +| 9008 | Too many requests are sent to TiKV at the same time. The number exceeds limit. | ## Troubleshooting From f94557450f858c71542293135336f6f3ea86003b Mon Sep 17 00:00:00 2001 From: Ran Date: Wed, 19 Feb 2020 15:01:43 +0800 Subject: [PATCH 02/10] Update error-codes.md --- dev/reference/error-codes.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/dev/reference/error-codes.md b/dev/reference/error-codes.md index 95e84dd39b987..6f292056ee739 100644 --- a/dev/reference/error-codes.md +++ b/dev/reference/error-codes.md @@ -19,18 +19,18 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8003 | If the data in a row is not consistent with the index when executing the `ADMIN CHECK TABLE` command, TiDB returns this error. | | 8004 | A single transaction is too large. | See [the error message `transaction too large`](/dev/faq/tidb.md#the-error-message-transaction-too-large-is-displayed) for the cause and solution. | | 8005 | Transactions in TiDB encounter write conflicts. | See [the Troubleshoot section](/dev/faq/tidb.md#troubleshoot) for the cause and solution. | -| 8018 | The plugin cannot be reloaded because it is not loaded. | -| 8019 | The reloaded plugin version is different from the previous one, so the plugin cannot be reloaded. | +| 8018 | The plugin cannot be reloaded because it has not been loaded. | +| 8019 | The version of the plugin that are being reloaded is different from the previous version. The plugin cannot be reloaded. | | 8020 | The table is locked. | | 8021 | The key does not exist. | -| 8022 | Transactions commit failed. You may retry the process. | -| 8023 | You cannot set an empty value. | +| 8022 | The transaction commit fails. You may retry the process. | +| 8023 | An empty value is not allowed. | | 8024 | Illegal transactions. | | 8025 | A single Key-Value pair that are being written is too large. | -| 8026 | This interface is not implemented. | -| 8027 | The version of table structure is outdated. | -| 8028 | The table structure has changed. | -| 8029 | Error value. | +| 8026 | The interface is not implemented. | +| 8027 | The table schema version is outdated. | +| 8028 | The table schema has changed. | +| 8029 | Incorrect value. | | 8030 | | | 8031 | A negative number is converted to a positive number, when being converted to an unsigned number. | | 8032 | Illegal `year` format. | From 625450ffa81945759d158e1bb795a7f157775e7a Mon Sep 17 00:00:00 2001 From: Ran Date: Wed, 19 Feb 2020 16:34:37 +0800 Subject: [PATCH 03/10] Update error-codes.md --- dev/reference/error-codes.md | 80 ++++++++++++++++++------------------ 1 file changed, 40 insertions(+), 40 deletions(-) diff --git a/dev/reference/error-codes.md b/dev/reference/error-codes.md index 6f292056ee739..1b824f5335278 100644 --- a/dev/reference/error-codes.md +++ b/dev/reference/error-codes.md @@ -19,7 +19,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8003 | If the data in a row is not consistent with the index when executing the `ADMIN CHECK TABLE` command, TiDB returns this error. | | 8004 | A single transaction is too large. | See [the error message `transaction too large`](/dev/faq/tidb.md#the-error-message-transaction-too-large-is-displayed) for the cause and solution. | | 8005 | Transactions in TiDB encounter write conflicts. | See [the Troubleshoot section](/dev/faq/tidb.md#troubleshoot) for the cause and solution. | -| 8018 | The plugin cannot be reloaded because it has not been loaded. | +| 8018 | The plugin cannot be reloaded because it has not been loaded before. | | 8019 | The version of the plugin that are being reloaded is different from the previous version. The plugin cannot be reloaded. | | 8020 | The table is locked. | | 8021 | The key does not exist. | @@ -31,63 +31,63 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8027 | The table schema version is outdated. | | 8028 | The table schema has changed. | | 8029 | Incorrect value. | -| 8030 | | -| 8031 | A negative number is converted to a positive number, when being converted to an unsigned number. | +| 8030 | After an unsigned positive integer is converted to a signed integer, it exceeds the maximum value and displays as a negative integer.| +| 8031 | When being converted to an unsigned integer, a negative integer is converted to a positive integer. | | 8032 | Illegal `year` format. | | 8033 | Illegal `year` value. | | 8034 | Incorrect `datetime` value. | | 8036 | Illegal `time` format. | | 8037 | Illegal `week` format. | -| 8038 | The field cannot access a default value. | -| 8039 | The ? of index exceeds boundary. | -| 8042 | The state of table structure is not existing. | -| 8043 | The state of column information is not existing. | -| 8044 | The state of index is not existing. | +| 8038 | The field cannot obtain a default value. | +| 8039 | Index offset is out of range. | +| 8042 | The state of table schema does not exist. | +| 8043 | The state of column information does not exist. | +| 8044 | The state of index does not exist. | | 8045 | Illegal table data. | -| 8046 | The state of column information is hidden. | -| 8047 | The system variable value you set is not supported. This error occurs in the warning after the user sets a variable value that is not supported in the database. -| 8048 | The user sets a database isolation level that is not supported. -| 8049 | The loading of privilege-related table failed. | -| 8050 | The privilege type you set is not supported. | +| 8046 | The state of column information is invisible. | +| 8047 | The value of the system variable is not supported. It usually occurs in the alarm information after the user sets a variable value that is not supported in the database. +| 8048 | An unsupported database isolation level is set. | +| 8049 | It fails to load the privilege related table. | +| 8050 | An unsupported privilege type is set. | | 8051 | Unknown field type. | -| 8052 | The serial number of the packet from client is incorrect. | -| 8053 | An illegal `AUTO-INCREMENT` value is obtained. | +| 8052 | The serial number of the data packet from the client is incorrect. | +| 8053 | An illegal auto-incrementing value is obtained. | | 8055 | The current snapshot is too old. The data may have been garbage collected. | | 8056 | Illegal table ID. | | 8057 | Illegal field type. | -| 8058 | You applied an auto variable type that does not exist. | -| 8059 | The obtain of auto random amount failed. | -| 8060 | Illegal auto-increment offset. | -| 8061 | The SQL Hint is not supported. | -| 8062 | An illegal token is used in the SQL Hint. It conflicts with reserved words in Hint. | -| 8063 | The memory usage limited in SQL Hint exceeds the upper limit set by the system. The setting in SQL Hint is ignored. | -| 8064 | 解析 SQL Hint 失败 | The parsing of SQL Hint failed. | -| 8065 | Illegal integer is used in SQL Hint. | +| 8058 | You apply an automatic variable type that does not exist. | +| 8059 | It fails to obtain an automatic random variable. | +| 8060 | Illegal auto-incrementing offset. | +| 8061 | Unsupported SQL Hint. | +| 8062 | An illegal token is used in SQL Hint. It conflicts with reserved words in SQL Hint. | +| 8063 | The limited memory usage set in SQL Hint exceeds the upper limit of the system. The setting in SQL Hint is ignored. | +| 8064 | It fails to parse SQL Hint. | +| 8065 | An illegal integer is used in SQL Hint. | | 8066 | The second parameter in the `JSON_OBJECTAGG` function is illegal. | -| 8101 | The format of plugin ID is incorrect. | The correct format is `[name]-【version]`, and no `-` is allowed in `name` and `version`. | -| 8102 | Unable to read the plugin definition information | +| 8101 | The format of plugin ID is incorrect. | The correct format is `[name]-[version]`, and no `-` is allowed in `name` and `version`. | +| 8102 | Unable to read the plugin definition information. | | 8103 | The plugin name is incorrect. | | 8104 | The plugin version does not match. | | 8105 | The plugin is repeatedly loaded. | | 8106 | The system variable name defined by the plugin does not begin with the name of the plugin. | -| 8107 | The loaded plugin does not specify a version, or the version specified is too low. | +| 8107 | The loaded plugin does not specify a version, or the specified version is too low. | | 8108 | Unsupported execution plan type. | -| 8109 | The specified index cannot be found when the index is analyzed. -| 8110 | The Cartesian product operation is not allowed. | Set the `cross-join` in the configuration to `true`. | +| 8109 | The specified index cannot be found when the index is analyzed. | +| 8110 | The Cartesian product operation cannot be executed. | Set `cross-join` in the configuration to `true`. | | 8111 | When executing the `EXECUTE` statement, the corresponding `Prepare` statement cannot be found. | 8112 | The number of parameters in the `EXECUTE` statement is not consistent with the `Prepare` statement. | -| 8113 | The table structure involved in the `Execute` statement has changed after the `Prepare` statement is executed. | +| 8113 | The table schema involved in the `Execute` statement has changed after the `Prepare` statement is executed. | | 8114 | Unknown execution plan type. | -| 8115 | Preparing multiple lines of statements is not supported. | -| 8116 | Preparing DDL statements is not supported. | -| 8118 | Executor build failed. | +| 8115 | It is not supported to prepare multiple lines of statements. | +| 8116 | It is not supported to preparing DDL statements. | +| 8118 | Executor build fails. | | 8120 | The `start tso` of transactions cannot be obtained. | -| 8121 | Privilege check failed. | +| 8121 | Privilege check fails. | | 8122 | Wild cards are specified, but no corresponding table name is found. | | 8123 | An SQL query with aggregate functions returns non-aggregated columns, which violates the `only_full_group_by` mode. | | 8200 | The DDL syntax is not yet supported. | | 8201 | TiDB is currently not the DDL owner. | -| 8202 | This index cannot be decoded. | +| 8202 | The index cannot be decoded. | | 8203 | Illegal DDL worker. | | 8204 | Illegal DDL job. | | 8205 | Illegal DDL job mark. | @@ -96,17 +96,17 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8210 | Illegal DDL state. | | 8211 | Panic occurs during the DDL operation in `re-organize` phase. | | 8212 | Illegal split range of Region. | -| 8213 | Illegal DDL job version | +| 8213 | Illegal DDL job version. | | 8214 | The DDL operation is terminated. | -| 8215 | The `ADMIN REPAIR TABLE` command fails. | -| 8216 | Illegal auto random columns. | -| 8221 | The Key encoding is incorrect. | -| 8222 | The indexing of Key encoding is incorrect. | +| 8215 | `ADMIN REPAIR TABLE` fails. | +| 8216 | Illegal automatic random columns. | +| 8221 | Incorrect Key encoding. | +| 8222 | Incorrect index Key encoding. | | 8223 | This error occurs when detecting that the data is not consistent with the index. | | 8224 | The DDL job cannot be found. | | 8225 | The DDL operation is completed and cannot be canceled. | | 8226 | The DDL operation is almost completed and cannot be canceled. | -| 8227 | Unsupported options are used when creating `Sequence`. | +| 8227 | Unsupported options are used when creating Sequence. | | 9001 | The PD request timed out. | Check the state/monitor/log of the PD server and the network between the TiDB server and the PD server. | | 9002 | The TiKV request timed out. | Check the state/monitor/log of the TiKV server and the network between the TiDB server and the TiKV server. | | 9003 | The TiKV server is busy and this usually occurs when the workload is too high. | Check the state/monitor/log of the TiKV server. | From a3e2256923a9f25d79f502c4462327c21e86c789 Mon Sep 17 00:00:00 2001 From: Ran Date: Wed, 19 Feb 2020 16:42:26 +0800 Subject: [PATCH 04/10] Update error-codes.md --- dev/reference/error-codes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev/reference/error-codes.md b/dev/reference/error-codes.md index 1b824f5335278..6dc988585094f 100644 --- a/dev/reference/error-codes.md +++ b/dev/reference/error-codes.md @@ -45,7 +45,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8044 | The state of index does not exist. | | 8045 | Illegal table data. | | 8046 | The state of column information is invisible. | -| 8047 | The value of the system variable is not supported. It usually occurs in the alarm information after the user sets a variable value that is not supported in the database. +| 8047 | The value of the system variable is not supported. This error usually occurs in the alarm information when the user sets a variable value that is not supported in the database. | 8048 | An unsupported database isolation level is set. | | 8049 | It fails to load the privilege related table. | | 8050 | An unsupported privilege type is set. | From 76ecc4092345ad14f168e9e7f3e44ac64ae975d3 Mon Sep 17 00:00:00 2001 From: Ran Date: Wed, 19 Feb 2020 18:23:58 +0800 Subject: [PATCH 05/10] reference: revise terms --- dev/reference/error-codes.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/dev/reference/error-codes.md b/dev/reference/error-codes.md index 6dc988585094f..15dad5adb1d9d 100644 --- a/dev/reference/error-codes.md +++ b/dev/reference/error-codes.md @@ -20,14 +20,14 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8004 | A single transaction is too large. | See [the error message `transaction too large`](/dev/faq/tidb.md#the-error-message-transaction-too-large-is-displayed) for the cause and solution. | | 8005 | Transactions in TiDB encounter write conflicts. | See [the Troubleshoot section](/dev/faq/tidb.md#troubleshoot) for the cause and solution. | | 8018 | The plugin cannot be reloaded because it has not been loaded before. | -| 8019 | The version of the plugin that are being reloaded is different from the previous version. The plugin cannot be reloaded. | +| 8019 | The version of the plugin that are being reloaded is different from the previous version. Therefore, the plugin cannot be reloaded. | | 8020 | The table is locked. | | 8021 | The key does not exist. | | 8022 | The transaction commit fails. You may retry the process. | | 8023 | An empty value is not allowed. | | 8024 | Illegal transactions. | -| 8025 | A single Key-Value pair that are being written is too large. | -| 8026 | The interface is not implemented. | +| 8025 | The single Key-Value pair that are being written is too large. | +| 8026 | The interface has no implementation. | | 8027 | The table schema version is outdated. | | 8028 | The table schema has changed. | | 8029 | Incorrect value. | @@ -51,12 +51,12 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8050 | An unsupported privilege type is set. | | 8051 | Unknown field type. | | 8052 | The serial number of the data packet from the client is incorrect. | -| 8053 | An illegal auto-incrementing value is obtained. | +| 8053 | An illegal auto-incrementing column value is obtained. | | 8055 | The current snapshot is too old. The data may have been garbage collected. | | 8056 | Illegal table ID. | | 8057 | Illegal field type. | | 8058 | You apply an automatic variable type that does not exist. | -| 8059 | It fails to obtain an automatic random variable. | +| 8059 | It fails to obtain an auto-random ID. | | 8060 | Illegal auto-incrementing offset. | | 8061 | Unsupported SQL Hint. | | 8062 | An illegal token is used in SQL Hint. It conflicts with reserved words in SQL Hint. | @@ -69,21 +69,21 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8103 | The plugin name is incorrect. | | 8104 | The plugin version does not match. | | 8105 | The plugin is repeatedly loaded. | -| 8106 | The system variable name defined by the plugin does not begin with the name of the plugin. | +| 8106 | The plugin defines a system variable name that does not begin with the plugin name. | | 8107 | The loaded plugin does not specify a version, or the specified version is too low. | | 8108 | Unsupported execution plan type. | | 8109 | The specified index cannot be found when the index is analyzed. | | 8110 | The Cartesian product operation cannot be executed. | Set `cross-join` in the configuration to `true`. | -| 8111 | When executing the `EXECUTE` statement, the corresponding `Prepare` statement cannot be found. +| 8111 | When executing the `EXECUTE` statement, the corresponding `Prepare` statement cannot be found. | | 8112 | The number of parameters in the `EXECUTE` statement is not consistent with the `Prepare` statement. | -| 8113 | The table schema involved in the `Execute` statement has changed after the `Prepare` statement is executed. | +| 8113 | The table schema involved in the `EXECUTE` statement has changed after the `Prepare` statement is executed. | | 8114 | Unknown execution plan type. | | 8115 | It is not supported to prepare multiple lines of statements. | -| 8116 | It is not supported to preparing DDL statements. | +| 8116 | It is not supported to prepare DDL statements. | | 8118 | Executor build fails. | | 8120 | The `start tso` of transactions cannot be obtained. | | 8121 | Privilege check fails. | -| 8122 | Wild cards are specified, but no corresponding table name is found. | +| 8122 | No corresponding table name is found, given the specified wild cards. | | 8123 | An SQL query with aggregate functions returns non-aggregated columns, which violates the `only_full_group_by` mode. | | 8200 | The DDL syntax is not yet supported. | | 8201 | TiDB is currently not the DDL owner. | @@ -91,7 +91,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8203 | Illegal DDL worker. | | 8204 | Illegal DDL job. | | 8205 | Illegal DDL job mark. | -| 8206 | The DDL operation in `re-organize` phase timed out. +| 8206 | The DDL operation in `re-organize` phase timed out. | | 8207 | Illegal storage nodes. | | 8210 | Illegal DDL state. | | 8211 | Panic occurs during the DDL operation in `re-organize` phase. | From d640b28effe78ff62c270608bba875c36fad63be Mon Sep 17 00:00:00 2001 From: Ran Date: Wed, 19 Feb 2020 18:31:19 +0800 Subject: [PATCH 06/10] reference: update minor change in error-codes --- dev/reference/error-codes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev/reference/error-codes.md b/dev/reference/error-codes.md index 15dad5adb1d9d..e89db47583390 100644 --- a/dev/reference/error-codes.md +++ b/dev/reference/error-codes.md @@ -69,7 +69,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8103 | The plugin name is incorrect. | | 8104 | The plugin version does not match. | | 8105 | The plugin is repeatedly loaded. | -| 8106 | The plugin defines a system variable name that does not begin with the plugin name. | +| 8106 | The plugin defines a system variable whose name does not begin with the plugin name. | | 8107 | The loaded plugin does not specify a version, or the specified version is too low. | | 8108 | Unsupported execution plan type. | | 8109 | The specified index cannot be found when the index is analyzed. | From b3a34da2f69b103eb86da854a0a9e65771605908 Mon Sep 17 00:00:00 2001 From: Ran Date: Wed, 19 Feb 2020 18:33:12 +0800 Subject: [PATCH 07/10] reference: minor change in error-codes --- dev/reference/error-codes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev/reference/error-codes.md b/dev/reference/error-codes.md index e89db47583390..0be8bcb620c14 100644 --- a/dev/reference/error-codes.md +++ b/dev/reference/error-codes.md @@ -20,7 +20,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8004 | A single transaction is too large. | See [the error message `transaction too large`](/dev/faq/tidb.md#the-error-message-transaction-too-large-is-displayed) for the cause and solution. | | 8005 | Transactions in TiDB encounter write conflicts. | See [the Troubleshoot section](/dev/faq/tidb.md#troubleshoot) for the cause and solution. | | 8018 | The plugin cannot be reloaded because it has not been loaded before. | -| 8019 | The version of the plugin that are being reloaded is different from the previous version. Therefore, the plugin cannot be reloaded. | +| 8019 | The version of the plugin that is being reloaded is different from the previous version. Therefore, the plugin cannot be reloaded. | | 8020 | The table is locked. | | 8021 | The key does not exist. | | 8022 | The transaction commit fails. You may retry the process. | From 30c05395a651d5b17f1c4507269c57cd978bd480 Mon Sep 17 00:00:00 2001 From: Ran Date: Fri, 21 Feb 2020 12:15:09 +0800 Subject: [PATCH 08/10] change choice of words Co-Authored-By: Jack Yu --- dev/reference/error-codes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev/reference/error-codes.md b/dev/reference/error-codes.md index 0be8bcb620c14..2a3ce3ef7c863 100644 --- a/dev/reference/error-codes.md +++ b/dev/reference/error-codes.md @@ -76,7 +76,7 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8110 | The Cartesian product operation cannot be executed. | Set `cross-join` in the configuration to `true`. | | 8111 | When executing the `EXECUTE` statement, the corresponding `Prepare` statement cannot be found. | | 8112 | The number of parameters in the `EXECUTE` statement is not consistent with the `Prepare` statement. | -| 8113 | The table schema involved in the `EXECUTE` statement has changed after the `Prepare` statement is executed. | +| 8113 | The table schema related in the `EXECUTE` statement has changed after the `Prepare` statement is executed. | | 8114 | Unknown execution plan type. | | 8115 | It is not supported to prepare multiple lines of statements. | | 8116 | It is not supported to prepare DDL statements. | From 84a742c7d32c619c34dbd6aea9e470f803e3381e Mon Sep 17 00:00:00 2001 From: Ran Date: Fri, 21 Feb 2020 16:00:15 +0800 Subject: [PATCH 09/10] Apply suggestions from code review Co-Authored-By: Lilian Lee --- dev/reference/error-codes.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/dev/reference/error-codes.md b/dev/reference/error-codes.md index 2a3ce3ef7c863..896d2d8677ac0 100644 --- a/dev/reference/error-codes.md +++ b/dev/reference/error-codes.md @@ -23,11 +23,11 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8019 | The version of the plugin that is being reloaded is different from the previous version. Therefore, the plugin cannot be reloaded. | | 8020 | The table is locked. | | 8021 | The key does not exist. | -| 8022 | The transaction commit fails. You may retry the process. | +| 8022 | The transaction commit fails. You can retry the process. | | 8023 | An empty value is not allowed. | -| 8024 | Illegal transactions. | -| 8025 | The single Key-Value pair that are being written is too large. | -| 8026 | The interface has no implementation. | +| 8024 | Invalid transactions. | +| 8025 | The single Key-Value pair being written is too large. | +| 8026 | The interface has not been implemented. | | 8027 | The table schema version is outdated. | | 8028 | The table schema has changed. | | 8029 | Incorrect value. | @@ -38,14 +38,14 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8034 | Incorrect `datetime` value. | | 8036 | Illegal `time` format. | | 8037 | Illegal `week` format. | -| 8038 | The field cannot obtain a default value. | +| 8038 | The field fails to obtain the default value. | | 8039 | Index offset is out of range. | | 8042 | The state of table schema does not exist. | | 8043 | The state of column information does not exist. | | 8044 | The state of index does not exist. | | 8045 | Illegal table data. | | 8046 | The state of column information is invisible. | -| 8047 | The value of the system variable is not supported. This error usually occurs in the alarm information when the user sets a variable value that is not supported in the database. +| 8047 | The value of the system variable is not supported. This error usually occurs in the alarm information when the user sets a variable value that is not supported in the database. | | 8048 | An unsupported database isolation level is set. | | 8049 | It fails to load the privilege related table. | | 8050 | An unsupported privilege type is set. | From fbee6083f644e55589759dd65837717f959f66f1 Mon Sep 17 00:00:00 2001 From: Ran Date: Fri, 21 Feb 2020 16:04:28 +0800 Subject: [PATCH 10/10] Replace illegal with invalid --- dev/reference/error-codes.md | 40 ++++++++++++++++++------------------ 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/dev/reference/error-codes.md b/dev/reference/error-codes.md index 896d2d8677ac0..da5612c0f49e5 100644 --- a/dev/reference/error-codes.md +++ b/dev/reference/error-codes.md @@ -33,17 +33,17 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8029 | Incorrect value. | | 8030 | After an unsigned positive integer is converted to a signed integer, it exceeds the maximum value and displays as a negative integer.| | 8031 | When being converted to an unsigned integer, a negative integer is converted to a positive integer. | -| 8032 | Illegal `year` format. | -| 8033 | Illegal `year` value. | +| 8032 | Invalid `year` format. | +| 8033 | Invalid `year` value. | | 8034 | Incorrect `datetime` value. | -| 8036 | Illegal `time` format. | -| 8037 | Illegal `week` format. | +| 8036 | Invalid `time` format. | +| 8037 | Invalid `week` format. | | 8038 | The field fails to obtain the default value. | | 8039 | Index offset is out of range. | | 8042 | The state of table schema does not exist. | | 8043 | The state of column information does not exist. | | 8044 | The state of index does not exist. | -| 8045 | Illegal table data. | +| 8045 | Invalid table data. | | 8046 | The state of column information is invisible. | | 8047 | The value of the system variable is not supported. This error usually occurs in the alarm information when the user sets a variable value that is not supported in the database. | | 8048 | An unsupported database isolation level is set. | @@ -51,19 +51,19 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8050 | An unsupported privilege type is set. | | 8051 | Unknown field type. | | 8052 | The serial number of the data packet from the client is incorrect. | -| 8053 | An illegal auto-incrementing column value is obtained. | +| 8053 | An invalid auto-incrementing column value is obtained. | | 8055 | The current snapshot is too old. The data may have been garbage collected. | -| 8056 | Illegal table ID. | -| 8057 | Illegal field type. | +| 8056 | Invalid table ID. | +| 8057 | Invalid field type. | | 8058 | You apply an automatic variable type that does not exist. | | 8059 | It fails to obtain an auto-random ID. | -| 8060 | Illegal auto-incrementing offset. | +| 8060 | Invalid auto-incrementing offset. | | 8061 | Unsupported SQL Hint. | -| 8062 | An illegal token is used in SQL Hint. It conflicts with reserved words in SQL Hint. | +| 8062 | An invalid token is used in SQL Hint. It conflicts with reserved words in SQL Hint. | | 8063 | The limited memory usage set in SQL Hint exceeds the upper limit of the system. The setting in SQL Hint is ignored. | | 8064 | It fails to parse SQL Hint. | -| 8065 | An illegal integer is used in SQL Hint. | -| 8066 | The second parameter in the `JSON_OBJECTAGG` function is illegal. | +| 8065 | An invalid integer is used in SQL Hint. | +| 8066 | The second parameter in the `JSON_OBJECTAGG` function is invalid. | | 8101 | The format of plugin ID is incorrect. | The correct format is `[name]-[version]`, and no `-` is allowed in `name` and `version`. | | 8102 | Unable to read the plugin definition information. | | 8103 | The plugin name is incorrect. | @@ -88,18 +88,18 @@ TiDB is compatible with the error codes in MySQL, and in most cases returns the | 8200 | The DDL syntax is not yet supported. | | 8201 | TiDB is currently not the DDL owner. | | 8202 | The index cannot be decoded. | -| 8203 | Illegal DDL worker. | -| 8204 | Illegal DDL job. | -| 8205 | Illegal DDL job mark. | +| 8203 | Invalid DDL worker. | +| 8204 | Invalid DDL job. | +| 8205 | Invalid DDL job mark. | | 8206 | The DDL operation in `re-organize` phase timed out. | -| 8207 | Illegal storage nodes. | -| 8210 | Illegal DDL state. | +| 8207 | Invalid storage nodes. | +| 8210 | Invalid DDL state. | | 8211 | Panic occurs during the DDL operation in `re-organize` phase. | -| 8212 | Illegal split range of Region. | -| 8213 | Illegal DDL job version. | +| 8212 | Invalid split range of Region. | +| 8213 | Invalid DDL job version. | | 8214 | The DDL operation is terminated. | | 8215 | `ADMIN REPAIR TABLE` fails. | -| 8216 | Illegal automatic random columns. | +| 8216 | Invalid automatic random columns. | | 8221 | Incorrect Key encoding. | | 8222 | Incorrect index Key encoding. | | 8223 | This error occurs when detecting that the data is not consistent with the index. |