November 2, between 2:43am CET and 3:14 CET we experienced Snowflake service degradation in EU region that led to slow down of the orchestrations. The issue has been resolved. We apologize for the inconvenience caused.
Complexity Badges
There are components in KBC which you can setup in just a few clicks with only basic knowledge. But there are also components which require you to have deep knowledge about how it works. For this reason we have introduced Complexity Badges to be able distinguish between these types of components even before you start setting them up.
Not all components have assigned Complexity Badges yet, but we are continuously working on updating the components catalog.
Minor Improvements
- When you are retrying failed orchestrations it will now continue from where it failed by default.
- Transformation backends have new labels with icons.
Components
- Medio has released a new Google Search Console extractor.
- Teradata extractor supports port parameter.
- New Line Endings processor allows you to normalize line endings to unix type.
- New Heureka.cz and Heureka.sk extractors provided by Medio replacing previously deprecated Heureka extractors.
- Improved performance of tables listing for MySQL, PostgreSQL and SQL Server extractors.
Restbox shutdown
We would like to remind you that the Restbox component was deprecated in July 2018 and will be completely shut down on November 1, 2018.
If you still have some Restbox configurations in your projects, please migrate them to one of following replacements:
- S3 extractor
- S3 writer
- HTTP extractor
- Keboola Connection Storage extractor
- Keboola Connection Storage writer
We have identified a bug in the primary key implementation in Storage which could lead to improper data deduplication. Only a very limited number of tables is affected by this bug – 7 tables in all KBC projects in all stacks. We'll be contacting owners of the affected projects soon to help fixing the affected tables.
Root Cause
The deduplication stopped working when a column used in a compound primary key was deleted.
During this operation, the information about the whole primary key was unknowingly dropped in the Snowflake backend and this was not propagated correctly to our Storage metadata that still contained the primary key (minus the deleted column). In Snowflake, commands such as ALTER TABLE ... DROP COLUMN ... immediately drop the whole primary key if it’s dropping a column of a compound primary key. The deduplication process retrieves primary key information from the DESCRIBE TABLE ... Snowflake command which shows no primary key in the affected tables, but our metadata still incorrectly shows that a primary key is set.
We are implementing a fix that will store and retrieve primary keys from a single source.
Operating with Primary Key Columns
- Deleting columns which are part of the table primary key is no longer supported in Storage.
- To delete a primary key column please drop the primary key first.
- To change primary key of a table you will need to first remove the primary key and then set it again.
Updated Components
- MS SQL Server extractor has had a driver update. Advanced queries now have slightly different behaviour so it is recommended to switch to simple table and column selected configurations. Where that is not possible, please see the documentation for further help.
- Snowflake writer - minor bugfixes and enhancements
- primary key is added when creating a table
- nonexistent schema/warehouse validation
- warehouse detected correctly for users with different login name and user name
- Database extractors - column datatypes are now shown in UI
Minor Improvements
- You can now change the sharing type of a shared bucket in the storage console.
Around 1:30am CEST one of the job worker instances stopped processing assigned jobs. This could have lead to jobs being stuck in the processing state for a long time without any activity.
At 11:15am CEST the worker instance was terminated and all unfinished jobs started processing on other instances.
We're sorry for this inconvenience.
Database storing locks was restarted at 03:49 UTC which caused the job failures. Also some of the jobs were queued after this failure.
The backlog of all jobs was cleared at 06:15 UTC. The system is fully operational now. We're working on infrastructure changes which should prevent similar issues.
The maintenance period in the US region has just finished. All systems are back online and working properly.
Thank you for your patience.
The maintenance period in the EU region has just finished. All systems are back online and working properly.
Thank you for your patience.
The pre-announced maintenance period for the US and EU regions has just started. The estimated downtime is 5 hours.
There will be a maintenance period on Saturday, October 6th, 2018 from 8:00am CEST and should take less than 5 hours.
We will be upgrading component job indices and metadata databases.
All projects in connection.keboola.com and connection.eu-central-1.keboola.com will be inaccessible during the maintenance.