Release notes
Firebolt continuously releases updates so that you can benefit from the latest and most stable service. These updates might happen daily, but we aggregate release notes to cover a longer time period for easier reference. The most recent release notes from the latest version are below.
- See the Release notes archive for earlier-version release notes.
Firebolt might roll out releases in phases. New features and changes may not yet be available to all accounts on the release date shown.
Firebolt Release Notes - Version 4.9
New Features
Added the enable_result_cache
setting for controlling query result caching during benchmarking
You can set enable_result_cache
to FALSE
to disable the use of Firebolt’s result cache, which is set to TRUE
by default. Disabling result cashing can be useful for benchmarking query performance. When enable_result_cache
is disabled, resubmitting the same query will recompute the results rather than retrieving them from cache. For more information, see Result Cache.
Added LAG
and LEAD
support for negative offsets.
The second parameter in both LAG and LEAD can now accept negative numbers. Given a negative number, a LAG
will become a LEAD
and vice versa. For example, LAG(x,-5,3)
is the same as LEAD(x,5,3)
.
Performance Improvements
Faster string searches for case-insensitive simple regular expressions in REGEXP_LIKE
Simple regular expressions in REGEXP_LIKE with case-insensitive matching, using the i
flag, now use the same optimized string search implementation as ILIKE, achieving up to three times faster runtimes in observed cases.
Bug Fixes
Empty character classes in regular expressions
Fixed a rare case where empty character classes were mistakenly interpreted as valid character classes instead of being treated as raw characters. In cases like []a]
, the expression is now correctly interpreted as a pattern that matches any single character from the list ]a
, rather than treating []
as an empty character class followed by a]
.
Trailing backslash in regular expressions
Fixed a rare case where invalid regular expressions with a trailing backslash \
were accepted.