Troubleshoot and resolve resource data loading errors that occur in data transformation rules for RDS, OSS, and LogStore resources.
Error handling mechanism
For information about error handling mechanisms for resource loading errors, see res_log_logstore_pull, res_rds_mysql, and res_oss_file.
General troubleshooting
Problem: A resource loading error occurs when a resource function is used independently without a wrapping function.
-
Sample transformation rules
res_log_logstore_pull(endpoint="cn-shenzhen.log.aliyuncs.com",ak_id="xxx", ak_secret="xxx",project="etl-test-shenzhen", fields=["__source__"]),field="processid",output_fields=["xx"]res_rds_mysql(address="xx",username="xx",password="xx",database="xx")res_oss_file(endpoint='xx',ak_id="xx",ak_key="xx",bucket='xx', file='xx',format='xx',change_detect_interval=0)
-
Error log
aliyun.log.logexception.LogException: {"errorCode": "InvalidEtlConfig", "errorMessage": "ETL config doesn't pass security check, detail: invalid type detected: <class '_ast.Expr'>", "requestId": ""} -
Cause
The error log indicates an ETL syntax configuration error. This error occurs because the res_log_logstore_pull, res_rds_mysql, or res_oss_file function is used independently. Resource functions do not support standalone use.
-
Solution
Wrap the resource function inside the e_table_map function. For more information, see Resource functions.
Related topics
-
For errors that occur when you pull data from another Logstore, see LogStore data (dimension table) loading errors.
-
For errors that occur when you pull data from OSS, see OSS data loading errors.
-
For syntax errors that occur when you pull data from RDS, see RDS MySQL data loading syntax errors.