DataArts Migration Error Codes
If an exception occurs during the execution of an operation request and the request is not processed, an error message is returned. The error information contains the error code and error description. Table 1 lists some common error code in CDM error messages. You can handle the exceptions by referring to the solutions in Table 1.
Error Code Description
|
Error Code |
Error Message |
Solution |
|---|---|---|
|
Cdm.0000 |
System error. |
Contact customer service or technical support. |
|
Cdm.0003 |
Kerberos login failed. |
Check whether the keytab and principal configuration files are correct. |
|
Cdm.0009 |
%s is not an integer or is beyond the value range [0, 2147483647]. |
Modify the parameter settings based on the error message and try again. |
|
Cdm.0010 |
The integer must be within the range of [%s]. |
Check whether the parameter value is valid based on the error message. If it is not, correct it and try again. |
|
Cdm.0011 |
The parameter value exceeds the value range. |
Check whether the parameter value is valid based on the error message. If it is not, correct it and try again. |
|
Cdm.0012 |
JDBC driver class is not found. |
Contact customer service or technical support. |
|
Cdm.0013 |
Failed to connect to the agent. |
It is possible that the network is disconnected, or no security group or firewall rule is configured to allow access. If the fault persists, contact customer service or technical support. |
|
Cdm.0014 |
The parameter is invalid. |
Change the parameter value and try again. |
|
Cdm.0015 |
An error occurred during file parse. |
Check whether the content or format of the uploaded file is correct. If it is not, correct it and try again. |
|
Cdm.0016 |
The file to be uploaded cannot be empty. |
Ensure that the file you uploaded is not empty and try again. |
|
Cdm.0017 |
MRS Kerberos authentication failed. |
Check whether the password used for Kerberos authentication is strong. If it is not, change to a strong password and try again. |
|
Cdm.0018 |
The content of jobs or links is invalid. |
Contact customer service or technical support. |
|
Cdm.0019 |
Invalid IP address and port number. |
Try again later or contact customer service or technical support. |
|
Cdm.0020 |
The string must contain the following substring: %s. |
Modify the parameter settings based on the error message and try again. |
|
Cdm.0021 |
Failed to connect to the server: %s. |
Contact customer service or technical support. |
|
Cdm.0023 |
Failed to write data. Cause: %s. |
Contact customer service or technical support. |
|
Cdm.0024 |
[%s] must be within the range of [%s]. |
Modify the parameter settings based on the error message and try again. |
|
Cdm.0025 |
The length of the written data exceeds the length defined by the table field. Error message: %s. |
Modify the length of the data to be written based on the error message and try again. |
|
Cdm.0026 |
The primary key already exists. Error message: %s. |
Check the data based on the error message and resolve the primary key conflict. |
|
Cdm.0027 |
The code of the written character string may be different from the code defined in the table. Error message: %s. |
Modify the character string code based on the error message. |
|
Cdm.0028 |
Incorrect username or password. Error message: %s. |
Change the username or password and try again. |
|
Cdm.0029 |
The database name does not exist. Error message: %s. |
Select a correct database and try again. |
|
Cdm.0030 |
Incorrect username, password, or database name. Error message: %s. |
Correct the username, password, and database name as prompted and try again. |
|
Cdm.0031 |
The connection timed out. |
Connection timed out. Check whether the IP address, host name, and port number are correct, and whether the security group and firewall are correctly configured. |
|
Cdm.0032 |
Incorrect username or password. See the error message returned by the server: %s. |
Change the username and password based on the error message and try again. |
|
Cdm.0033 |
SIMPLE authentication is not supported. |
Select the Kerberos authentication type and try again. |
|
Cdm.0034 |
Restart the CDM cluster to reload MRS or FusionInsight configurations. |
Restart the CDM cluster to reload MRS or FusionInsight configurations. |
|
Cdm.0035 |
You do not have the write permission on the file. Error message: %s. |
Configure the permission based on the error message and try again. |
|
Cdm.0036 |
Invalid datestamp or date format. Error message: %s. |
Configure the datestamp or date format based on the error message and try again. |
|
Cdm.0037 |
The parameter is invalid. Error message: %s. |
Correct the parameter settings based on the error message and try again. |
|
Cdm.0038 |
The connection timed out. |
Check the VPC and security group rules. |
|
Cdm.0039 |
The connection name cannot be modified. |
The connection name cannot be changed. |
|
Cdm.0040 |
Logs are deleted because they are periodically cleared. |
Contact customer service or technical support. |
|
Cdm.0041 |
The group in use cannot be updated or deleted. |
Do not modify the group. |
|
Cdm.0042 |
Failed to operate the group. Error message: %s. |
Select a correct group based on the error message and try again. |
|
Cdm.0043 |
Failed to trigger data extraction or loading failed. Cause: %s. |
Contact customer service or technical support. |
|
Cdm.0051 |
Invalid submission engine: %s. |
Specify a correct job engine and try again. |
|
Cdm.0052 |
Job %s is running. |
The operation cannot be performed because the job is running. Try again after the job completes. |
|
Cdm.0053 |
Job %s is not running. |
Run the job and try again. |
|
Cdm.0054 |
Job %s does not exist. |
Check whether the job exists. |
|
Cdm.0055 |
Unsupported job type. |
Specify a correct job type and try again. |
|
Cdm.0056 |
Failed to submit the job. Cause: %s. |
Locate the cause based on the error message, rectify the fault, and try again. |
|
Cdm.0057 |
Invalid job execution engine: %s. |
Specify a correct job engine and try again. |
|
Cdm.0058 |
Invalid combination of submission and execution engines. |
Specify a correct job engine and try again. |
|
Cdm.0059 |
Job %s has been disabled. Failed to submit the job. |
Create a job and try again. Alternatively, contact customer service or technical support. |
|
Cdm.0060 |
Link %s for this job has been disabled. Failed to submit the job. |
Change the link and submit the job again. |
|
Cdm.0061 |
Connector %s does not support the specified direction. Failed to submit the job. |
The connector cannot be used as the source or destination of a job. Change the link and submit the job again. |
|
Cdm.0062 |
The binary file is applicable only to the SFTP, FTP, HDFS, or OBS connector. |
Specify a correct connector and try again. |
|
Cdm.0063 |
An error occurred during table creation. Cause: %s. |
Locate the cause based on the error message, rectify the fault, and try again. |
|
Cdm.0064 |
The data format is incorrect. |
Check whether the data format is correct based on the error message. If it is not, correct it and try again. |
|
Cdm.0065 |
Failed to start the scheduler. Cause: %s. |
Contact customer service or technical support. |
|
Cdm.0066 |
Failed to obtain the sample value. Cause: %s. |
Contact customer service or technical support. |
|
Cdm.0067 |
Failed to obtain the schema. Cause: %s. |
Contact customer service or technical support. |
|
Cdm.0068 |
Failed to clear table data. Cause: %s. |
|
|
Cdm.0070 |
Failed to run task %s because the maximum number of running jobs has been reached. |
Contact customer service or technical support. |
|
Cdm.0071 |
Failed to obtain table data. Cause: %s. |
Contact customer service or technical support. |
|
Cdm.0074 |
Failed to repair the table. Cause: %s. |
Contact customer service or technical support. |
|
Cdm.0075 |
Failed to delete the table. Cause: %s. |
|
|
Cdm.0080 |
Invalid username. |
Correct the username based on the error message and try again. |
|
Cdm.0081 |
Invalid certificate. |
Contact customer service or technical support. |
|
Cdm.0082 |
The certificate is not readable. |
Contact customer service or technical support. |
|
Cdm.0083 |
A process cannot be configured with multiple certificates. Restart to use the new certificate. |
Modify the certificate based on the error message and restart the system. |
|
Cdm.0085 |
The value exceeds the upper limit. |
Contact customer service or technical support. |
|
Cdm.0088 |
Incorrect XX configuration item. |
Modify the configuration item based on the error message and try again. |
|
Cdm.0089 |
The configuration item XX does not exist. |
|
|
Cdm.0091 |
The patches cannot be installed. |
Contact customer service or technical support. |
|
Cdm.0092 |
The backup file does not exist. |
Contact customer service or technical support. |
|
Cdm.0093 |
Failed to load the krb5.conf file. |
Contact customer service or technical support. |
|
Cdm.0094 |
The link named XX does not exist. |
Check whether the XX link exists based on the error message and try again. |
|
Cdm.0095 |
The job named XX does not exist. |
Check whether the XX job exists based on the error message and try again. |
|
Cdm.0100 |
Job [%s] does not exist. |
Specify a correct job and try again. |
|
Cdm.0101 |
Link [%s] does not exist. |
Specify a correct link and try again. |
|
Cdm.0102 |
Connector [%s] does not exist. |
Specify a correct connector and try again. |
|
Cdm.0104 |
The job name exists. |
Rename the job and try again. |
|
Cdm.0105 |
The expression is empty. |
|
|
Cdm.0106 |
Failed to calculate the XX expression. |
|
|
Cdm.0107 |
The task is being executed. Modify job configurations later. |
After the task is complete, modify the job configurations. |
|
Cdm.0108 |
Failed to query table records. |
|
|
Cdm.0109 |
The length of a job or link name cannot exceed %s. |
Modify the job or link name based on the error message. |
|
Cdm.0110 |
Invalid name. The name must start with a character or digit and consist of only letters, digits, underscores (_), hyphens (-), and dots (.). |
Change the name based on the error message. |
|
Cdm.0201 |
Failed to obtain the instance. |
Contact customer service or technical support. |
|
Cdm.0202 |
Unknown job status. |
Try again later or contact customer service or technical support. |
|
Cdm.0204 |
No MRS link is created. |
Go to the Link Management page to create an MRS link and try again. |
|
Cdm.0230 |
Failed to load the specified class: %s. |
Contact customer service or technical support. |
|
Cdm.0231 |
Failed to initialize the specified class: %s. |
Contact customer service or technical support. |
|
Cdm.0232 |
Failed to write data. Cause: %s. |
Contact customer service or technical support. |
|
Cdm.0233 |
An exception occurred during data extraction. Cause: %s. |
Contact customer service or technical support. |
|
Cdm.0234 |
An exception occurred during data loading. Cause: %s. |
Contact customer service or technical support. |
|
Cdm.0235 |
All data has been consumed. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact customer service or technical support. |
|
Cdm.0236 |
Invalid partitions have been retrieved from Partitioner. |
Locate the cause based on the error message. If the fault persists, contact customer service or technical support. |
|
Cdm.0237 |
Failed to find the JAR file of the connector. |
Contact customer service or technical support. |
|
Cdm.0238 |
%s cannot be empty. |
Modify the parameter settings based on the error message and try again. |
|
Cdm.0239 |
Failed to obtain HDFS. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact customer service or technical support. |
|
Cdm.0240 |
Failed to obtain the status of the %s file. |
Contact customer service or technical support. |
|
Cdm.0241 |
Failed to obtain the type of the %s file. |
Contact customer service or technical support. |
|
Cdm.0242 |
An exception occurred during file check: %s. |
Contact customer service or technical support. |
|
Cdm.0243 |
Failed to rename %s to %s. |
Rename the job and try again. |
|
Cdm.0244 |
Failed to create the %s file. |
Check whether you have the permissions or try again later. If the fault persists, contact customer service or technical support. |
|
Cdm.0245 |
Failed to delete the %s file. |
Check whether you have the permissions or try again later. If the fault persists, contact customer service or technical support. |
|
Cdm.0246 |
Failed to create the %s directory. |
Check whether you have the permissions or try again later. If the fault persists, contact customer service or technical support. |
|
Cdm.0247 |
HBase operation failure. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact customer service or technical support. |
|
Cdm.0248 |
Failed to clear data in %s. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.0249 |
The file name %s is invalid. |
Modify the file name and try again. |
|
Cdm.0250 |
Failed to perform operations in the path: %s. |
Check whether you have the permissions or try again later. If the fault persists, contact . |
|
Cdm.0251 |
Failed to load data to HBase. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.0307 |
Failed to release the link. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.0315 |
The link name %s already exists. |
Specify another link name and try again. |
|
Cdm.0316 |
The link that does not exist cannot be updated. |
Specify a correct link and try again. |
|
Cdm.0317 |
Link %s is invalid. |
Specify a correct link and try again. |
|
Cdm.0318 |
The job exists and cannot be created repeatedly. |
Specify another job name and try again. |
|
Cdm.0319 |
The job that does not exist cannot be updated. |
Check whether the job to be updated exists. If it does, modify the job name and try again. |
|
Cdm.0320 |
Job %s is invalid. |
Contact . |
|
Cdm.0321 |
Link %s has been used. |
Release the link and try again. |
|
Cdm.0322 |
Job %s has been used. |
Contact . |
|
Cdm.0323 |
The submission already exists and cannot be created repeatedly. |
Try again later. |
|
Cdm.0327 |
Invalid link or job: %s. |
Specify a correct link or job and try again. |
|
Cdm.0411 |
An error occurred when connecting to the file server. |
Contact . |
|
Cdm.0412 |
An error occurred when disconnecting from the file server. |
Contact . |
|
Cdm.0413 |
An error occurred in data transfer to the file server. |
Contact . |
|
Cdm.0415 |
An error occurred when downloading files from the file server. |
Contact . |
|
Cdm.0416 |
An error occurred during data extraction. |
Contact . |
|
Cdm.0420 |
The source file or source directory does not exist. |
Check whether the source file or source directory exists. If it does not, specify a correct source file or directory and try again. |
|
Cdm.0423 |
Duplicate files exist in the destination path. |
Delete duplicate files from the destination path and try again. |
|
Cdm.0500 |
The source directory or the [%s] file does not exist. |
Specify a correct source file or directory and try again. |
|
Cdm.0501 |
Invalid URI [%s]. |
Specify a correct URI and try again. |
|
Cdm.0518 |
Failed to connect to HDFS. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.0523 |
Connection timed out due to insufficient user permissions. |
Create another service user, grant required permissions to the user, and try again. |
|
Cdm.0600 |
Failed to connect to the FTP server. Cause: %s. |
It is possible that the network is disconnected, no security group or firewall rule is configured to allow access, the FTP host name cannot be parsed, or the FTP username or password is incorrect. If the fault persists, contact . |
|
Cdm.0700 |
Failed to connect to the SFTP server. Cause: %s. |
It is possible that the network is disconnected, no security group or firewall rule is configured to allow access, the SFTP host name cannot be parsed, or the SFTP username or password is incorrect. If the fault persists, contact . |
|
Cdm.0800 |
Failed to connect to the OBS server. Cause: %s. |
It is possible that the OBS endpoint is inconsistent with the current region, the AK/SK pair is incorrect, the AK/SK pair is not the current user's, or no security group or firewall rule is configured to allow access. If the fault persists, contact . |
|
Cdm.0801 |
OBS bucket [%s] does not exist. |
The OBS bucket may not exist or is not in the current region. Specify a correct OBS bucket and try again. |
|
Cdm.0900 |
Table [%s] does not exist. |
Specify a correct table name and try again. |
|
Cdm.0901 |
Failed to connect to the database server. Cause: %s. |
Contact . |
|
Cdm.0902 |
Failed to execute the SQL statement. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.0903 |
Failed to obtain metadata. Cause: %s. |
Check whether the quote character is correct or whether the database table exists when you create the link. If the fault persists, contact . |
|
Cdm.0904 |
An error occurred while retrieving data from the result. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.0905 |
No partition column is found. |
Specify a partition column and try again. |
|
Cdm.0906 |
No boundary is found in the partition column. |
Contact . |
|
Cdm.0911 |
The table name or SQL must be specified. |
Specify a table name or SQL statement and try again. |
|
Cdm.0912 |
The table name and SQL cannot be specified at the same time. |
Specify one of them and try again. |
|
Cdm.0913 |
Schema and SQL cannot be specified at the same time. |
Specify one of them and try again. |
|
Cdm.0914 |
Partition column is mandatory for query-based import. |
Specify a partition column and try again. |
|
Cdm.0915 |
The SQL-based import mode and columnList cannot be used at the same time. |
Use either of them and try again. |
|
Cdm.0916 |
Last value is mandatory for incremental read. |
Specify the last value and try again. |
|
Cdm.0917 |
Last value cannot be obtained without field check. |
Contact . |
|
Cdm.0918 |
If no transfer table is specified, shouldClearStageTable cannot be specified. |
Specify a transfer table and try again. |
|
Cdm.0921 |
Type %s is not supported. |
Specify a correct type and try again. |
|
Cdm.0925 |
The partition column contains unsupported values. |
Correct the values and try again. |
|
Cdm.0926 |
Failed to obtain the schema. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.0927 |
The transfer table is not empty. |
Specify an empty transfer table and try again. |
|
Cdm.0928 |
An error occurred when data is migrated from the transfer table to the destination table. |
Contact . |
|
Cdm.0931 |
Schema column size [%s] does not match the result set column size [%s]. |
Change the schema column size to be the same as the result set column size and try again. |
|
Cdm.0932 |
Failed to obtain the maximum value of the field. |
Contact . |
|
Cdm.0934 |
Multiple tables of the same name exist in different schemas or catalogs. |
Contact . |
|
Cdm.0935 |
No primary key. Specify the partition column. |
Specify a partition column and try again. |
|
Cdm.0936 |
The maximum number of error dirty data records has been reached. |
Edit the job and increase the number of error dirty data records. |
|
Cdm.0940 |
Failed to match the exact table name. |
Specify a correct table name and try again. |
|
Cdm.0941 |
Failed to connect to the server. Cause: %s. |
Check whether the IP address, host name, and port number are correct, and whether the network security group and firewall are correctly configured. Locate the fault based on the error message. If the fault persists, contact . |
|
Cdm.0950 |
Failed to connect to the database with the existing authentication information. |
Incorrect authentication information. Correct it and try again. |
|
Cdm.0960 |
Server address must be specified. |
Specify the server address and try again. |
|
Cdm.0961 |
Invalid server address format. |
Change to the correct format and try again. |
|
Cdm.0962 |
The host IP address must be specified. |
Specify the host IP address and try again. |
|
Cdm.0963 |
The host port must be specified. |
Specify the host port and try again. |
|
Cdm.0964 |
The database must be specified. |
Specify a database and try again. |
|
Cdm.1000 |
Hive table [%s] does not exist. |
Specify a correct Hive table name and try again. |
|
Cdm.1010 |
Invalid URI [%s]. The URI must be either null or a valid URI. |
Specify a correct URI and try again. Correct URI examples:
|
|
Cdm.1011 |
Failed to connect to Hive. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1012 |
Failed to initialize the Hive client. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1100 |
Table [%s] does not exist. |
Enter a correct table name and try again. |
|
Cdm.1101 |
Failed to obtain the link. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1102 |
Failed to create the table. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1103 |
No rowkey is set. |
Set the rowkey and try again. |
|
Cdm.1104 |
Failed to open the table. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1105 |
Failed to initialize the job. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1111 |
The table name is mandatory. |
Specify a correct table name and try again. |
|
Cdm.1112 |
The import mode is mandatory. |
Set the import mode and try again. |
|
Cdm.1113 |
Whether to clear data before import has not been specified. |
Set Clear Data Before Import and try again. |
|
Cdm.1114 |
The rowkey is empty. Set it in field mapping. |
Fix the error based on the error message. |
|
Cdm.1115 |
Columns is empty. Set it in field mapping. |
Fix the error based on the error message. |
|
Cdm.1116 |
Duplicate column names. Set it in field mapping. |
Fix the error based on the error message. |
|
Cdm.1117 |
An error occurred when checking whether the table exists. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1118 |
Table %s does not contain the %s column family. |
Specify a column family and try again. |
|
Cdm.1119 |
The number of column families is %s and the number of columns is %s. |
Change the number of column families to the same as the number of columns and try again. |
|
Cdm.1120 |
The table contains data. Clear the table data or set the configuration item to specify whether to clear the table data before the import. |
Fix the error based on the error message. |
|
Cdm.1121 |
Failed to close the link. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1201 |
Failed to connect to the Redis server. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1202 |
Failed to connect to the Redis cluster in single-node mode. |
Connect to the Redis cluster in another mode. |
|
Cdm.1203 |
Failed to extract data from the Redis server. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1205 |
Redis Key Prefix cannot be blank. |
Delete the whitespace before the Redis prefix and try again. |
|
Cdm.1206 |
The storage type of the Redis value must be STRING or HASH. |
Fix the error based on the error message. |
|
Cdm.1207 |
When the value of the storage type is STRING, Value Delimiter must be specified. |
Specify a value delimiter and try again. |
|
Cdm.1208 |
columnList of Redis must be specified. |
Specify columnList and try again. |
|
Cdm.1209 |
Redis Key Delimiter cannot be empty. |
Enter a correct delimiter and try again. |
|
Cdm.1210 |
primaryKeyList of Redis must be specified. |
Specify primaryKeyList and try again. |
|
Cdm.1211 |
primaryKeyList of Redis must exist in columnList. |
Specify primaryKeyList and try again. |
|
Cdm.1212 |
databaseType of Redis must be Original or DCS. |
Fix the error based on the error message. |
|
Cdm.1213 |
Redis Server Address must be specified. |
Specify Redis Server Address and try again. |
|
Cdm.1301 |
Failed to connect to the MongoDB server. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1302 |
Failed to extract data from the MongoDB server. Cause: %s |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1304 |
The collection of MongoDB servers must be specified. |
Specify the collection of MongoDB servers and try again. |
|
Cdm.1305 |
Server Address of MongoDB must be specified. |
Specify Server Address and try again. |
|
Cdm.1306 |
The database name of the MongoDB service must be specified. |
Specify a database and try again. |
|
Cdm.1307 |
serverlist of MongoDB must be specified. |
Specify serverlist and try again. |
|
Cdm.1400 |
Failed to connect to the NAS server. |
Contact . |
|
Cdm.1401 |
No permissions to access the NAS server. |
Apply for the permissions and try again. |
|
Cdm.1501 |
Failed to connect to the Elasticsearch server. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1502 |
Failed to write data to the Elasticsearch server. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1503 |
Failed to close the Elasticsearch link. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1504 |
An error occurred when obtaining the Elasticsearch index. Cause: %s |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1505 |
An error occurred when obtaining the Elasticsearch type. Cause: %s |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1506 |
An error occurred when obtaining the Elasticsearch field. Cause: %s |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1507 |
An error occurred when obtaining the Elasticsearch sample data. Cause: %s |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1508 |
The host name or IP address of the Elasticsearch server must be specified. |
Specify the host name or IP address and try again. |
|
Cdm.1509 |
The port of the Elasticsearch server must be specified. |
Specify a port and try again. |
|
Cdm.1510 |
The Elasticsearch index must be specified. |
Specify an index and try again. |
|
Cdm.1511 |
The Elasticsearch type must be specified. |
Specify a type and try again. |
|
Cdm.1512 |
columnList of Elasticsearch must be specified. |
Specify columnList and try again. |
|
Cdm.1513 |
columnList must contain the field type definition. |
Include the field type definition and try again. |
|
Cdm.1514 |
columnList must contain primaryKey. |
Set the primary key field and try again. |
|
Cdm.1515 |
An error occurred when resolving the JSON character string. Cause: %s. |
Locate the cause based on the error message, rectify the fault, and try again. If the fault persists, contact . |
|
Cdm.1516 |
The column name %s is invalid. |
Enter a correct column name and try again. |
|
Cdm.1517 |
An error occurred when obtaining the number of documents. |
Contact . |
|
Cdm.1518 |
The partition fails to be created. |
Contact . |
|
Cdm.1519 |
An error occurred during data extraction. |
Contact . |
|
Cdm.1520 |
Failed to obtain the type. Cause: %s. |
Locate the cause based on the error message. If the fault persists, contact . |
|
Cdm.1601 |
Failed to connect to the server. |
Contact . |
|
Cdm.1603 |
Failed to obtain the sample value of the %s topic. |
Contact . |
|
Cdm.1604 |
No data exists in topic %s. |
Locate the cause. Alternatively, change the topic and try again. |
|
Cdm.1605 |
Invalid brokerList. |
Specify a correct brokerList and try again. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
