update error code

docs-2.0/20.appendix/0.FAQ.md

@@ -47,6 +47,7 @@ From Nebula Graph version 3.0.0, the Storage services added in the configuration
 
 From Nebula Graph version 3.0.0, patterns support matching multiple tags at the same time, so you need to specify a tag name when querying properties. The original statement `RETURN variable_name.property_name` is changed to `RETURN variable_name.<tag_name>.property_name`.
 
+<!--
 ### "How to resolve `[ERROR (-1005)]: Used memory hits the high watermark(0.800000) of total system memory.`?"
 
 The reason for this error may be that `system_memory_high_watermark_ratio` specifies the trigger threshold of the memory high watermark alarm mechanism. The default value is `0.8`. If the system memory usage is higher than this value, an alarm mechanism will be triggered, and Nebula Graph will stop querying.
@@ -56,6 +57,8 @@ Possible solutions are as follows:
 * Clean the system memory to make it below the threshold.
 * [Modify the Graph configuration](../5.configurations-and-logs/1.configurations/1.configurations.md). Add the `system_memory_high_watermark_ratio` parameter to the configuration files of all Graph servers, and set it greater than `0.8`, such as `0.9`.
 
+-->
+
 ### "How to resolve the error `Storage Error E_RPC_FAILURE`?"
 
 The reason for this error is usually that the storaged process returns too many data back to the graphd process. Possible solutions are as follows:
@@ -70,6 +73,7 @@ The reason for this error is usually that the storaged process returns too many
 
 It is a known issue. Just retry 1 to N times, where N is the partition number. The reason is that the meta client needs some heartbeats to update or errors to trigger the new leader information.
 
+<!--
 ### "How to resolve `[ERROR (-1005)]: Schema not exist: xxx`?"
 
 If the system returns `Schema not exist` when querying, make sure that:
