ccr任务job_progress接口-子任务的binlog_type字段都有哪些枚举值

Viewed 6

ccr版本3.06-rc05
doris版本3.0.3
{
"success": true,
"job_progress": {
"job_name": "ccr_test2",
"sync_state": 501,
"sub_sync_state": {
"state": 201,
"binlog_type": -1
},
"job_sync_id": 1784612266,
"prev_commit_seq": 11628,
"commit_seq": 11628,
"last_commit_seq": 0,
"unknown_commit_seq": 0,
"data": "",
"prev_txn_id": -1,
"created_at": 1784612265,
"full_sync_start_at": 1784612265,
"incremental_sync_start_at": 1784612307,
"full_sync_info": {
"prev_commit_seq": 0,
"commit_seq": 0,
"sub_sync_state": {
"state": 0,
"binlog_type": -1
},
"info": "new job, job: ccr_test2, sync type: table_sync"
}
}
}这个是job_progress返回的json,"full_sync_info的binlog_type": -1代表什么,其他值有什么,又代表什么
或者说做异常恢复的时候怎么判断是卡在建表DDL语句处了,根据binlog_type可以判断吗?

0 Answers