Snowflake data previews in Storage were returned in wrong encoding since this Friday which caused that some characters were missing.
This is fixed now. Stored, imported and exported data wasn't affected by this bug.
Sorry for any inconvenience.
We have updated the UI for the S3 Extractor and the CSV Import tool. We're keen on trying new things to improve your user experience with Keboola Connection and hope that these improvements offer a simpler and easier approach to editing your component configurations.
There is no difference between editing and non-editing state, everything is directly editable and the state of the Save button indicates if the configuration has been changed or not.
If this approach proves useful and stands the test of time, we'll carry it on to other components as well.
Let us know what you think!
Between Mar 29 10:03 UTC and Mar 29 13:10 UTC all Snowflake Writer jobs had accidentally 15 seconds limit and potentially ended-up by error message:
Statement reached its statement or warehouse timeout of 15 second(s) and was canceled.
All Snowflake writers should be fully operational now. Only four jobs were affected by this bug - Please accept our sincere apologies for this inconvenience!
Trash for configurations
One of the most wanted features in Keboola Connection was the option to restore deleted configuration.
We are happy to announce this feature is now avalable for all users.
This feature allows you to:
1. Check who and when deleted a configuration
2. Restore configuration
Configuration Restore is supported by all components, except Orchestrator, GoodData Writer and some old components which have configuration in a bucket created in `sys` stage.
3. Delete configurations permanently
If you use "Empty Trash" button, all configurations will be deleted permanently. There is no other way to restore them!
As always, you can use mentioned functionality by calling our Storage API: http://docs.keboola.apiary.io/#reference/component-configurations/configuration-restore/restore-deleted-configuration
Fixes and improvements
- added optional parameter to specify warehouse in Snowflake Database Writer
- fixed credentials editing in DB writers
tldr; If you're using the old Facebook Ads (Deprecated) extractor then migrate to new extractor or set the `api_version` attribute to v2.8 in corresponding configuration sys table of the old extractor before April 25 2017.
Marketing API(aka Facebook Ads API) version v2.7 has been marked as deprecated and will stop working from April 25, 2017. The latest version is v2.8, see Marketing API Changes in v2.8.
The New Facebook Ads extractor uses version v2.8 by default so no actions are required.
The Old Facebook Ads extractor uses version v2.7 by default. The best thing to do would be to migrate to the new extractor. Another possibility is to override the api version setting: Go to the configuration sys table and update the attribute api_version with value v2.8. There should be no incompatibilities, but we offer no guarantees.
New Components
- Facebook Extractors have been rewritten. For more information see this post.
New Features
- We added Table Data Filter to latest versions of our database writers. So it's possible to filter data by "days" and "conditions"
- New option of bucket sharing has been added. Now you can share buckets to your whole organization (by setting new sharing option) and anyone in your organization be able to link bucket to his project.
Minor Improvements & Fixes
From now, attempt to set nonexistent column as Primary Key (in Storage API) will cause an user error
As you might have already noticed, new versions of Facebook Extractor and Facebook Ads Extractor, that runs on container based architecture, are available. The old ones have been marked deprecated.
Improvements compared to the old extractors
- UI templates allow you to easily configure the extraction.
- More customisation possible (more endpoints, different api versions)
- The output tables have more intuitive structures. Unfortunately this means that direct data transfer from the old extractor is not possible
- Tables are always incrementally imported with auto-detected primary keys
Migration
Due to various differences in output tables structure and configuration between new and old Facebook extractors we don't provide automatic migration tool, however there is basic tutorial on how to create configuration with same authorized account. See here for Facebook and here for Facebook Ads extractor.
We are always glad to receive feedback, so if you have any questions or ideas how to improve this component, please don't hesitate to contact us. Go ahead and try it ;)
We no longer provide Keboola MySQL database provisioning for database writers. Existing Keboola provisioned MySQL databases will be kept intact till the end of Jun 2017. Existing MySQL users will have to move to their own MySQL instances. Here are a few suggestions of vendors which provide MySQL provisioning:
You can keep your data inside KBC and connect to them directly. We believe that our Snowflake Writer is a great replacement for your existing MySQL Writer, so please check it out!
Do not hesitate to contact if you have any questions!
Signing into KBC with your Google account is not working presently.
We're investigating and hope to have it resolved shortly.
In the meantime, please sign in using the standard email and password method.
Sorry for this inconvenience, this post will be updated when further information becomes available.
UPDATE 08:21 UTC We have identified the issue. The fix will be deployed in ASAP.
UPDATE 08:55 UTC Signing in with your Google account is again fully operational.
New Components
Snowflake Extractor
- Snowflake Extractor is now in private beta. For an early access please contact us at support@keboola.com.
Minor Improvements
Next Event application now estimates the date of the next event
Fixes
-
Fixed all dead links on status.keboola.com and help.keboola.com
Google Sign In correctly redirects after authorization
Keboola Connection cookies use the secure flag
Password reset does not leak information about (non)existing user
Orchestrator trims notification email addresses, no more whitespace mess
GoodData Writer properly propagates errors when creating a new writer
GoodData Writer does not remove our domain admin from a project which is shared among more writers