-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Blob / binary columns #94
Comments
ok, I'll look into the crash. would you want the blob output as base64? That's sort of the best thing I can think of to do with it.... |
base64 makes the most sense to me |
#97 that was easier than I thought it would be |
Great #97 fixes the crash and I can see the base64'd data coming through maxwell. However, I notice the base64 encoded string is not padded and is a 'URL safe' version. Was this intentional? I think a padded base64 with standard encoding would be best for interoperability, unless there is a reason for choosing a URL safe version? |
I wanted to avoid the line chunking that happens in apache commons 1.4. I'll use a different method, one sec. |
updated apache commons to 1.5 for non-chunked base64, now it's padded. |
Awesome 👍, decoding's a lot more straightforward now (Python) |
cool, I will release this and others once I can get sign-off from a Zendesk folk (dumb coding standards) :) |
I realise from the docs that binary column support is experimental. I'd like to use maxwell with an existing database which has some blob columns but maxwell crashes whenever a row with a
blob
column is modified.MySQL 5.1.59
Maxwell 0.11.0-RC1
Steps to reproduce:
Maxwell log
The text was updated successfully, but these errors were encountered: