Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TDengine-server-3.3.2.0-Linux-x64
[root@ecs-cd21 ~]# taosdump --version; taosdump version: 3.3.2.0 git: 6d748239c188db3d2293ae31196ed7ed76a40f38 build: Linux-x64 2024-06-28 10:22:45 +0800
taosdump -D banhusha -o /opt ============================== ========== arguments config ========= taosdump version: 3.3.2.0 git: 6d748239c188db3d2293ae31196ed7ed76a40f38 build: Linux-x64 2024-06-28 10:22:45 +0800 host: (null) user: root port: 0 outpath: /opt/ inpath: resultFile: ./dump_result.txt all_databases: false databases: true databasesSeq: banhusha schemaonly: false with_property: true avro codec: snappy data_batch: 16383 thread_num: 8 allow_sys: false escape_char: true loose_mode: false isDumpIn: false arg_list_len: 0 build: Linux-x64 2024-06-28 10:22:45 +0800 start time: 2024-07-09 17:17:54 OK: Database: banhusha exists INFO: Getting table(s) count of db (banhusha) ... INFO: Start to dump out database: banhusha INFO: start dump out super table data (history_data_jt_mc_ag1004g) ... INFO: start dump super table meta (history_data_jt_mc_ag1004g) col:5 tags:2 ... INFO: Get super table (history_data_jt_mc_ag1004g) child tables (2) ok INFO: The number of tables of history_data_jt_mc_ag1004g is 2! INFO: connection: 0x4487460 is dumping out schema of sub-table(s) of history_data_jt_mc_ag1004g INFO: connection 0x4487460 is dumping out schema: 1 from history_data_jt_mc_ag1004g.t_history_jt_mc_ag1004g_860411047253933 INFO: connection 0x4487460 is dumping out schema: 2 from history_data_jt_mc_ag1004g.t_history_jt_mc_ag1004g_860411047674773 OK: total 2 table(s) of stable: history_data_jt_mc_ag1004g schema dumped. INFO: create 2 thread(s) to export data ... WARN: generateSubDirName() LN8358, /opt/taosdump.3441033348664/data0 exists. .INFO: banhusha.history_data_jt_mc_ag1004g [1/2] write avro 100% of t_history_jt_mc_ag1004g_860411047253933 .INFO: banhusha.history_data_jt_mc_ag1004g [2/2] write avro 100% of t_history_jt_mc_ag1004g_860411047674773 INFO: super table (history_data_jt_mc_ag1004g) dump 2 child data ok. close taos connections... ERROR: typeStrToType() LN756 Unknown type: VARBINARY ERROR: typeStrToType() LN756 Unknown type: VARBINARY ERROR: typeStrToType() LN756 Unknown type: VARBINARY INFO: start dump out super table data (alarm_data) ... ERROR: typeStrToType() LN756 Unknown type: VARBINARY ERROR: typeStrToType() LN756 Unknown type: VARBINARY ERROR: typeStrToType() LN756 Unknown type: VARBINARY INFO: start dump super table meta (alarm_data) col:24 tags:2 ... INFO: Get super table (alarm_data) child tables (3) ok INFO: The number of tables of alarm_data is 3! ERROR: convertTbDesToJsonImplMore() LN4060, wrong type: 0 ERROR: convertTbDesToJsonImplMore() LN4060, wrong type: 0 ERROR: prepareAvroWface() LN3440, Unable to parse: {"type":"record","name":"banhusha._stb","fields":[{"name":"stbname","type":["null","string"]},{"name":"tbname","type":["null","string"]},},}]} to schema error message: Error parsing JSON: unexpected token near '}'
The text was updated successfully, but these errors were encountered:
TDengine-server-3.3.2.0-Linux-x64
[root@ecs-cd21 ~]# taosdump --version;
taosdump version: 3.3.2.0
git: 6d748239c188db3d2293ae31196ed7ed76a40f38
build: Linux-x64 2024-06-28 10:22:45 +0800
The text was updated successfully, but these errors were encountered: