Keboola Status

DoubleClick Extractor Update

DoubleClick Extractor has been updated to support version 2.3 of DoubleClick API.

Creating tables with large amount of columns bugfix

Creating tables with large amount of columns caused internal error in Storage API. Now it produces a user error with proper error message. Current limits for number of columns are 4096 on MySQL backend and 1600 on Redshift.

GoodData Writer API news

We are progressively working on new version of GoodData Writer API. You can see it's current status in Apiary: http://docs.keboolagooddatawriterv2.apiary.io. This week we finished resource for handling user filters and SSO access to projects.

Other posts this week

• Twitter extractor issues
• SAS Writer
  
• Automatic configuration of GoodData Writer from existing project
  
• Jobs outage
  

Jobs were unaccessible between 4:30am–4:31am PST which caused failure of few orchestrations. These were restarted.

UPDATE 6:22am PST

The issue reappeared between 5:48am and 6:09am PST. All failed orchestrations were restarted.

We are sorry for any inconvenience.

If you create new Writer's configuration from existing GoodData project, our app will read it and attempt to set it up automatically. It will also prepare data bucket in Storage API out stage with tables. So you just need to fill them with data and you can start using the writer instantly.

Select an existing Redshift bucket and SAS writer will provide credentials and detailed instructions on how to connect to it from SAS via ODBC Redshift driver.

We have been experiencing increased error rate from our Twitter extractor recently.

Today we've updated the extractor and the issue seems to have been remedied. It is possible that some configurations will still finish with an error on import to Storage API. To fix that error, backup and delete the target table that failed to be imported. The results table creation has been improved in the extractor so that this error should not occur any longer, but it's possible some of existing tables have incorrect columns, or some of their existing columns will have to be processed again by the extractor upon receiving such data from Twitter.

We apologize for the inconvenience! Please contact us at support@keboola.com in case this error keeps occuring even after deleting problematic result tables.

In our effort to bring you all updates we're now starting a regular weekly post that will include a list of all changes, that didn't make it to a separate post.

Input mapping UI bugfix

Creating a duplicate destination in input mapping is now displayed as an error.

Input mapping UI improvement

When selecting a table, the destination is automatically populated with table name (previously with full table id).

Storage: Redshift primary keys bugfix

Setting a primary key on a Redshift table failed when there was another table in the project with the same name and different columns.

Storage: MySQL long primary key bugfix

Setting a compound primary key with more than 4 columns failed with an internal error. This was fixed and it shows a warning that MySQL primary key is limited to 4 columns.

Other posts this week

• End of Life Announcement for Telfa Extractor
  
• End of Life Announcement for Elasticsearch Writer/Extractor
  
• End of Life Announcement: Remote Transformations (eg. Text Splitter)

As of today, January 22th 2016 we won't be making any further improvements or updates on Remote Transformations (including the executor interface in Transformations and all remote transformations, eg. Text Splitter)

As of February 22th 2016 Remote Transformations functionality will be completely removed from Transformations.

Text Splitter functionality can be replaced by an R transformation, see the demo code.

Contact our support, if you need any assistance with migration to R transformation.

As of today, January 21th, 2016, we won't be making any further improvements or updates on Elasticsearch Writer/Extractor. As of February 21th, 2016, Elasticsearch Writer/Extractor will be completely removed.

Please note, that Elasticsearch Extractor functionality can be easily replaced with our Generic Extractor. 

Feel free to contact our support if you need any assistance.

Telfa Extractor functionality is covered by our Generic Extractor. Therefore as of today, January 20th, 2016, we won't be making any further improvements or updates on Telfa Extractor. As of February 20th, 2016, Telfa Extractor will be completely removed.

Here is an example on how to configure Generic Extractor for Telfa API.

Contact our support, if you need any assistance with migration to Generic Extractor.

The MySQL sandbox server (sh-tapi.keboola.com) is currently not available, we're investigating the cause.

Update Jan 20 5:35pm CET

The backup MySQL sandbox server tapi-sandbox-fallback-3.keboola.com is up and serving all sandbox requests. All previous sandboxes were deleted and all credentials cleared. We'll be transitioning back to the original server sh-tapi.keboola.com tomorrow. Please check your sandbox credentials to be sure you're logging on the right server.

We're sorry for this inconvenience and thanks for your understanding

Update Jan 21 5.33pm CET

The original MySQL sandbox server (sh-tapi.keboola.com) is back up. All new sandboxes will be created on this server, all currently existing sandboxes will remain on tapi-sandbox-fallback-3.keboola.com and will be purged on Sunday night.