Closed drewipson closed 2 years ago
@drewipson Sent over data on which stream this was failing at it seems to be "folder_customfield"
@drewipson could you make a reproducable file here. Ideally it'd be 2 lines first line , SCHEMA etc etc with the schema for that stream second line an offending record, RECORD etc etc with the record data that's failing for you from clickup (any sensitive data scrambled of course)
Idea is we should be able to run
cat testdata | target-snowflake
and reproduce the error
I can't see how we'd be failing at this, I guess I could run a test with my test data and target-snowflake as well
Found it it's not in the custom field stream.
It's in folder_list (and folderless_list)
https://gitlab.com/meltano/sdk/-/issues/228#note_801273924 , validate on the SDK should be able to catch this I'd think.
Spent way more time than I wanted on this today, but I did find the next fix here. https://gitlab.com/meltano/sdk/-/issues/299 I put into the SDK.
Refs are not supported. I have no idea how this wouldn't have been caught it our testing, but I guess those fields weren't needed for anything we were using.
Fix is to resolve all of these references, and to put in a PR without using any Refs. I tried to find a script that would do this for us , and tested a few, but I haven't been so lucky yet.
Using Tap-Clickup with the target-snowflake pipelinewise variant loader throws a KeyError on load.
Traceback goes to the
adjust_timestamps_in_record
function in stream_utils.py in the target-snowflake library.Offending Record:
Traceback: