Snowflake announced a planned change of behavior to the the SQL RIGHT function which returns returns the rightmost substring of its input. The change is planned for July 27-31, 2020.
With the current behavior, the RIGHT function returns an empty string if the input string is shorter than the requested length.
With the new behavior the RIGHT function will return the whole input string if it is shorter than the requested length.
See the example below:
SELECT RIGHT('hello', 2) AS "RIGHT", LEFT('hello', 2) AS "LEFT"
UNION SELECT RIGHT('hello', 5), LEFT('hello', 5)
UNION SELECT RIGHT('hello', 50), LEFT('hello', 50);| RIGHT | LEFT |
|---|---|
| lo | he |
| hello | hello |
| hello |
| RIGHT | LEFT |
|---|---|
| lo | he |
| hello | hello |
| hello | hello |
While the current behavior is obviously incorrect (and inconsistent with the LEFT function) we can't rule out the option that results of your transformations might be affected or that some code is inadvertently relying on the current buggy behavior. Please feel free to contact our support (use the support button in your project) where we can provide you with further assistance (e.g. a list of possibly affected transformations or queries).
10 Jul 2020 08:55 UTC We're seeing a higher load and longer execution time in EU Snowflake queries. We are investigating the causes. Next update in 60 minutes or as new information becomes available.
10 Jul 2020 09:55 UTC Unfortunately we have no update at the moment. We have added some processing power to the Snowflake warehouse and we are monitoring the situation closely to see if that helps. Job processing should be fine, you may only see slight delays. Next update in 60 minutes or as new information becomes available.
10 Jul 2020 11:10 UTC No update at the moment. Next update in 60 minutes or as new information becomes available.
10 Jul 2020 12:30 UTC No update at the moment. Next update in 90 minutes or as new information becomes available.
10 Jul 2020 14:00 UTC We're in touch with Snowflake support and trying to identify the root cause. Next update in 3 hours or as new information becomes available.
10 Jul 2020 18:00 UTC We're changing certain scaling parameters of the Snowflake warehouse to see if it can help resolve the issue. Next update in 24 hours or as new information becomes available.
11 Jul 2020 18:50 UTC The configuration change helped and we're fully operational. This is the last update of the incident. Thanks for your patience!
9 Jul 2020 08:24 UTC We're seeing a higher load and longer execution time in EU Snowflake queries. We are investigating the causes. Next update in 60 minutes or as new information becomes available.
UPDATE 9 Jul 2020 8:54 UTC We have added additional power to the warehouse to help process the queued queries. Currently the situation seems normal, but we're monitoring it closely for next couple hours. Next update in 90 minutes or as new information becomes available.
UPDATE 9 Jul 2020 9:18 UTC After all the additional workload has been processed we have scaled down the cluster, but we're seeing queuing jobs again. We have again scaled up the cluster to help with the load. We're monitoring the situation closely. Next update in 60 minutes or as new information becomes available.
UPDATE 9 Jul 2020 10:15 UTC We're in touch with Snowflake support to resolve this issue. Meanwhile we have decreased the worker capacity so the Storage jobs may be queued on our end. This should take some load off the Snowflake warehouse to maximize it's performance. Next update in 60 minutes or as new information becomes available.
UPDATE 9 Jul 2020 11:45 UTC Snowflake engineering team is resolving the underlying issue. Thanks to the throttling on our end there are currently no delays in jobs processing. Next update in 60 minutes or as new information becomes available.
UPDATE 9 Jul 2020 12:30 UTC Snowflake informed us that the issue was fixed. We're restoring platform parameters to the original values and will continue monitoring the situation. Next update in 60 minutes or as new information becomes available.
UPDATE 9 Jul 2020 13:20 UTC All operations are back to normal and everything is fully working.
We're sorry for the inconvenience and appreciate your patience.
From now on, you'll be able to see invited users on the dashboard.
We are introducing shorter expiration times for files in Storage.
From July 13, newly created files will have the following expiration settings:
- 15 days for table import files and manual uploads
- 48 hours for table export files
Expiration of existing files will not be affected by this change.
We’re currently experiencing OAuth authorization errors returning error:
Docker encryption error: Contact support@keboola.com and attach this exception id
Only authorization of new configuration is affected, running jobs aren't affected. First occurrence of the error was at 14:02 UTC.
We are performing rollback. Next update in 60 minutes or as new information becomes available.
UPDATE 14:42 UTC - Rollback was successfully performed on EU region. Rollback for US region is in progress. Next update in 60 minutes or as new information becomes available.June 17, 10:26 UTC - After releasing a new version of OAuth broker we have identified that UI of components relying on OAuth authorization is broken, displaying only message: "Something went wrong".
UPDATE 11:01 UTC - We have reverted the release to previous version, which restored the functionality. We are still investigating this issue. It's possible that the problem also affected jobs of these components.
UPDATE 11:31 UTC - We have confirmed that the jobs of the components were unaffected by this bug
Some API calls to run jobs are ending with an application error in the US region. We're investigating the causes.
Update 0:40 UTC: The problem is resolved now. One of the API worker freeze. Running jobs were not affected. We will post a detailed analysis within a week.