Keboola Status

We have released new versions of these database writers:

• MySQL
• Microsoft SQL Server
• Redshift
• Oracle

Also, we are introducing Cloudera Impala database writer.

All these writers are running on container based architecture with SSH tunnel support.

Here's what last week was about:

• Fixed bug in Redshift backend: Exporting a table with column of maximum allowed length (64KB) no longer causes an error.
• MariaDB, which is used as MySQL backend in transformations, was updated to version 5.5.53. This update enhances the handling of 4-byte UTF-8 characters. In previous version 5.5.44 a string was cut after the first utf8mb4 character. Now, all these characters will be converted to '?'. Full support of 4-byte UTF-8 characters is unfortunately unavailable in MySQL.
• Fixed bug in MySQL extractor: When query returned an empty result, extractor ended up with 'Orphaned manifest' error

During last 24 hours some MySQL transformation jobs failed with the following error message:

SQLSTATE[HY093]: Invalid parameter number: no parameters were bound

This was caused by an update in the application and it only affects transformations, that contain empty queries (eg. just ";" character). The fix will be deployed shortly and we'll restart all affected orchestrations. 

We're sorry for this inconvenience.

As always, here's the list of most important changes we made last week.

• Load to Redshift workspaces fetches information about Primary Key(s) from Storage API metadata
• Fixed issue when Primary Key couldn't be deleted after table optimization on Redshift storage backend
• Table aliases can now be loaded to Workspaces/Sandboxes and Transformations too

And we enabled Project Power feature to all users of Keboola Connection, so you can check Storage usage of your project.

Last week we saw a little more outages than expected, someone tried to scare us before Halloween! But we don't give up.

• New self-managed Currency Extractor with a hint of gap-filling script.
• Configuration description now supports markdown.
  

  

• OpenRefine transformation won't let you save invalid JSON.
• SQL editor shows a warning if your last query is a comment. Executing a comment will most likely fail the execution, so the warning is a temporary workaround before we're able to parse the SQL and strip the comments.
• MongoDB extractor now supports raw export mode.

Have you ever used Sailthru and are you interested in analysis of your campaign data? If you answer is positive in both cases, you might be happy for this new extension to the Keboola Connection family - Sailthru Campaign Extractor. 

As title says, the extractor is able to download your campaign data and datasets like beacon times, devices, domains, engagement, just to name a few (you can see the full list in the documentation).

The configuration of this extractor is very simple and a lot of things are happening 'under the hood'. The output datasets are aggregated and some of them contain some additional information, just for your convenient to potentially simplify your analytics queries in Keboola Connection (at least a little bit). During the development there was a big focus on extensibility and for that reason there is a high probability there will be a new set of cool features in the future. 

The development was sponsored by Pond5 and developed independently by Radek Tomášek. I would love to thank Petr Havlik for his tremendous support during the whole development process. His experience made the whole development easier. For more information on how to use the extractor, please refer to the documentation.

It is my pleasure to announce a new extension to a Keboola Connection component family - Ooyala Video Analytics Extractor, which will help you with the extraction of the analytical data from Ooyala Analytical backend.

The component has quite flexible options for the configuration and you can get (aggregated) data based on various metrics and timeframes. 

There are also a lot of things for your convenient on the Ooyala backend. A good example are the error messages, if you put something unexpected into the configuration, the backend will raise a very specific response which helps you to debug the configuration easily.

This writer is developed independently by Blue Sky Media. For more information on how to use the writer, please refer to the documentation. In case you run into some issues or you have more questions, please contact me directly. 

Recently, there was an announcement from Apple about their plans to deprecate the iTunes Connect Autoingest tool by the end of November, 2016. They also mentioned the new way how to download financial and sales data from their APIs and for that reason they made available the new Reporter API.

In order to avoid any potential problems, it is my pleasure to announce that the iTunes Connect Extractor was updated and from now on it started using the new APIs which helps you to keep downloading data from the Apple reporting without any problem.

The new set of APIs is not the only change. I focused all my effort on simplicity and simplified the way how to pass the input params into Keboola. That means a lot of bigger things are now managed 'under the hood' and you don't to worry much about it. For instance, if you start selling the content in any new country, the extraction process will handle that and you will see the new region in your Keboola Storage object automatically. 

This writer is developed independently by Blue Sky Media. For more information on how to use the extractor, please refer to the documentation. In case you run into some issues or you have more questions, please contact me directly. 

We're encountering difficulties with our MySQL transformation server, some jobs are ending up with an application exception. We're closely monitoring this issue and restarting all failed orchestrations until the situation gets stable.

We're sorry for any inconvenience.

We're affected by DockerHub and Quay.io Service Disruption. Some components are failing. 

We'll update this post once the disruption is over and will restart all affected orchestrations.

You can also check the official DockerHub status page and Quay.IO status page for more information.

We're sorry for this inconvenience.

UPDATE: The Quay.IO disruption is over.