Warning type: "json_value_too_long"
Not plannedFivetran logs do not specify which exact schema/table/record is receiving this warning, when its type: "json_value_too_long".
With the table, at least, this warning could be useful to track the issue.
-
Official comment
Hi Rodrigo,
Thanks for submitting this request. I agree the lack of detail here makes the error less useful. When this is encountered, the value inserted into the destination will beFIVETRAN ERROR": "Original value could not be synced because it exceeded your warehouse's maximum length”
At present, we don't have plans to enhance this error reporting to point to the record in question. We understand it can be a little worrying when seeing this error and not knowing where the effect is, and if we see that the downstream problems are significant and best detectable via an improved error, we'll certainly take give this request another look.
Until then, all viewers interested, please upvote if you're interested in the same improvement!
All the best,Ray Harris
Product Manager, Sales & Customer Success Analytics
Please sign in to leave a comment.
Comments
1 comment