We're encountering difficulties with our MySQL transformation server, some jobs are ending up with an application exception. We're closely monitoring this issue and restarting all failed orchestrations until the situation gets stable.
We're sorry for any inconvenience.
We're affected by DockerHub and Quay.io Service Disruption. Some components are failing.
We'll update this post once the disruption is over and will restart all affected orchestrations.
You can also check the official DockerHub status page and Quay.IO status page for more information.
We're sorry for this inconvenience.
UPDATE: The Quay.IO disruption is over.
Between Oct 26 10:40am UTC and Oct 26 12:50am UTC we encountered issues connecting to Snowflake.
Some jobs might have ended with Internal error or one of these exceptions:
We're investigating the root cause with Snowflake support and identifying and restarting affected orchestrations.
We have created a new currency exchange rate extractor. This component allows you to extract currency exchange rates as published by European Central Bank (ECB). Its configuration is dead simple, all you need to do is select the source currency (USD and EUR are currently supported).
This extractor provides the same data in the same format as the old extractor (which had to be configured through support). We encourage you to switch to the new one - set it up as any other extractor. We will keep running the old extractor till January 2017. Just let us know once you don't need it, so that we can deactivate it and stop magically pushing data to your project.
Like in the old currency extractor, the resulting data contains gaps for bank holidays (including weekends). If you would like to fill the gaps with last known value, you can use a little SQL script we hacked together.
We're encountering a higher number of "Output mapping does not match destination table" errors in applications today since 10:30am. This was caused by deploying strict validation in output mapping. Our detection script did not detect and prevent all cases, so we're rolling back this release and restarting all affected orchestrations.
We're sorry for this inconvenience.
On October 21, 2016 at 11:43:58 PM CEST/UTC+2 one of our database servers was restarted due to a hardware failure. Jobs running during that time failed when trying to reconnect to the database later in the processing.
Update October 21, 2016 at 01:20 AM CEST/UTC+2: Jobs/orchestrations affected with this restart didn't stop processing and finished successfully, they may show incorrect job result as error instead of success.
We're sorry for this inconvenience and we're restarting all failed orchestrations.
We have investigated issues with Amazon DNS service in us-east region.
It affects jobs processing and API availability of our components. Thanks for patience.
UPDATE:
AWS confirmed the problem - 5:15 AM PDT We are investigating elevated errors resolving the DNS hostname used to access the EC2 APIs.
AWS status update - 5:51 AM PDT We have identified the root cause of the issue causing errors resolving the DNS hostname used to access the EC2 APIs and are currently working to resolve.
Our transformation MySQL server was under heavy load between October 20th 12:00am and 3:00am UTC. Transformation processes were slowed down or halted.
We have identified the blocking processes and all operations returned to normal. In a few cases we have terminated stalled transformations and restarted the orchestrations.
We're sorry for this inconvenience.
Even though the weekly status has been a little weak recently, it does not mean that we're dawdling. We are working on some quite big internal things, which take much more than a week. For example (in no particular order):
All of the above are in various state of completeness (except the last item, which is complete). So stay tuned for more announcements when these features are finished.
We're opening OpenRefine transformations to public. You can now use OpenRefine in your transformation pipeline.
No further need to write long string replaces in SQL or study how to open CSV files in Python or R. OpenRefine excels in data cleanup and many other data wrangling tasks.
To create an OpenRefine transformation choose OpenRefine (beta) when creating a new transformation.
Learn more about OpenRefine and its functions and about OpenRefine integration in Keboola Connection.