Connector Improvement: Improved logging to identify table causing sync error. The logs need to include the table name to reduce debugging time and recovery of the replication job.
Answered
When I got the following error which ended the sync job how do I tell which table or previous log step caused the error ?
Currently I go back and look at the previous 5-10 log steps and make sure they have a completed future log entry but why not add the table name to the error message below ?
{
"event" : "status",
"data" : {
"status" : "FAILURE_WITH_TASK",
"reason" : "java.sql.SQLSyntaxErrorException: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.",
"taskType" : "row_size_too_big"
},
"created" : "2022-03-05T00:24:59.270Z",
"connector_type" : "netsuite_suiteanalytics",
"connector_id" : "folly_song",
"connector_name" : "netsuiteprod",
"sync_id" : "025c26ba-d854-49df-9d92-eb5df3913b94"
}
-
Official comment
Hi Mike -
Thanks for submitting this feature request. We will look into adding more clear, and accurate logs for the Netsuite connector so you can better troubleshoot errors.
I will discuss this with engineering to understand the level of difficulty.
Best,Erin
Please sign in to leave a comment.
Comments
1 comment