In this version, we've made many usability improvements. Many of them small, but together they should make a noticeable overall impact on your experience. We've also added a new input for data stored in Microsoft's Azure Storage.
- Microsoft Azure Input - If your data is stored in files on Microsoft Azure Blob Storage, or Microsoft Application Insights, you can now import it to Redshift in minutes.
- Granular MySQL Input - You can now select which tables to replicate and spend your throughput where you want it.
- Custom Email Digest List - We introduced Email Notifications in our last version, to let you know how your system is doing right in your inbox. As always, we try to bring new features to our users as fast as we can, and then adjust and update as we progress. In this version, you can customize the list of emails to which Alooma will send notifications (previously, the system sent notifications only to registered users).
- Sandboxed Python Transform - We made our Python engine a bit more durable, so even if you make mistakes, your system will stay protected. We invite you to try and hack it - we promise eternal respect to anyone who succeeds.
- We've made a few small improvements to the Mapper:
- Drop a table directly from the Mapper - If you’ve found yourself adding an input, creating a table, mapping the events to it, and then realizing that you made a some mistake and you need to restart, this update is for you. We've added a tiny feature that will save you some time on the cleanup - 'drop table' straight from the Mapper. You will find this option in the Table selection dropdown - just hover over a table name and click “Drop”.
- Now you can map fields to VARCHAR columns of any length, and not just rely on the default 256 characters. You should keep in mind that Amazon recommends not to include VARCHAR columns on redshift at all (as it is an analytical data store). If you do, keep your VARCHAR columns limited to 40 characters. But we understand its your data, and you should store it however you want, so we let you set any limit on your VARCHAR columns (up to the 65535 character Redshift maximum).
- More flexible filtering options for your fields - See mapped or unmapped fields, and discarded or invalid mappings, or any combination of them. Find the fields you care about quickly and efficiently.
- We’ve added a new warning issued when Redshift isn't configured properly - a small yet long needed one. We hope it will help our users understand their Redshift is misconfigured - either not configured at all, missing table modification permissions, or any other issue. Whatever it is that's preventing Alooma from loading your data - we try to let you know about it clearly and promptly.
- Added a tooltip which explains the acceptable table names in the Create Table menu of the Mapper screen.
- Changed the way S3 retention checks for bucket permissions.
- Ensured the Strict/Flexible Mapping Mode configuration is maintained between updates
- The selection of Sort Columns no longer disappears if the table creation operation failed.
- The auto-map button is now only there when there are fields to map.
- We fixed the notification for a failure in altering a table.
- No more embarrassing texts & typos!