Resolved Issues

Executing a SQL query with more than 50 JOIN operations could incorrectly report, "java.sql.SQLException: Memory exhausted". (14405)
The issue has been resolved.

In rare cases, during indexing, the Storage Managers (SMs) and Transaction Engines (TEs) could shut down unexpectedly reporting, "FAILED: !index.isArchive || NODE_STATE_SYNCING == index.thisNode→nodeState". (14537)
The issue has been resolved.

SQL queries with INNER JOINS and OUTER JOINS could take longer to execute. (14468, 14435)
The issue has been resolved.

Inserting a row into a very large table containing hundreds of millions of rows, with a large number of record atoms with free space, could cause the TE to shut down unexpectedly with, "listener thread taking longer than XX milliseconds to apply YY message". (14439, 14454, 14458, 14463, 14453, 14514)
The issue has been resolved.

SQL insert operations into a table with a non-unique Merge Tree index could be blocked indefinitely. (14145, 14307, 14314)
The issue has been resolved.

Executing the EXPLAIN (ANALYZE_GRAPH on) query on a SQL statement that included a LEFT OUTER JOIN, RIGHT OUTER JOIN, or FULL OUTER JOIN could report, "Error 58000: op type N4Exec18RightHashOuterJoinE is not supported by execution tree walker". (14423)
The issue has been resolved.

A SQL query that included a parameterized limit could take longer to execute. (14320)
The issue has been resolved.

The execution of nuodump returned SQL statements with improper formatting. (14155)
The issue has been resolved.

When pip install 'pynuoadmin[completion]' was used to install the pynuoadmin package, a nuocmd command could report "Cannot locate NuoDB: please set the NUODB_HOME environment variable." (14287)
The issue has been resolved.

A SQL SELECT query with a LEFT OUTER JOIN could take longer to execute when using the Merge Tree indexing compared to the B Tree indexing. (14265)
The issue has been resolved.

Execution of a JOIN operation on byte type attributes of different lengths could report, "Unsupported cast from bytes(n) to bytes."
The issue has been resolved.

If a query includes null predicates (IS [NOT] NULL), an OUTER join could incorrectly be written as an INNER join, causing inaccurate results.
The issue has been resolved.

A SQL comparison operation between two numeric values using < or >, where the first value has more decimal places than the second, could return incorrect results.
The issue has been resolved.

Executing a SQL query with a correlated subquery that references columns from the outer query in the SELECT list could report, "Error 58000: Internal error: failed precondition resolution."
The issue has been resolved.

Executing a SQL query containing an outer query that groups the results of a subquery returning multiple rows of NULL values could report, "Error 58000: unknown function type: 39`".
The issue has been resolved.

Executing a SQL query containing an existential subquery that queries a table function could report, "failed precondition projection().selectionVectorId() == _producers[_projectingProducer]→projection().selectionVectorId()".
The issue has been resolved.

Executing a SQL query that references a table that does not exist in the schema could result in the log message, "table 'XXX' does not exist" appearing multiple times.
The issue has been resolved.

Executing a SQL query on a partitioned table using Merge Tree indexes could report inaccurate results.
The issue has been resolved.

Execution of a SQL query that contains a GROUP BY operation on numerics of different scales could return inaccurate results.
The issue has been resolved.

Executing SQL queries that include sorting binary values in descending order, specifically zero values, with different byte lengths could return inaccurate results.
The issue has been resolved.

When executing ALTER DATABASE RUN GARBAGE COLLECTION, the command did not wait for the garbage collection process to complete.
The issue has been resolved.

Case sensitivity comparisons between CLOB (and TEXT) data types were not performed, regardless of their collation settings.
The issue has been resolved.

Execution of the EXPLAIN SQL command could return results containing extra empty spaces.
The issue has been resolved.

SQL queries involving inverted Merge Tree indexes with a large number of index components stored at higher levels than lower, could cause a TE and a SM to shut down with an Out-of-Memory (OOM) error.
The issue has been resolved.

