After an error occurs, an error code and an error message are returned. The following sections describe the cause of each error to help you troubleshoot the errors that may occur during your use of OpenSearch.
Common errors
Error code | Description |
1000 | A timeout error occurs. Try again and check whether the error still occurs. If the error still exists, submit a ticket. |
2112 | The field referenced in a feature function, such as text_relevance(field) or fieldterm_proximity(field), in a sort expression must be a source index field of a query. Otherwise, an error is returned, but the search results are not affected. |
3007 | The error code is returned because the interval at which API operations are called to push data exceeds the limit. We recommend that you call API operations at an appropriate interval. |
4003 | Use the sample document to check whether the same signature result is returned. This method can be used to check whether the error is caused by the signature algorithm. If the error is not caused by the signature algorithm, check whether the common parameters in uppercase rank before the request parameters in lowercase after all these parameters are sorted in alphabetical order. In addition, you can use encoding rules to check spaces. For more information, see the authorization documentation. |
4007 | A format may fail to be parsed because the JSON field contains double quotation marks (" ") or non-printable characters. In this case, use an escape character or specify a filter condition. Then, try again. |
4010 | The format or value of the TimeStamp parameter is invalid. Configure this parameter based on the current time in the valid format. |
5001 | The user does not exist. This error may be caused because the AccessKey pair is invalid or the API endpoint is invalid. Make sure that the AccessKey pair and the API endpoint are valid, and try again. To view the API endpoint, perform the following operations: Log on to the OpenSearch console. In the left-side navigation pane, click Instance Management. Find the application that you want to manage and click Details in the Actions column. In the API Endpoint section, view the API endpoint. |
5008 | OpenSearch verifies your identity by using the AccessKey pair. Make sure that your AccessKey pair is enabled. You can log on to the OpenSearch console and create or delete an AccessKey pair on the AccessKey management page. |
6013 | The sum of the values of the start and hit parameters cannot exceed 5000. Otherwise, an error is returned and no result is returned. For requests in which the sum of the values of the start and hit parameters exceeds 5000, check whether the configurations of a scroll search meet the requirements specified in the API reference. |
6015 | The request is discarded because the logical computing units (LCUs) of computing resources exceed the purchased quota. To increase the quota, perform the following operations: Log on to the OpenSearch console. In the left-side navigation pane, click Instance Management. Find the application that you want to manage and choose More > Change Specifications/Quotas in the Actions column. On the page that appears, increase the quota of computing resources. |
6127 | The fields referenced in clauses other than query clauses must be configured as attribute fields. Modify the application schema and try again. You can configure the attribute fields by performing offline changes. For more information, see Modify Offline Application. |
7500 | An internal error occurs. Submit a ticket. |
System errors whose error codes range from 1000 to 1999
Error code | Description |
1000 | An internal error occurs. |
1001 | The template does not exist. |
1003 | The index type is invalid. |
1004 | The service is unavailable. Try again later. |
Application-related errors whose error codes range from 2000 to 2999
Error code | Description |
2001 | The specified application does not exist. |
2002 | The specified application already exists. |
2003 | The number of applications has reached the upper limit. |
2004 | The application name is invalid. The application name can be up to 30 characters in length, and can contain digits, letters, and underscores (_). |
2005 | The application name is not specified. |
2006 | The new application name is not specified. |
2007 | The description exceeds the upper limit in length. The description can be up to 300 characters in length. |
2008 | A summary parameter is invalid. |
2009 | Failed to update the status of the application. |
2010 | The application is paused. |
2011 | The application is frozen. |
2012 | The application is not started. |
2013 | The delete operation failed because the application does not exist. |
2014 | Failed to upload the file. |
2016 | The region is not specified. |
2017 | The application does not reside in the current region. |
2099 | This operation is unavailable. |
2101 | The expression does not exist. |
2102 | The expression name already exists. |
2103 | The number of expressions in the application has reached the upper limit. |
2104 | The expression name is invalid. The expression name can be up to 30 characters in length, and can contain digits, letters, and underscores (_). |
2105 | The expression name is not specified. |
2106 | The new expression name is not specified. |
2107 | The expression description exceeds the upper limit in length. The expression description can be up to 300 characters in length. |
2108 | The format of the expression description is invalid. |
2109 | The expression format is invalid. |
2110 | The expression exceeds the upper limit in length. |
2111 | The expression ID is not specified. |
2112 | The expression is invalid. |
2113 | The expression is empty. |
2114 | An operation error occurs. |
2201 | The name of the rough sort expression is not specified. |
2202 | The name of the rough sort expression already exists. |
2203 | The number of rough sort expressions exceeds the upper limit. |
2204 | The name of the rough sort expression is invalid. The name can contain only digits, letters, and underscores (_). |
2205 | The name of the rough sort expression exceeds the upper limit in length. |
2206 | The fields used for rough sort are not of numeric types. |
2207 | The rough sort expression does not exist. |
2208 | The rough sort expression is invalid. Make sure that fields are specified in the rough sort expression. |
2209 | The weight configuration in the rough sort expression is invalid. Make sure that a weight value is a non-zero numeric value that ranges from -100000 to 100000. A numeric value of the FLOAT type can be precise to six decimal places. |
2210 | The name is used by the default rough sort expression in the system. |
2211 | The parameter value in the timeliness() function is not of the INT type. |
2112 | The sort expression is invalid. |
2551 | The drop-down suggestion rule that is specified in the query does not exist. |
Document-related errors whose error codes range from 3000 to 3999
Error code | Description |
3001 | The document is empty. |
3002 | The document size exceeds the upper limit. |
3003 | The number of documents has reached the upper limit. |
3004 | Failed to save the document. |
3005 | The document format is invalid. |
3006 | The command that is used to process the document is invalid. |
3007 | Excessive requests are submitted in a short period of time. |
3008 | The document size is excessively large. |
3009 | No document ID is specified. |
3011 | You cannot push documents by calling API operations after an ApsaraDB RDS for MySQL or MySQL data source is configured. |
3012 | The specified resource does not exist. |
3013 | The rate at which documents are pushed exceeds the maximum threshold specified in the application. |
3014 | The rate at which documents are pushed exceeds the system limit. |
3015 | The number of documents that are pushed each time exceeds the upper limit. |
3016 | The total number of documents in the application exceeds the upper limit. |
Authorization-related errors whose error codes range from 4000 to 4999
Error code | Description |
4001 | The authentication failed. |
4002 | No signature is configured. |
4003 | Failed to verify the signature. |
4004 | The SignatureNonce parameter is not specified. |
4005 | The value of the SignatureNonce parameter is not unique. |
4006 | The SignatureNonce verification failed. |
4007 | Failed to parse the JSON format. |
4008 | No username is specified. Check whether the domain name is correct. |
4009 | The user ID is not specified. |
4010 | The timestamp is invalid. |
4011 | This operation is not allowed for a demo account. |
4012 | The specified table does not exist. |
4013 | The timestamp format is invalid. |
4014 | The Timestamp parameter is not specified. |
4020 | Failed to authenticate the RAM user. |
User-related errors whose error codes range from 5000 to 5999
Error code | Description |
5001 | The user does not exist. |
5002 | The username is invalid. |
5003 | You have not logged on. |
5008 | The AccessKey pair is disabled. |
5100 | You are not authorized to perform operations in this region. |
5004 | You have overdue payments. |
5005 | The OpenSearch service is not activated. Go to the Alibaba Cloud official website to activate the service. |
5006 | The specified application is frozen due to overdue payments. |
5008 | The AccessKey pair is disabled. |
5009 | The user is deleted. |
5010 | The AccessKey pairs are disabled. |
5011 | Multiple users are registered by using the same email address. |
5012 | CODE_USER_ALIYUN_USER_ID_INVALID. No error message is returned. |
5013 | CODE_USER_ALIYUN_BID_INVALID. No error message is returned. |
5014 | CODE_USER_CLIENT_ID_INVALID. No error message is returned. |
5015 | CODE_USER_ID_INVALID. No error message is returned. |
5100 | You are not authorized to perform operations in this region. |
Search-related errors whose error codes range from 6000 to 6999
Error code | Description |
6001 | No search query is entered. |
2022 | The application version is unavailable. Reindexing is not complete for the version. |
6002 | The keyword used to search for a key is invalid. |
6003 | The keyword used to search for a field is invalid. |
6004 | Complex queries are not specified. |
6005 | The field is invalid. |
6006 | Excessive application names are contained in the request. |
6007 | The total number of indexes in each template for a multi-index query exceeds the upper limit. |
6008 | Failed to parse the request due to a syntax error. |
6009 | The query clause is too long. |
6010 | The rerank size is invalid. |
6011 | The SignatureNonce format is invalid. |
6013 | The sum of the values of the start and hit parameters exceeds the upper limit. |
6014 | The request is discarded because the system is busy. |
6015 | The request is discarded because the LCUs of computing resources exceed the purchased quota. |
6016 | The request is discarded because the number of query hits exceeds the upper limit. The value range is [0,500]. |
6017 | The scroll parameter is specified, but the search_type parameter is not set to scan. |
6018 | The scroll parameter is specified, but the search_type parameter is not specified. |
6019 | Failed to parse the scroll_id parameter. |
6020 | The value of the scroll parameter is invalid. |
6021 | The aggregate, sort, or distinct clause is not supported by scroll requests. |
6022 | The value of the scroll_id parameter has expired. |
6024 | The value of the hit parameter in the drop-down suggestion is invalid. |
6031 | The value of the abtest parameter is invalid. |
6033 | The value of the re_search parameter is invalid. |
6034 | The value of the biz parameter is invalid. |
6100 | No search query is specified. |
6101 | The index field of the query does not exist. |
6102 | The numeric value range in the query clause is invalid. |
6103 | The return value of the expression in the filter clause is not of the BOOLEAN type. |
6104 | The return value of the expression in the sort clause is of the BOOLEAN type. |
6105 | Same expressions are contained in the sort clause. |
6106 | The query clause in the query is invalid. |
6107 | The return value of the statistical function is of the BOOLEAN or STRING type. |
6108 | The range specified in the statistical function is not in ascending order. |
6109 | The data type of the value returned by the range expression in the statistical function is invalid. |
6110 | The statistical function does not exist. |
6111 | The statistical function is invalid. |
6112 | The query clause is invalid. |
6113 | The filter clause is invalid. |
6114 | The aggregate clause is invalid. |
6115 | The sort clause is invalid. |
6116 | The distinct clause is invalid. |
6117 | The query contains unknown clauses. |
6118 | A syntax error occurs. |
6119 | The value of the dist_count parameter in the distinct clause is invalid. This value must be an integer greater than 0. |
6120 | The value of the dist_times parameter in the distinct clause is invalid. This value must be an integer greater than 0. |
6121 | The value of the reserved parameter in the distinct clause is invalid. This parameter must be set to true or false. |
6122 | The distinct_key parameter is not specified in the distinct clause. |
6123 | The value of the grade parameter in the distinct clause is invalid. For example, this parameter is left empty or set to a non-numeric value. |
6124 | The value of the distinct parameter in the distinct clause is invalid. The value must be within the range of (0,2]. |
6125 | The value of the max_item_count parameter in the distinct clause is invalid. This value must be an integer greater than 0. |
6126 | The value of the update_total_hit parameter in the distinct clause is invalid. This parameter must be set to true or false. |
6127 | The request contains undefined attribute fields. Modify the application schema and try again. You can configure the attribute fields by performing offline changes. For more information, see Modify Offline Application. |
6128 | The data types of the operands that surround the binary operator in the expression are different. |
6129 | The operands that surround the binary operator in the expression are constants at the same time. |
6130 | The value type of the binary logic operation expression is invalid. The value must be of the BOOLEAN type. |
6131 | The values in the binary expression are of the STRING type, which is not supported. |
6132 | The values in the binary expression are of the ARRAY type, which is not supported. |
6133 | The value type of the bit manipulation is invalid. |
6134 | The data type of the value returned by the constant expression is invalid. |
6135 | The value type of the constant expression is invalid. |
6140 | A syntax error occurs in the aggregate clause. The SUM function is used when the field is of the LITERAL type. The SUM function does not support a field of the LITERAL type. |
6300 | The values in the constant expression are not integers or floating-point numbers. |
6301 | The operands on which you want to perform bitwise negation are not integers. |
6302 | The operands on which you want to perform negation are not numbers. |
6303 | The operands on which you want to perform logical NOT operations are not numbers. |
6304 | The data type of the operand on which the binary operation is performed is invalid. |
6305 | The binary operator is invalid. |
6306 | The parameter type of the function is invalid. |
6307 | The function is undefined. |
6308 | The number of parameters in the function is invalid. |
6309 | The array operation is invalid. |
6310 | No field can be filtered. |
6311 | An array field is used as a single-value field. |
6312 | A single-value field is used as an array field. |
6313 | The subscript value of the array field is invalid. Make sure that the subscript value is not less than 0. |
6314 | The field type is invalid. |
6315 | The parameter that specifies an index field does not exist. |
6316 | No index is specified in the query. |
6317 | A formula is used more than once in the filter clause. Make sure that each formula is used only once in a filter clause. |
6318 | Failed to parse the formula syntax. |
6400 | The sort script does not exist. |
6450 | An error occurs when the script is being used. |
6500 | The search syntax contains fields that do not exist. |
6501 | No index data is contained in the online system. |
6502 | The syntax of the query is invalid. |
6503 | The default operator OR is not supported. |
6504 | Accurate statistics are not supported. |
6505 | The rank size is invalid. |
6506 | An excessive number of terms are obtained after query analysis. |
6601 | An index field is contained in more than one rule. Make sure that each index field is contained only in one rule. |
6602 | No search query is specified. For example, default:" is specified. |
6603 | The index field in the query is not specified in the query analysis rule. |
6604 | The keyword is not enclosed in single quotation marks (' '). For example, default:xxx is specified. The valid form is default:'xxx'. |
6605 | The keyword is enclosed in double quotation marks (" "). In this case, query analysis rules cannot be configured. |
6606 | The search query does not contain the index that needs to be analyzed. |
6607 | The format of the disable parameter is invalid. |
6608 | The index field to be disabled based on the disable parameter does not exist. |
6609 | A list of features to be disabled based on the disable parameter does not exist. |
6610 | The query obtained after query analysis is empty. This may be caused because the original query is empty or the original query contains only stop words. |
6611 | No index field is specified in the query. |
6612 | The intervention data does not take effect. |
6136 | An invalid expression is used in the clause, such as sort=-2, where -2 is a constant. |
Data processing errors whose error codes range from 7000 to 7999
Error code | Description |
7202 | The command is invalid. Only UPDATE, ADD, and DELETE commands are supported. |
7301 | Failed to push data because the primary key field of the document does not exist. |
7302 | The data type does not match. Data failed to be pushed because the primary key value of the document is invalid. |
7303 | Failed to push data because multiple primary key values are contained in the document. |
7304 | Failed to push data because the primary key value of the document is empty. |
7305 | Failed to push data because the table name does not exist in the current application. |
7500 | An internal error occurs. Submit a ticket. |
7520 | Failed to push data because the size of a single document exceeds 1 MB, which is the upper limit specified in the system. |
7503 | Failed to push data because the field value that is obtained by using the JSON plug-in is not in the JSON format. Check and try again. |
7504 | Failed to push data because the key corresponding to the field value that is obtained by using the JSON plug-in does not exist. |
7505 | A configuration error occurs in content conversion by using the TairLDBExtractor plug-in. As a result, the connection to Tair fails. Check whether the configuration ID or namespace is valid. |
7510 | Failed to push data because an error occurs in field processing by using the KeyValueExtractor plug-in. |
7515 | An error occurs when the filter condition is being used. |
7523 | Failed to push data because an error occurs in data processing by using the StringConnector plug-in. |
7524 | The value of the geo field is outside the value range. The longitude or latitude value of the range field is outside the value range. The longitude value must be greater than 180, and the latitude value must be greater than 90. |
7525 | The formats of the geo and range fields are invalid. |
7601 | An error occurs when the task is running. Submit a ticket. |
7602 | No data is contained in the MaxCompute table. Make sure that data can be generated in the MaxCompute table partitions and try again. |
7607 | You have no permissions on the MaxCompute table. |
7603 | An error occurs when an ApsaraDB RDS for MySQL or PolarDB for MySQL data source is being configured. |
7605 | A configuration error occurs in Taobao Distributed Data Layer (TDDL). |
7608 | A source field does not exist in the MySQL data source. |
7803 | Failed to push data because the document to be updated does not exist. |
7805 | Failed to push data because an error occurs in data processing by using the HTML plug-in. |
7807 | The field type and value do not match. As a result, the field type fails to be converted. The missing value will be imputed with a default value. |
73106 | The number of data push operations has reached the upper limit. Increase the quota. |
Document-related internal errors whose error codes range from 8000 to 8999
Error code | Description |
8001 | Failed to save the error message. |
8002 | The required parameters are missing. |
8003 | The application does not exist. |
8004 | One or more parameters are invalid. |
Template-related errors whose error codes range from 9000 to 9999
Error code | Description |
9001 | The username is not specified. |
9002 | The application name is not specified. |
9003 | The template name is invalid. The template name can contain only digits, letters, and underscores (_). |
9004 | The template name exceeds the upper limit in length. The template name can be up to 30 characters in length. |
9005 | An error occurs when you query the template information. |
9006 | The template name already exists. |
9007 | An error occurs when you insert data into the template. |
9008 | Data is invalid. |
9009 | The number of fields that can be defined exceeds the upper limit specified in the system. |
9010 | The name of this field is reserved. |
9011 | The field name already exists. |
9012 | The index name does not meet the requirements. An index name can be up to 30 characters in length. It can contain digits, letters, and underscores (_), and must start with a letter. The multi-value field cannot be of the SWS_TEXT or TEXT type. |
9013 | Arrays are not supported. |
9014 | Primary keys are not supported. |
9015 | No primary key is specified. |
9016 | The primary key is not unique. |
9017 | Failed to update the information. |
9018 | Failed to delete the information. |
9019 | The number of search fields exceeds the upper limit. The maximum number of search fields that contain multiple index fields is four. |
9020 | An index field of the STRING or TEXT type is used in multiple single-field search fields. |
9021 | The index name does not meet the requirements. An index name can be up to 30 characters in length. It can contain digits, letters, and underscores (_), and must start with a letter. |
9022 | An association is established with this table. |
9023 | The index name contains different types of fields, which is not allowed. |
9100 | An internal error occurs. |
9101 | The quantity of the field exceeds the upper limit. |
9102 | This data source is not used. |
9103 | The connection to a secondary table is invalid. |
9104 | The number of association levels exceeds the upper limit. The maximum number of association levels is two. |
9105 | The template to be checked does not exist. |
9501 | The username is not specified. |
9502 | The application name is not specified. |
9519 | The template is not specified. |
9600 | An internal error occurs. |
9902 | The field type of the plug-in is invalid. |
9999 | This service is unavailable for this domain name. |
Data synchronization-related errors whose error codes range from 10000 to upwards
Error code | Description |
10001 | Failed to obtain the TDDL information because the TDDL group key is not specified. |
10002 | Failed to obtain the field or the table does not exist. |
10011 | Failed to connect to Aggregator. |
10012 | The application contains documents. |
10013 | The application schema is not a custom one. |
10110 | The task is complete. |
10010 | Specific data sources contain invalid data. The invalid data is ignored. |
10014 | The data source type is invalid. |
10100 | Failed to create the task. Specific tasks are in process. |
10101 | The application ID is not specified. |
10106 | The application ID is not specified. |
10107 | The application ID is not specified. |
10102 | The action is invalid. |
10112 | The number of documents exceeds the upper limit. |
10201 | Failed to obtain the quota list. |
10202 | Failed to update the quota. |
10301 | One or more required parameters are not specified or their formats are invalid. |
10302 | The time parameter is invalid. |
10303 | No data source is configured. |
10304 | The quota for this table exceeds the upper limit. |
10305 | An Object Storage Service (OSS) parameter is invalid. |
10306 | The name of the OSS bucket is invalid. |
10307 | The OSS record type is invalid. |
10308 | The logging feature of the OSS bucket is disabled. |
10309 | Specific tasks are in process. |
10310 | The application is not running. Tasks cannot be created. |
10311 | The time range is invalid. |
10312 | The application description exceeds the upper limit in length. The application description can be up to 600 characters in length. |
10313 | The OSS content format is invalid. |
10314 | Failed to access the access control list (ACL) in the region in which the OSS bucket resides. |
10315 | The endpoint of the OSS bucket is invalid. |
10330 | Data source parameters are invalid. |
10350 | Failed to connect to the MaxCompute data source. |
10351 | An error occurs in the MaxCompute data source. |
10400 | The prefix of the OSS bucket name is invalid. |
10450 | The field does not exist. |