TigerGraph DB Release Notes

Fixed missing error message when running a non-procedural GSQL query containing syntax errors at the end (GLE-10295).

Eliminated false REST-10015 error message when upserting a single vertex using the gsql-atomic-level:atomic flag via REST API (GLE-10680).

Fixed a GPE crash caused by removing a cluster node or when a Disaster Recovery cluster has fewer replicas than the primary cluster (CORE-4967).

Fixed the MaxFlow algorithm to return correct results, consistent with documented examples (GLE-10737).

Fixed a UDF parsing error that failed to detect user-defined function names which conflict with built-in functions (GLE-10326).

Fixed an issue where the system would throw a NullPointerException and fail to create or install a query during code validation (GLE-10501).

Fixed an issue where authentication was skipped when replaying requests in a Disaster Recovery cluster (GLE-10702).

Improved the upgrade process by performing query and token bank compilation checks during pre‑upgrade instead of post-upgrade (GLE‑9459).

Fixed GSQL startup failures during upgrade caused by errors while verifying dictionary and UDF files (GLE-11224).

Fixed: If an interpreted non-procedural query contained an error but the text prior to the error was valid, the partial query would run and ignore the error (GLE-10295).

Fixed an issue that could cause false negatives or false positives during license checks caused by an underflow in the vertex count reporting (CORE-5117).

Reduced disk usage by removing on-disk indexes in cloud mode and deleting main files in both cloud and on-prem deployments (CORE-4930).

Enhanced security for namespace-scoped TigerGraph Operator installations by separating the necessary cluster roles and namespace roles (TP-7024).

Improved upgrade logs with a clearer message: Installation of new TigerGraph version (TP-8249).

Improved the Rolling Upgrade documentation to explain how queries behave during upgrades, how retries are handled, and how to tune timeout settings, so users can plan smoother upgrades.

Improved the Vector Search documentation to detail known limitations, including unsupported ListAccum patterns, use of the ListAccum operator, and WHERE clause restrictions.

Added support for configuring file permissions when exporting query results with PRINT TO_CSV, instead of using hardcoded defaults (GLE-11322).

Eliminated a security vulnerability that allowed AWS credentials to be read in plain text using the gadmin config get command. These values are now masked (TP-8285).

Fixed unauthorized exposure of graph name and creator information via the /auth/simple and /internal/info APIs (GLE-10746).

Eliminated the potential exposure of personally identifiable information (PII) in loading job summary files by replacing detailed data with line numbers for invalid entries (TP-8575).

Eliminated potential exposure of personally identifiable information (PII) in error messages when a loading job semantic check failed during creation (GLE-11125).

Addressed multiple upstream and OS-level security vulnerabilities through package upgrades and dependency patching. Fixed the following security vulnerabilities:

Fixed issue where the loading job status was incorrectly cleaned up in advance due to an inaccurate loading job counter (TP-4741).

Fixed issue where the loader would fail silently, and now it reports an error directly if the loader fails to start (TP-6420).

Fixed issue where loading an empty file triggered a failure loop (TP-6530).

Fixed issue with audit error codes being logged when a CDC message fails to deliver to external Kafka (CORE-4249).

Fixed critical disk issue caused by the rebuilder getting stuck in a partitioned cluster after dropping vertex or edge attributes (CORE-4303).

Fixed issue where CDC EDGE messages with "UNKNOWN" ID were not removed when a query deleted a vertex and edge simultaneously (CORE-4457).

Fixed issue where the primary ID was missing when inserting a vertex implicitly from loading an edge in a single-partition cluster and the target vertex used "primary_id_as_attribute=true" (GLE-7562).

Fixed issue with running the TigerGraph command gcollect on Kubernetes (TP-6353).

Added namespace as a suffix of the HostName in HostList on Kubernetes (TP-6214).

Fixed query compilation errors when iterating over FOREACH to retrieve an accum type attribute with the -single or distributed keyword; ensured operations between two different GroupByAccums hold the same data types and field names (GLE-8507).

Fixed issue with double quotes in literal strings during the creation of a loading job (GLE-8630).

Fixed the inability to fetch dynamic file output policy during query execution (GLE-4847).

Fixed issue where sensitive information was not removed from the browser localStorage, ensuring better security (APPS-1066)

Fixed a query installation failure for single-node queries that initialize vertex set variables in conditional branches, such as if-else or case-when statements (GLE-7369).

Added a button to refetch real-time graph statistics on the Load Data page in GraphStudio (APPS-2565).

Added the standard Triangle Counting Algorithm to the built-in query list on the Write Query page in GraphStudio (APPS-3429).

Fixed the issue where query creation failed with a "query not found" prompt in GraphStudio (APPS-3624).

Removed the requirement to restart the GSQL service after modifying the SSO settings in Admin Portal (APPS-3167).

Allowed aborting a query in GraphStudio (APPS-3487).

Checked that the buffer length is non-negative before reading a file (TP-6690).

Fixed the issue where unauthorized users could access sensitive data, including superuser info, via the /gsql/v1/users API endpoint (GLE-8290).

Fixed NoSuchElementException thrown when removing all authentication tokens (GLE-8937).

Fixed issue with data source creation failing to sync to Disaster Recovery (DR) due to complex payload handling (GLE-9617).

Fixed bug with the to_vertex_set function (GLE-8083).

Unblocked the usage of the keyword “function” as a vertex/edge/attribute name (GLE-9803).

Fixed the backup restoration issue where GSQL was in a warmup state when importing GSQL data (TP-6949).

Fixed the metrics issue where tigergraph_cpu_usage exceeded 100 and tigergraph_cpu_available was negative under high load (TP-7127).

Fixed issue where failed backups in corner cases caused the Engine to pause for an extended period, leading to subsequent query timeouts (CORE-4532).

Resolved the issue with downloading GSQL output files larger than 3GB in AdminPortal (APPS-3271).

Fixed an issue where the GSQL-TIMEOUT header was not being forwarded in the /api/graphql/gsql endpoint (APPS-3648).

Fixed a bug where local accumulators defined across multiple lines in a query were misinterpreted as a file in the GSQL client (GLE-8261).

Allowed the globaldesigner role to monitor queries in Admin Portal (APPS-3172).

Improved performance of GSQL queries containing DELETE statements intended for deleting all vertices of a given type (GLE-8328).

Added support for debug mode when a pod restart fails due to a PostStartHookError (TP-7228).

Corrected the logic for the SelectVertex() function so it throws an error if the filePath is not an absolute path.

Fixed the following security vulnerabilities: CVE-2023-45288, CVE-2024-24790, CVE-2024-34156, and CVE-2024-45337.