- MemSQL Output Beta - Make room, Redshift, we now support output to MemSQL (still in beta)! Our vision has always been to let you do anything with your data, and we're excited to make a first step towards opening up our outputs horizons. Redshift has been our bread and butter since the beginning, and MemSQL is the first of a few other outputs we have in our sleeve.
- Since this output is still in Beta, we'll have to turn it on for you by request. Reach out to firstname.lastname@example.org if you have MemSQL and want your data flowing there!
- SSH Support for Inputs and Outputs - Secure connectivity is the name of the game, and that's why we've added SSH support not only to our inputs (namely MySQL, PostgreSQL, and MongoDB), but also to outputs.
- When defining any connection, you can simply check the "Connect via SSH" checkbox and you'll have the opportunity to define the SSH server connection info.
- We suggest using our public key to connect, but feel free to use your own password if you prefer.
- Improved Python SDK - We've updated our Python SDK to reflect the latest and greatest capabilities, including token support. To use it, just
pip install alooma_pysdkand go! Check out our documentation or the GitHub repo itself and let us know what you think.
- Our fresh new auto-mapper was stopping if it hit any fields it couldn't map. Now we've improved it to continue on to the rest of the event fields, and report back on whichever fields were an issue. This information will be found in your notifications - and if you haven't started using our auto-mapper - what are you waiting for?! Email us at email@example.com if you have any questions about it.
- We added a "seconds" indicator in our input throughput graphs (shown when you click on any input node), so now it's clear in which part of the minute the data arrived.
- We removed the unnecessary "logfile" and "logpos" from our MySQL integration screen to make connecting to MySQL even simpler. If you need to pass those parameters because, for instance, you'd like to start or rerun your replication from a specific point in the log, they can still be accessed through the backend, so just let us know.
- Searching just got a little easier - our search box on the Mapper used to only search field names, but we extended it to be able to search over entered target output column names as well.
- Do you prefer that empty fields be loaded as NULL into your Redshift instead of as an empty value? If so, just give us a shout at firstname.lastname@example.org and we'll turn on that brand-spankin-new option in our backend for you.
- Our auto-mapper was failing on blob fields coming out of MySQL. "Blob" may sound funny, but it shouldn't cause an error, so we went ahead and fixed that.
- Our auto-mapper was also mapping according to statistics instead of schema data in the event that the database in question was not available. We want to make sure to always use the schema, so we remedied that.
- We fixed an issue where notifications were sometimes showing a length of "0" in the errors for fields that were longer than their varchar length.