Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'evidence' column in 'disputes' object is a stringified field, not valid JSON #119

Open
ilkkapeltola opened this issue Feb 16, 2022 · 3 comments

Comments

@ilkkapeltola
Copy link

My ETL fails because at least 'evidence' is not valid JSON, but stringified.

Changing the catalog entry for evidence from

"evidence": { "type": [ "null", "string", "object" ],

to

"evidence": { "type": [ "null", "object" ],

worked for me

@ilkkapeltola
Copy link
Author

Actually, I see this was changed in 2019 for some reason.
transferwise/pipelinewise-target-snowflake#244

I think it was a mistake to put "string" first before "object".
Reversing those would also work for me.

@ilkkapeltola
Copy link
Author

I got my hands on another stripe source that I ran into this very same issue.
Doing this worked:
"evidence": { "type": [ "null", "object", "string" ],

evidence is not a string.

@sebasgarcep
Copy link

I also experienced the same issue and @ilkkapeltola's solution worked for me. I can tackle this bug if the maintainers give me some pointers on where to start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants