tom_elliff
10/07/2020, 5:03 PMpipelinewise-tap-postgresql
but when I send it to my target (in my case target-jsonl
) I get errors when handling numeric
columns because the defined schema for the column looks like:
"duration": {
"type": [
"null",
"number"
],
"exclusiveMaximum": true,
"maximum": 100000000000000000000000000000000000000000000000000000000000000,
"multipleOf": 1e-38,
"exclusiveMinimum": true,
"minimum": -100000000000000000000000000000000000000000000000000000000000000
},
which then causes the json schema validation to throw a precision error in Python's decimal class when it tries to divide the column by 1E-38. Has anyone else encountered this? If so how did they handle it?