• Bucket description is optional when creating new bucket
• Tables including columns can now be listed by one API call. 
• Fixed updating of Redshift alias SQL in Firefox

After June 1st 2015 we'll be enforcing strict limits on MySQL queries. All queries longer than 30 minutes (1800 seconds) will be terminated and the transformation will fail. You can now see duration of all queries longer than 2 minutes (120 seconds) in event log of any Transformation job so you can take optimization steps in advance.

We're introducing this limit to prevent errors like forgotten indexes and also to balance load on the shared MySQL Transformation database.

If your queries take significantly longer time than 30 minutes, please consider migrating your project to Redshift.

Our MySQL sandbox server (tapi-ovh.keboola.com) is down. We're firing up another server, will be up shortly.

UPDATE 4.43pm PST: Our backup sandbox server (tapi-sandbox.keboola.com) is up and running.

The Database Extractor now supports Oracle. 

We're experiencing very slow connection between our workers and the sandbox DB server. Please bear with us, we'll keep this post updated.

UPDATE 9.30pm PST: Looks like the connectivity is back at full speed. Thanks for your patience.

AdWords Extractor has been updated to AdWords API 2015.02, see http://googleadsdeveloper.blogspot.cz/2015/03/announcing-v201502-of-adwords-api.html for list of new features. 

Some AWQL queries configured in the Extractor will stop working because there have been few changes in column names (the most visible is probably renaming of Conversions to ConvertedClicks).

We are experiencing mysql transformations processes to be running much slower than usually. We are working on fixing this issue. However, this does not affect the redshift based transformations which should be running normally.

Sorry for any incovience. 

Update (11:30am PST): Issue has been resolved, everything is running fine now.

Replace attributes

All attributes of table or bucket can be set by one API call 

File Storage RunId

RunId identifiing running job is associated to all Storage API Files generated by this job. At the moment files can be filtered by RunId http://docs.keboola.apiary.io/#get-%2Fv2%2Fstorage%2Ffiles

This is a building block for upcoming aggregation API which will be able to provide aggregated informations about jobs such as data size transfered in and out, imported or created tables etc. 

We're experiencing connectivity issues from AWS to some parts of the outer world (aka the Internet). As our transformation sandbox server (ovh-tapi.keboola.com) is not in AWS you may experience failures when creating sandboxes and credentials. If this is not resolved within AWS shortly, we'll be switching the sandbox server into AWS network. 

We will keep this post updated with the current status.

UPDATE (2:00pm PST): Connectivity seems to work fine now.

We're changing the way Facebook Extractor reacts to invalid accounts and tokens. Previously all invalid accounts/tokens were automatically disabled (with an error event in Storage) and the extractor continued with extraction. 

As this event was easy to miss and there was no other notification about an invalid token/account, we switched to a more strict behavior. Any invalid account/token will stop the execution of the whole job/orchestration with an explaining message:

You need then to change the token or disable the account manually. 

For any questions and comments do not hesitate to contact us at support@keboola.com.