When a SELECT FOR UPDATE SKIP LOCKED statement was executed on a locked table, the statement could wait for an extended period until the lock was released.
The issue has been resolved.

The peak amount of memory allocated during the execution of the statement reported by the PEAKMEMUSAGE field in the LASTSTATEMENT system table could be inaccurate.
The issue has been resolved.

When executing a query using nuosql from stdin, if the query contains a multi-line string, line breaks will be ignored.
The issue has been resolved.

When using nuosql, executing a query that includes a backslash literal (\) within a quoted string could report, "unrecognized character error".
The issue has been resolved.

When using nuodump, extracting DML statements that include quotes nested inside a quoted string could return inaccurate results.
The issue has been resolved.

When using nuodump, primary keys with user-specified names were not logged accurately.
The issue has been resolved.

Execution of the nuoarchive check --rewrite command could rewrite older atoms to the default version of nuoarchive rather than the effective version.
The issue has been resolved.

In rare instances, when an SM was shut down immediately after starting, the database could not be restarted and the SM remained in the UNKNOWN state indefinitely.
The issue has been resolved.

In rare cases, a CREATE TABLE statement could block another CREATE TABLE statement.
The issue has been resolved.

In a Kubernetes deployment, starting a process before Kubernetes populated the running pod state could result in "KubernetesResourceInspector Unable to find authoritative TE\SM process for dbName=xxx".
This issue has been resolved.

In Kubernetes deployments with multiple databases, scaling down to zero SM replicas could lead to inaccurate counting of database archives. This could result in logging error messages when attempting to remove the final archive for a database.
The issue has been resolved.

When using Java drivers, the generated keys from a statement or execution could be requested even after they had been invalidated.
The issue has been resolved.

When a server was configured to use IPv6 instead of IPv4 and requireLocalDomainUser was set to true in nuoadmin.conf, the unrestricted domain user specified by the nuoadmin.conf property domainUser did not have connect access despite being on the same host as the Admin Process (AP).
The issue has been resolved.

If an SM started on a new archive was shut down before initializing the archive, restarting the SM may report, "Location xx is not a valid file archive".
The issue has been resolved.

In rare cases, after an archive syncing process, a specific sequence of events could cause slow query performance due to long queues for atom reloads on a SM. (13083, 13700, 13757, 13950, 13993, 14131, 14190, 14299, 14303, 14334, 14342, 14347, 14385, 14390, 14394, 14444)
The issue has been resolved.

If the database protocol was not upgraded to at least version 6.0, migration of data from File archives to Log-Structured Archives (LSA) could cause the SMs to shut down unexpectedly. (14254, 14368)
The issue has been resolved.

Logging the execution plan of a running SQL query could cause the TE that executed the query to shut down unexpectedly if the client process was terminated abruptly. (14381, 14403)
The issue has been resolved.

When the ALTER TABLE REBUILD INDEXES USING MERGE TREE SQL command was used, the SM could shut down unexpectedly with "ASSERT: FAILED:thisObj.isComplete() || thisObj.isPurged()". (14296, 14297, 14298)
The issue has been resolved.

In rare cases, a SQL query with an ORDER BY clause on an indexed column may not execute. (14159)
The issue has been resolved.

In a Kubernetes deployment, in rare cases, especially if rapidly deleting and recreating a database with the same name, a database would not start because the NuoDB Kubernetes Aware Admin (KAA) became out of sync with the actual Kubernetes state due to rapid removal and recreation of archive objects.
The issue has been resolved.

In rare cases, a SQL request to lock data could run indefinitely because the chairman could not correctly ignore stale pending lock versions.
The issue has been resolved.

A SQL query that included a JOIN operation performed on columns of different data types could report, " failed: Internal error: failed precondition vectorDesc.dataTypeDesc(). ".
The issue has been resolved.

In some cases, a SQL query that included window functions in JOIN conditions could not execute and reported an error.
The issue has been resolved.