-
Notifications
You must be signed in to change notification settings - Fork 196
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
Fix/2089 support sets for pyarrow backend #2090
Fix/2089 support sets for pyarrow backend #2090
Conversation
master merge for 1.0.0 release
Merge broken docs fix to master
master merge for 1.1.0 release
master merge for 1.2.0 release
master merge for 1.3.0 release
master merge for 1.4.0 release
✅ Deploy Preview for dlt-hub-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
a9930a1
to
816b7d3
Compare
@karakanb LGTM! do you have any tests for that in your code base? does it solve your problem? we do not have MySQL test setup for the sql source (only for the destination). |
I only have integration tests in ingestr, unfortunately no unit tests that might cover this. I have manually tested this and it solved the problem. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! thanks for the fix
Description
This PR fixes the issue with mysql set fields on pyarrow backend.
Related Issues
Open Questions
There's also a similar issue with using sqlalchemy backend, it requires a custom type adapter callback function to be useful. should it be handled properly inside dlt by default? I couldn't find a common sqltype to represent dicts, happy to fix it if you have any recommendations on how to fix it.