Maintenance Release Changelog
On this page
2024-12-04 Version 8. 0. 35
This is the final release of SingleStore version 8.
2024-08-26 Version 8. 0. 34
-
Bugfix: Fixed a rare race condition where PITR would incorrectly operate on an unrecoverable database.
-
Bugfix: Fixed an issue that could occur when replacing JSON expressions with computed columns in
GROUP BY
lists. -
Bugfix: Fixed an issue that could cause scans using non-unique indexes to return wrong results or to crash.
-
Bugfix: Fixed an issue where user defined variables could read collation-related variables incorrectly during a
SET @var = .
command.. . -
Bugfix: Fixed incorrect results in an uncommon scenario where hash join operators with an optimization path need to spill.
-
Enhancement: Added the
throttle_
engine variable which controls how far the system allows a child aggregator to lag behind replicating the transaction log of its master aggregator before throttling is applied to the master aggregator.replay_ behind_ tail_ mb -
Bugfix: Fixed an issue in
ALTER TABLE
when adding a computed column containingJSON_
.BUILD_ OBJECT -
Bugfix: Addressed a crash issue with
REGEX_
.REPLACE -
Enhancement: Allow Kerberos users to skip password validation for users who are authenticated with plug-ins.
-
Bugfix: Addressed a crash issue occurring while executing queries with vector builtins on clusters running via Docker containers on Mac machines equipped with Apple silicon processors (M1).
-
Bugfix: Fixed an issue that caused rare "Arrangement already exists in namespace" errors in recursive CTE queries.
2024-04-18 Version 8. 0. 33
-
Fixed a case where a killed query could incorrectly return a JSON error rather than query interrupted message.
-
MV_
queries can no longer block garbage collection.DISK_ USAGE -
Fixed a JSON insertion failure to old utf8 sample tables that contain utf8mb4 characters by encoding it with base64 format beforehand for backward compatibility.
-
Fixed an issue with a blob file leak in a rare crash scenario.
-
Fixed a potential deadlock in a scenario involving DDL, a 2PC transaction, and a concurrent failover.
-
Updated timezone data, now using IANA's tzdata version 2024a; new timezones Kyiv, Ciudad_
Juarez, and Kanton supported.
2024-03-13 Version 8. 0. 32
-
Fixed an issue in background merger that allowed concurrent deletes of empty segments.
-
Added the ability to collect and send SingleStore Self-Managed usage telemetry data to SingleStore via the
EXPORT TELEMETRY
sql command (for 1-time or ad hoc use) or thesend_
engine variable.usage_ telemetry This defaults to OFF. Added an associated information schema table: usage_
telemetry_ status -
Added spilling metrics for TopSort (
ORDER BY with LIMIT
).
2024-02-27 Version 8. 0. 31
-
Added new metrics to
memsql_
based on theexporter information_
columns.schema. mv_ sysinfo_ disk -
Fixed an issue with a sensitive information leak inside of out-of-memory reports.
-
Fixed a bug in backup restore when the backup has a corrupted GV timestamp in the about snapshot record.
-
Fixed an issue with
hex()
not handling decimal types correctly. -
Fixed an issue with exporter not working with Public-Key Cryptography Standards #8(PKCS#8) pem format.
-
Fixed a crash that occurred when trying to grant access to the table with no context database in per-privilege mode.
-
Added ability to
memsql_
to always return all sub-activities of an aggregator activity.exporter -
Fixed an issue with backups not throttling after snapshot.
-
Fixed an optimization phase out-of-memory issue caused by operators generated for an unused wide user table.
-
Appended column name to include the error message when an invalid date/time is inserted into a column.
-
Fixed an issue to show the number of rows affected with
SELECT INTO
object storage. -
Resolved an issue related to
FROM_
andBASE64 TO_
built-ins when processing large string inputs, preventing potential errors in reading communication packets.BASE64 -
Increased
backup_
max value to 15.multipart_ upload_ concurrency -
Improved the backup download errors.
-
Fixed an issue where
INSERT.
queries with a partition_. . SELECT id() filter generating an error. -
Fixed an issue with memory crashing when using
REGEXP_
orMATCH, JSON_ INCLUDE_ MASK, JSON_
built-ins.EXCLUDE_ MASK -
Fixed an issue with
START PIPELINE FOREGROUND
skipping files in some circumstances.
2024-01-17 Version 8. 0. 30
-
Fixed an allocation issue that caused poor performance on high load insertion queries.
-
Fixed an issue with memsql_
exporter working improperly in ANSI_
QUOTES sql_
.mode -
Added the
optimizer_
engine variable which disables predicate transitivity on query rewrites if set todisable_ transitive_ predicates TRUE
.This engine variable defaults to FALSE
. -
ALTER PIPELINE
settingmax_
to use a default 0 value is now allowed.partitions_ per_ batch -
JSON_
escape characters were not working as expected.KEY -
Updated the
information_
view to reflect the account status for locked users.schema. USERS -
Fixed a crash that occurred when user-defined variables are used in the
GROUP BY
andORDER BY
clauses. -
Fixed an error that occurred when a user attempts to access a view that is based on a table that has no privileges granted on it.
-
Added support for creating a
DEEP COPY
of tables with computed columns. -
Improved the ability to kill queries containing JSON built-in functions.
2023-12-05 Version 8. 0. 29
-
Fixed an issue where the wrong table was dropped while creating a
DEEP COPY
with computed columns. -
Fixed an issue where the number of rows affected with
SELECT INTO
object storage was erroneously reported as 0 rows. -
Fixed an issue where small tables use an inappropriately small sample size by setting a lower bound.
This mostly affects reference tables.
2023-11-21 Version 8. 0. 28
-
Fixed a potential crash that could occur when
LOAD DATA
is used without a database context. -
Pipeline state is now shown consistently across primary and child nodes.
-
Fixed an issue with
JSON_
used in UDFs.SET_ JSON -
Fixed a potential issue related to hash join spilling.
-
Reduced blocking in query compilation after evicting many (10K+) plans in the plancache.
-
Disabled group-by on encoded data when there is an aggregate on full-text match.
-
Fixed a potential security issue with users created without a password.
-
Fixed some cases where
APPROX_
erroneously included nulls in the count.COUNT_ DISTINCT_ ACCUMULATE -
Added additional node metrics to the /cluster-metrics endpoint of the
memsql_
.exporter -
Added three new fields to
MV_
:SYSINFO_ DISK -
READ_
: Number of read operations performed by the device since start up.OPERATIONS_ CUMULATIVE_ PER_ DEVICE -
WRITE_
: Number of write operations performed by the device since start up.OPERATIONS_ CUMULATIVE_ PER_ DEVICE -
DEVICE_
: Name of the device to which the values inNAME read_
andoperations_ cumulative_ per_ device write_
are associated.operations_ cumulative_ per_ device
-
-
Addressed some performance issues that occur when performing large sets of security operations (creating a lot of groups/users/roles, etc.
) via the new privilege_
engine variable.caches_ update_ mode This variable can be used to temporarily disable updating privilege caches while performing security operations such as: granting/revoking permissions to/from users, granting/revoking permissions to/from roles, adding/deleting roles to/from groups, adding/deleting users to/from groups, role deletion, group deletion.
This can result in a performance gain. IT IS IMPORTANT that the privilege cache updates be reenabled (value set back to
always
) once the administration work is finished.To use this variable:
-
Set the value to
never
. -
Perform the operations.
-
Set the value back to
always
.
-
2023-10-17 Version 8. 0. 27
-
Reverted the ability to use SSL keys with a password in the HTTP API.
2023-10-11 Version 8. 0. 26
-
Added ability to use SSL keys with a password in the HTTP API.
-
Added resource pool metrics to the cluster-metrics endpoint of the
memsql_
.exporter -
Fixed an issue where unlimited storage databases stored on Amazon S3 could run out of connections under intense loads.
-
Fixed an issue where an incorrect result is produced when the engine variable
query_
is set withparallelism flexible_
.parallelism query_
is deprecated andparallelism query_
should be used instead.parallelism_ per_ leaf_ core -
Removed an unexpected warning related to the engine variable
query_
(which is deprecated) when a query contains anparallelism ORDER BY
clause with anIN
list filter that matches the table's shard key.
2023-09-11 Version 8. 0. 25
-
Fixed a bug where an aggregator result table hits a lockdown when
sql_
is set.select_ limit -
Fixed a memory leak issue in the
memsql_
process.exporter -
Fixed an issue where
memsql_
was generating too much "pipeline_exporter error" data. -
The
SHOW COLUMNAR MERGE STATUS
command now outputs status for tables with empty sort keys. -
The following commands now respect non-default
columnstore_
values:table_ lock_ threshold INSERT .
,. . SELECT . . . ON DUPLICATE UPDATE REPLACE .
, and. . SELECT REPLACE .
.. . LOAD -
Fixed an issue where
VECTOR_
was returning incorrect results on shard tables.MUL -
Fixed an issue where
LIMIT
andOFFSET
after a window function with noPARTITION BY
clause were returning incorrect information.
2023-08-22 Version 8. 0. 24
-
Improved performance of multi-part GCS backups.
-
Increased
mv_
from varchar(64) to varchar(512).plancache. activity_ name -
Fixed a potential crash in NFS backup when encountering an IO error.
-
SKIP PARSER ERRORS
is now supported for Kafka.Additionally, a new related engine variable, pipelines_
, has been added.parse_ errors_ threshold -
Fixed an issue with significant memory reduction from spilling for hash join queries with variable length strings (varchar, text, etc.
) involved. -
Fixed a memory leak when using backreferences inside regexp built-ins (e.
g. `regexp_ substr()`). -
Fixed an issue where, when parsing a table with many secondary keys, an incorrect name was used to refer to table's the primary key.
-
SingleStore now supports in-place change of the
data_
for persisted computed column shard keys.conversion_ compatibility_ level We still suggest testing any existing applications before deploying a change to a production environment.
2023-07-25 Version 8. 0. 23
-
Added metrics to
memsql_
to show a breakdown of disk usage by SingleStore.exporter -
Added metrics to
memsql_
to show unlimited storage utilization statistics.exporter -
Fixed a JSON formatting issue with the
MV_
info schema table.EVENTS -
Fixed a potential issue where changing a user password would not change the connection pool password in the Data API.
-
Fixed a bug where the
mv_
table would show incorrect results for the plancache directory.disk_ usage -
Fixed an issue where creating a
TEMP
table with aPERSISTED
column would result in anER_
.TABLEACCESS_ DENIED_ ERROR -
Reverted the performance improvements for backups to GCS (Google Cloud Storage).
-
Fixed a bug for the statistic
blob_
value.fetch_ network_ time -
Fixed a performance bug regarding the prefetch queue's size when flexible parallelism is enabled.
The prefetch queue's size was increased from 10 to 10 times the number of scanning threads to improve query performance. -
Fixed an issue with the incremental restore of an unlimited database that would fail if the restore was larger than the disk.
-
Fixed a pipeline wrong state issue caused by an error in a table with a computed column.
-
Added support for Control Group v2 (cgroup v2).
-
Fixed an issue where a large spike in the query memory consumption on a any SingleStore node could cause replicas on the same node to become unrecoverable.
-
Fixed a bug where the permissions do not clear for Data Manipulation Language (DML) queries and then leak to subsequent Data Definition Language (DDL) queries.
2023-06-26 Version 8. 0. 22
-
Fixed a rare case where the query optimizer re-wrote a query into a non-equivalent query which produced more result rows.
-
Improved the performance of backups to GCS (Google Cloud Storage).
GCS backups are not using multi-part uploads. -
Fixed a crash that could occur if Linux refused to start a thread due to hitting a system limit on threads.
-
Introduced an optimizer feature where a single sharded table may be gathered to the optimizer in order to reduce duplicate work across partitions.
Two new engine variables were added to control this behavior: optimizer_
andmin_ reference_ tables_ for_ gathered_ join optimizer_
.min_ reference_ rows_ for_ gathered_ join -
Fixed an issue on sample tables that can be created with different collations on different partitions.
-
Added the
max_
engine variable.execution_ time It is unused and setting this variable has no effect. It exists so certain MySQL-compatible apps that have this variable set will not fail when connected to SingleStore. -
Added
mv_
anddisk_ usage mv_
information schema tables that report the breakdown of disk utilization by SingleStore.data_ disk_ usage -
PAM (Pluggable Authentication Module) users are now allowed to start and configure the
memsql_
process.exporter -
Added support for
ROW_
information function within views.COUNT -
Fixed a bug where a
HashJoin
on a materialized CTE gets executed as aNestedLoopJoin
in some query shapes causing slow join performance. -
Fixed the
SPLIT
string function that was not detecting the correct argument type when used inside a table-valued function (TVF) or a user-defined scalar-valued function (UDF). -
Improved the accuracy of the
blob_
statistic in query profiles.fetch_ network_ time
2023-06-06 Version 8. 0. 21
-
Fixed unlimited storage S3 multipart uploads to properly retry on 200 responses which contain an embedded "SlowDown" error, instead of failing immediately.
-
Reduced memory usage in situations where tables are repeatedly created and dropped.
-
Fixed an issue where memory accumulates over time if reshuffle or repartition operators are executed for many unique query shapes.
-
Introduced a new global engine variable
backup_
that can be used to improve blobstore backup performance.multipart_ upload_ concurrency The default value (3) can improve performance out of the box. -
Improved the performance of a left join of a reference table with a sharded table by pushing the reference table clauses to the leaves.
The engine variable disable_
must be set to "OFF" to enable this operation.reference_ table_ leftjoin_ where_ pushdown -
Fixed the
query_
output in profiles generated while the profiled query is executing.text -
Fixed an issue where the query optimizer could choose incorrectly between using the
HashGroupBy
or theStreamingGroupBy
operators. -
Fixed an issue where JSON computed column matching incorrectly triggers a
JSON_
function.EXTRACT_ <type> -
Fixed a
STR_
function bug when used with '%T' or '%r' in the format string.TO_ DATE -
Fixed a rare log file corruption issue with sync durability in unlimited storage databases.
-
Fixed an issue with handling a query that contains a common table expression (CTE) in a
CREATE VIEW
statement that has multipleUNION
operators.
2023-05-17 Version 8. 0. 20
-
Added cross-database support for Recursive CTEs.
-
Fixed a bug where
DEFAULT NOW/UUID/SYS_
is sometimes ignored when specified on a column in the primary key.GUID -
Fixed an issue where
JSON_
built-in returns a document with all fields, instead of zero fields for an empty mask '{}' case.INCLUDE_ MASK -
Added ability to
JSON_
to receive the columnstore optimization even if the entire JSON column is projected in the query.MATCH_ ANY() -
Fixed a crash caused by reusing plancache for a deleted link.
2023-05-01 Version 8. 0. 19
-
Fixed an issue with
DATETIME
columns withON UPDATE CURRENT_
defaults that could cause incorrect results.TIMESTAMP -
The
sql_
session variable now shows up inmode SHOW VARIABLES
and the mv_global_ variables view. -
Fixed an issue that could cause an incorrect error message to be generated on an out of memory error.
-
Fixed an issue where a NULL could be pushed down to a union which could cause the type-cast/collation to be lost, resulting in an error: "Operation 'Scanning a hash join build' is not allowed".
2023-04-25 Version 8. 0. 18
-
Fixed an issue where errors could occur during backup when large files are copied.
-
Fixed an issue where S3 pipelines could stop loading data from the bucket if files are deleted from the bucket while the pipeline is active.
-
Fixed an issue where, in rare cases, an
UPDATE
statement with a left join in the filter clauses could fail to execute. -
Fixed an issue where replica blobs could be loaded into the blob cache with an incorrect LRU timestamp.
-
Improvements to memsql_
exporter: Improved error handling and reduced memory usage. -
Fixed an issue with
ALTER USER
, and now the following syntax works as expected:ALTER USER user IDENTIFIED BY 'password'; -
Added
JSON_
function when applied to a JSON document; it will return a subset of the document based on the mask.INCLUDE/EXCLUDE_ MASK JSON_EXCLUDE_MASK(<json>,<mask>);JSON_INCLUDE_MASK(<json>,<mask>);
2023-04-17 Version 8. 0. 17
-
Added support for LOAD DATA from S3 for Avro and Parquet data.
-
Fixed a potential crash issue in
UPDATE
queries that involve joins and that have scalar subselects inSET
clauses. -
Fixed an issue where running
DROP PLAN FROM PLANCACHE .
on a query with invalid syntax could cause a crash.. . FOR QUERY -
Updated timezone metadata to include Mexico's latest timezone change.
-
Fixed an issue where
DETACH DATABASE
was not killing long running queries that were blocking the database from getting detached. -
Fixed an issue with missing row counts during optimization when sampling is disabled.
-
Fixed an issue where background mergers were not stopping quickly enough, resulting in delayed DDL operations or
REBALANCE
commands. -
Fixed an issue with setting
maximum_
on a single site that could cause the blob cache to shrink incorrectly.blob_ cache_ size_ percent -
Fixed an issue where
CLEAR ORPHAN DATABASE
could cause data loss if run when the master aggregator has a database in an unrecoverable state. -
Fixed an issue in information schema view
JSON_
where incorrect details were being shown for the leaf columns.COLUMN_ SCHEMA -
Fixed an issue where the memory used by an external function was not being freed quickly enough.
-
Fixed a column name resolution issue for recursive CTEs when the column type is the same across the base branch and the recursive branch.
2023-04-03 Version 8. 0. 16
-
The
default_
global variable will no longer be user-settable in SingleStore Helios, ensuring that it's always defined for the most optimal performance, according to the current resource size.partitions_ per_ leaf -
Fixed an issue where filters using the
range_
column in thestats information_
table were not allowed.schema. optimizer_ statistics -
Fixed an issue where incorrect results could be returned when segment-level flexible parallelism is used inside a subquery containing both a shard key filter and either an aggregate, a window function, or the limit clause.
-
Fixed an issue where an internal result table was not created for a recursive CTE involving data across databases.
2023-03-27 Version 8. 0. 15
-
Fixed an error that could occur when attaching databases with a snapshot file of greater than 5 GB.
-
Fixed an issue where too many rows are sampled from columnstore tables with more than 1 billion rows.
-
Fixed an issue with histogram estimation in columns with a negative value
TIME
type. -
Fixed an error caused by setting the
collation_
global variable to a non-default value when performing aserver REBALANCE PARTITIONS
resource availability check. -
Fixed "table partition count mismatch errors" that occur due to the following conditions: the system variable
enable_
is set and there is an upgraded workspace with an attached read replica.workspace_ ha -
Fixed an issue with DDL endpoint queries using a lower-than-specified query parallelism setting when workspaces are enabled.
-
Improved column type resolution for base and recursive branches in recursive common table expressions (CTEs).
-
Fixed an issue that prevents
GROUP BY Push-Down
optimization if the join filter contains a mismatched column type. -
Fixed a data conversion compatibility level 8.
0 error that may occur when sampling columnstore tables. -
Fixed a possible deadlock that may occur between the blob cache and the Rowstore Garbage Collection (GC) when the blob cache encounters an out-of-memory error.
-
Add an information schema table (
JSON_
) which shows the schema inferred for JSON columns in columnstore tables.COLUMN_ SCHEMA
2023-03-20 Version 8. 0. 14
-
Improved the parsing performance of queries that contain several tables.
-
Improved error handling when restoring from an incomplete incremental backup.
-
Improved the performance of S3 pipelines when Garbage Collection (GC) is enabled.
-
The
read_
,advanced_ counters snapshot_
, andtrigger_ size snapshot_
engine variables can now be set on SingleStore Helios.to_ keep -
Added new session variable
disable_
to prevent theremove_ redundant_ gby_ rewrite GROUP BY
columns from being removed when used in anORDER BY
clause. -
Added syntax to allow multiple leaf nodes to be detached using the
DETACH LEAF
command. -
Introduced disk and memory availability checks that run before a database is allowed to be attached to a workspace.
-
Added the ability to cache histogram results during optimization to reduce the work performed by the histograms.
-
Added the ability to backup a database to an HTTPS S3 target with an unverified SSL certificate when using the option:
verify_
.ssl: false
2023-03-06 Version 8. 0. 13
-
Fixed an issue with column type checking on base and recursive case of a recursive common table expression.
-
Fixed an issue that may cause a "Table doesn't exist" error when a multi-insert contains expressions and the target table has a computed column as its shard key.
-
Expanded existing Unicode characters to support Private Use Area (PUA) code points.
Including one in the Basic Multilingual Plane (U+E000–U+F8FF) and one in each plane 15 and 16 (U+F0000–U+FFFFD, U+100000–U+10FFFD). -
Fixed a crash that could occur when a computed column definition refers to a table name.
-
Increased default blob cache size on hosts with less than 200GB of total disk space.
-
Added the ability to set the
maximum_
global variable for workspaces.blob_ cache_ size_ percent -
Fixed an issue with promote lock timeout errors that may occur during a rebalance due to a heavy ingest workload, which causes the merger to be slow to pause.
-
Introduced a new global variable
subprocess_
, which is used for retrying on retry-able connection failures during select into/backup queries for S3 and GCS.max_ retries -
New feature:
ORDER BY SELF JOIN
, creates a self join onORDER BY LIMIT
queries to take advantage of differences in bandwidth. -
Fixed an issue with the schema registry so only superusers can see redacted pipeline metadata such as credentials and URLs.
2023-02-27 Version 8. 0. 12
2023-02-21 Version 8. 0. 11
-
Fixed an issue that occurred when the
MATCH_
argument of thePARAM_ <type> JSON_
function was not in a predicate expression.MATCH_ ANY -
Improved the performance of the
JSON_
function over columnstore tables.MATCH_ ANY_ EXISTS -
Fixed a profiling issue specific to non-collocated hash joins where the memory usage and disk spilling are missing under the join operators.
2023-02-13 Version 8. 0. 10
-
Fixed an issue where the database engine locks up on certain out-of-memory errors.
-
Fixed an issue where the audit logs now show the original user of a query forwarded to the master aggregator instead of the internal distributed user.
-
Fixed a parsing issue for queries containing multi-line comments near
GROUP BY
orORDER BY
clauses. -
The
num_
engine variable is now settable on Cloud.background_ merger_ threads -
The
ORDER BY ALL [DESC|ASC]
(orORDER BY *
) syntax is now supported. -
The
GROUP BY ALL [DESC|ASC]
(orGROUP BY *
) syntax is now supported. -
Improved the query execution performance of JSON columns under a higher level of parallelism.
-
Expanded support for encoded
GROUP BY
query shapes containing expressions in aggregates. -
Added support for incremental backups to blob stores where a single partition contains more than 5 TB of data.
2023-02-06 Version 8. 0. 9
-
Added the
REVERSE()
built-in string function that reverses the target string. -
Added the
DATETIME_
column to bothPRECISION PARAMETER
andROUTINES
information_schema views. Also, the DATETIME_
column will includePRECISION TIME
andTIMESTAMP
data types in theCOLUMNS
information_schema view. -
Fixed an issue causing incorrect trace messages in master logs where clocks were incorrectly advancing from "0".
-
Added a new information_
schema view named LMV_
.LOCAL_ DATABASES This view shows the state of local databases like SHOW DATABASES EXTENDED
, but it can be queried against unlike show commands. -
Improved the code generation performance of tables with a large number of indexes.
-
Added the
/api/v2/jwks_
endpoint to Data API to allow users to enable JWT Auth in Data API on Cloud.setup See jwks_ setup for more information. -
Sampling will no longer be used for table size estimation when statistics are present.
-
Fixed an issue where extra CPU was used when a read-only database is attached to a workspace without any writable mount for the read-only database.
-
The
spilling_
engine variable can now be set at startup.minimal_ disk_ space
2023-01-30 Version 8. 0. 8
-
Fixed an issue with the master aggregator leaking memory while performing a background task.
-
Fixed the case where the
REGEXP_
andREPLACE REGEXP_
expressions can produce non-utf8 strings by introducing the new engine variableSUBSTR regexp_
.output_ validation_ mode Regular expression built-ins can produce non-utf8 strings because they don't have full support for multi-byte characters. The engine variable controls this behavior if regular expression built-ins return strings that are invalid under its collation settings. -
Improved the performance on columnstore scans that perform multiple JSON extraction operations on the same JSON column.
2023-01-24 Version 8. 0. 7
-
Added a new
OPTIMIZE TABLE <table_
command for columnstore tables.name> INDEX; This command runs the optimization routine for columnstore secondary indexes manually. -
Fixed an issue where recursive CTEs could fail to execute on upgrade to 8.
0 if materialized CTEs were disabled. -
Added the
ignore_
system variable, which allows foreign key syntax inforeign_ keys CREATE TABLE
commands, but completely ignores the key (it will not show up in metadata). -
Allow modifying the
json_
engine variable as long as a computed column that modifies the shard key does not contain a call toextract_ string_ collation JSON_
.EXTRACT_ STRING -
Added a new option,
SERVER_
, to theV2 json_
engine variable.extract_ string_ collation This new, recommended option is the default for new clusters, and allows comparison of utf8mb4 strings extracted from JSON to utf8 string constants. Existing clusters will retain their original setting upon upgrade. -
Fixed an issue with databases becoming unrecoverable when upgrading to version 8.
0 if any tables contained shard keys using computed columns that call JSON_
.EXTRACT_ STRING -
Added the option to authenticate Data API requests using JWT.
-
Added the
skip_
engine variable, which controls when segment elimination will not use an IN list that is too large (default 1000 elements).segelim_ with_ inlist_ threshold
2023-01-17 Version 8. 0. 6
-
Fixed a performance regression when running
SET <system variable> = <expression>
commands.These commands are often run by client drivers on new connections. -
Improved the performance of various commands (
SHOW
commands, DDL, etc.) when there are very many views or tables in the database (100s of thousands). -
Added
CREATE_
andTIME ALTER_
columns to information_TIME schema. pipelines. CREATE_
shows the date/time a pipeline was created or recreated.TIME ALTER_
shows the date/time a pipeline was altered via anTIME ALTER PIPELINE
statement. -
Fixed an issue introduced in version 8.
0. 4 where SHOW TABLE STATUS
was incorrectly displaying views. -
Added a new global variable,
num_
, which controls the number of background merger threads to start for each node.background_ merger_ threads -
information_
now correctly shows information about global temporary tables.schema. table_ statistics
2023-01-11 Version 8. 0. 5
-
Added support to
PROFILE
for hash join spilling. -
Fixed an upgrade issue where a database that was originally created on SingleStore 6.
8 or earlier and was then upgraded to 7. 3 is then REPLICATED to SingleStore version 7. 8 could result in broken shard keys. -
Added support for Recursive CTEs in cases where a Recursive CTE has dependency on a streaming result table outside of its dependency cycle.
-
Fixed an issue with Recursive CTEs where one Recursive CTE refers to another Recursive CTE and that second CTE would only read the rows from the first CTE’s final iteration.
-
The
SHOW STATUS EXTENDED
command contains a new "Gv_
" key whose value is the current logical clock of the server.clock -
The
SHOW DATABASE STATUS
command contains a new "gv_
" key whose value is the current logical clock of the server.clock -
Fixed an issue with aggregate functions using incorrect enum/set types that may result in inaccurate output in the operator tree.
-
Fixed an edge case issue which could cause the engine to hang during shutdown.
-
Improved performance of comparing utf8mb4 strings.
-
Added a new information schema view
internal_
which shows memory use of SingleStore internal metadata tables.table_ statistics The columns displayed are the same as those shown for table_
.statistics -
Fixed an edge case issue that could cause
ADD AGGREGATOR
to fail. -
Reduced the memory used by
ANALYZE
queries by splitting approx count queries to only query a single JSON column at a time. -
Improved the accuracy of
network_
intime PROFILE
output for some query shapes. -
The blob cache is now allowed to use more disk space by default on larger local disks.
It will now use up to 90% of local disk space on disks over 2 TB in size instead of 75%. -
Added a new global variable,
maximum_
, which can set the blob cache size as a value from 0 to 1 that is percentage of local disk the blob cache is allowed to use.blob_ cache_ size_ percent The default value is 0. -
Added a new global variable,
num_
, which controls the number of background merger threads to start for each node.background_ merger_ threads The default value is 2. -
Fixed a MySQL protocol incompatibility where SingleStore was not properly sending back the SERVER_
STATUS_ IN_ TRANS flag. This was impacting some MySQL php drivers.
Last modified: December 4, 2024