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
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.
Over the past few years, we’ve introduced several standalone Keboola Connection Applications that accomplish specific tasks. With our focus shifting to core Keboola Connection, we’ve made the decision to discontinue support for the Sardine App. This means that as of today, January 15th, 2016, we won't be making any further Sardine improvements or updates. As of April 15th, 2016, support for Sardine will be completely discontinued.
What will happen after April 15th, 2016?
You can expect that Sardine will continue to work as normal for some time. However, future updates of related APIs might result in certain features breaking. Since Sardine will no longer be supported, we won't be updating it in these cases.
Suggested Alternative
For clients using Sardine to provision users for their GoodData's projects, we suggest you to switch to the 3rd party Keboola Connection application made by BizzTreat.com. You can find it in Applications. Please don't hesitate to contact BizzTreat.com with feature suggestions or for help with implementation.
For clients using Sardine for GoodData access via a branded UI, we suggest using the http://www.dashboardizer.com/ developed by Slowpath.com. Feel free to contact them directly for a quote.
