Database extractor can be now configured via UI that can be found in KBC under “Extractors” tab
We are experiencing problems with one of our server causing fails of some GoodData Writer jobs. They typically end with “Job execution error” message without other explanation. We are working on fix. Thanks for your patience.
Update: The problem should be fixed by now.
On the new sandbox credentials page you can now share your sandbox database to another user in the same project. The user, you’re sharing your sandbox with, needs to have active sandbox credentials, and your sandbox database will show up in the databases list in his MySQL client.
Reset Project - you can discard existing GoodData project and automatically recreate new one. Existing Writer’s configuration will be reused.
Turn Maintenance On - if you turn it on, all communication with GoodData API will be paused.
Reset Table - by pressing this button, GoodData dataset will be removed and your table configuration will be ready to create fresh dataset.
A new Elasticsearch Writer and Extractor came live, enabling you to query your data in real time using all Elasticsearch’s endless possibilities.
We introduced some security improvement to generation of SSO links which could cause you problem if you threw away default GoodData project of your writer and use some other instead. In that case let us know on support@keboola.com please.
Data in some buckets are not accessible at the moment, bucket’s database recovery is in progress.
UPDATE
Everything should be back in normal.
You can now define which rows are deleted in the output table. This only makes sense with incremental turned on though.
List of tables is now available in bucket detail.
We are investigating issue with slow Storage API table imports on some table, some transformations have failed on time import limits.