datax启动任务报错
- Dominant language
- Java
- Stars
- 17.4k
- Forks
- 5.7k
- PR merge metrics
- No merged PRs in 30d
Description
各位小伙伴帮忙分析一下原因?
$ python datax.py ../job/job.json
DataX (DATAX-OPENSOURCE-3.0), From Alibaba !
Copyright (C) 2010-2017, Alibaba Group. All Rights Reserved.
2018-12-17 17:55:51.636 [main] WARN ConfigParser - 插件[null,null]加载失败,1s后重试... Exception:Code:[Framework-12], Description:[DataX插件初始化错误, 该问题通常是由于DataX安装错误引起,请联系您的运维解决 .]. - 插件加载失败,未完成指定插件加载:[null]
2018-12-17 17:55:52.718 [main] ERROR Engine -
经DataX智能分析,该任务最可能的错误原因是:
com.alibaba.datax.common.exception.DataXException: Code:[Framework-12], Description:[DataX插件初始化错误, 该问题通常是由于DataX安装错误引起,请联系您的运维解决 .]. - 插件加载失败,未完成指定插件加载:[null]
at com.alibaba.datax.common.exception.DataXException.asDataXException(DataXException.java:26)
at com.alibaba.datax.core.util.ConfigParser.parsePluginConfig(ConfigParser.java:142)
at com.alibaba.datax.core.util.ConfigParser.parse(ConfigParser.java:63)
at com.alibaba.datax.core.Engine.entry(Engine.java:137)
at com.alibaba.datax.core.Engine.main(Engine.java:204)
**job任务:**
{
"job": {
"content": {
"reader": {
"name": "ftpreader",
"parameter": {
"column": [
"*"
],
"compress": "zip",
"encoding": "utf-8",
"fieldDelimiter": ", ",
"host": "172.21.2.160",
"maxTraversalLevel": 100,
"nullFormat": "\\N",
"password": "etl",
"path": [
"/etl/liufl/protal_jwt/cpusta.log"
],
"port": 21,
"protocol": "ftp",
"skipHeader": "N",
"sliceRecordCount": 1000,
"username": "etl"
}
},
"writer": {
"name": "streamwriter",
"parameter": {
"visible": false,
"encoding": "UTF-8"
}
}
},
"setting": {
"errorLimit": {
"percentage": 0.01,
"record": 0
},
"speed": {
"byte": 2000,
"channel": 10,
"record": 1024
}
}
}
}
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported command, datax.py, and the job/job.json configuration. Read ConfigParser.java, especially parsePluginConfig, along with the Engine.java entry points and the ftpreader and streamwriter plugin names. Reproduce the plugin-loading failure and identify a documented, testable cause before proposing a fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100