@@ -78,6 +82,8 @@ If the system returns `Schema not exist` when querying, make sure that:
 
 - Whether the name of the tag or the edge type is a keyword. If it is a keyword, enclose them with backquotes (\`). For more information, see [Keywords](../3.ngql-guide/1.nGQL-overview/keywords-and-reserved-words.md).
 
+-->
+
 ### Unable to download SNAPSHOT packages when compiling Exchange, Connectors, or Algorithm
 
 Problem description: The system reports `Could not find artifact com.vesoft:client:jar:xxx-SNAPSHOT` when compiling.
@@ -103,7 +109,7 @@ Solution: Add the following configuration in the `profiles` scope of Maven's `se
   </profile>
 ```
 
-### "How to resolve `[ERROR (-7)]: SyntaxError: syntax error near`?"
+### "How to resolve `[ERROR (-1004)]: SyntaxError: syntax error near`?"
 
 In most cases, a query statement requires a `YIELD` or a `RETURN`. Check your query statement to see if `YIELD` or `RETURN` is provided.
 

docs-2.0/3.ngql-guide/10.tag-statements/2.drop-tag.md

@@ -14,7 +14,7 @@ This operation only deletes the Schema data. All the files or directories in the
 
 - Running the `DROP TAG` statement requires some [privileges](../../7.data-security/1.authentication/3.role-list.md) for the graph space. Otherwise, Nebula Graph throws an error.
 
-- Before you drop a tag, make sure that the tag does not have any indexes. Otherwise, the conflict error (`[ERROR (-8)]: Conflict!`) will be returned when you run the `DROP TAG` statement. To drop an index, see [DROP INDEX](../14.native-index-statements/6.drop-native-index.md).
+- Before you drop a tag, make sure that the tag does not have any indexes. Otherwise, the conflict error (`[ERROR (-1005)]: Conflict!`) will be returned when you run the `DROP TAG` statement. To drop an index, see [DROP INDEX](../14.native-index-statements/6.drop-native-index.md).
 
 ## Syntax
 

docs-2.0/3.ngql-guide/10.tag-statements/3.alter-tag.md

@@ -6,7 +6,7 @@
 
 - Running the `ALTER TAG` statement requires some [privileges](../../7.data-security/1.authentication/3.role-list.md) for the graph space. Otherwise, Nebula Graph throws an error.
 
-- Before you alter properties for a tag, make sure that the properties are not indexed. If the properties contain any indexes, the conflict error `[ERROR (-8)]: Conflict!` will occur when you `ALTER TAG`. For more information on dropping an index, see [DROP INDEX](../14.native-index-statements/6.drop-native-index.md).
+- Before you alter properties for a tag, make sure that the properties are not indexed. If the properties contain any indexes, the conflict error `[ERROR (-1005)]: Conflict!` will occur when you `ALTER TAG`. For more information on dropping an index, see [DROP INDEX](../14.native-index-statements/6.drop-native-index.md).
 
 ## Syntax
 

docs-2.0/3.ngql-guide/11.edge-type-statements/2.drop-edge.md

@@ -10,7 +10,7 @@ This operation only deletes the Schema data. All the files or directories in the
 
 - Running the `DROP EDGE` statement requires some [privileges](../../7.data-security/1.authentication/3.role-list.md) for the graph space. Otherwise, Nebula Graph throws an error.
 
-- Before you drop an edge type, make sure that the edge type does not have any indexes. Otherwise, the conflict error (`[ERROR (-8)]: Conflict!`) will be returned. To drop an index, see [DROP INDEX](../14.native-index-statements/6.drop-native-index.md).
+- Before you drop an edge type, make sure that the edge type does not have any indexes. Otherwise, the conflict error (`[ERROR (-1005)]: Conflict!`) will be returned. To drop an index, see [DROP INDEX](../14.native-index-statements/6.drop-native-index.md).
 
 ## Syntax
 

docs-2.0/3.ngql-guide/11.edge-type-statements/3.alter-edge.md

@@ -6,7 +6,7 @@
 
 - Running the `ALTER EDGE` statement requires some [privileges](../../7.data-security/1.authentication/3.role-list.md) for the graph space. Otherwise, Nebula Graph throws an error.
 
-- Before you alter properties for an edge type, make sure that the properties are not indexed. If the properties contain any indexes, the conflict error `[ERROR (-8)]: Conflict!` will occur when you `ALTER EDGE`. For more information on dropping an index, see [DROP INDEX](../14.native-index-statements/6.drop-native-index.md).
+- Before you alter properties for an edge type, make sure that the properties are not indexed. If the properties contain any indexes, the conflict error `[ERROR (-1005)]: Conflict!` will occur when you `ALTER EDGE`. For more information on dropping an index, see [DROP INDEX](../14.native-index-statements/6.drop-native-index.md).
 
 ## Syntax
 

docs-2.0/3.ngql-guide/12.vertex-statements/1.insert-vertex.md

@@ -156,7 +156,7 @@ nebula> INSERT VERTEX t5(p1, p2, p3) VALUES "001":("Abe", 2, 3);
 
 # In the following example, the insertion fails because the value of p1 cannot be NULL.
 nebula> INSERT VERTEX t5(p1, p2, p3) VALUES "002":(NULL, 4, 5);
-[ERROR (-1005)]: Storage Error: The not null field cannot be null.
+[ERROR (-1009)]: SemanticError: No schema found for `t5'
 
 # In the following example, the value of p3 is the default NULL.
 nebula> INSERT VERTEX t5(p1, p2) VALUES "003":("cd", 5);

docs-2.0/3.ngql-guide/17.query-tuning-statements/6.kill-query.md

@@ -28,5 +28,5 @@ nebula> KILL QUERY(SESSION=1625553545984255,PLAN=163);
 The query will be terminated and the following information will be returned.
 
 ```ngql
-[ERROR (-1005)]: Execution had been killed
+[ERROR (-1005)]: ExecutionPlanId[1001] does not exist in current Session.
 ```