TigerGraph DB Release Notes

TigerGraph Server 4.2.0 Preview was released on April 3, 2025.

TigerGraph Server 4.2.0 Alpha was released on March 4, 2025.

TigerGraph 4.2’s feature set is an enhancement of what was available in 4.1.2. Therefore, features that were in 4.1.2 are not considered New Features.

Key New Features

Detailed List of New and Modified Features

System Management Enhancements

Security and Access Control Enhancements

Integration Enhancements

  • Writing query output to an S3 object can now be configured at the user session level instead at the system administration level, for better alignment of roles and privileges.

  • Updated Kafka from 2.5.1 to 3.6.2. Updated Zookeeper from 3.6.3 to 3.8.4.

API Enhancements

Query Language Enhancements

Loading Enhancemnts

Performance Improvements

GraphStudio, Admin Portal, and Insights

Fixed issues

Fixed and Improved in 4.2.0

Functionality

  • 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).

  • Added the 'graph' field to CDC messages generated by the TigerGraph CDC service (CORE-4147).

  • 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 support for debug mode when a pod restart fails due to a PostStartHookError (TP-7228).

  • 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).

Improvements

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

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

Compatibility Issues

Description Version Introduced

To apply a File Input Policy or File Output Policy change, now both gsql and restpp servers must be restarted: gadmin restart gsql restpp -y

v4.2.0

The --incremental option for backup now performs a true incremental backup instead of a differential backup.

v4.2.0

In CDC messages, the format of tuple values has changed.

v4.2.0

SelectVertex() may not be used with a relative filepath but previously this was not enforced. It is now enforced.

v4.2.0

The 'graph' field is now included in CDC messages generated by the TigerGraph CDC service.

v3.11.0, v4.1.1

In CDC messages, the format of map values has changed.

v3.11.0, v4.1.1

A full export package now includes access policies and template queries.

v4.1.0

Users could encounter file input/output policy violations when upgrading a TigerGraph version. See Input policy backward compatibility.

v3.10.0

When a PRINT argument is an expression, the output uses the expression as the key (label) for that output value. To better support Antlr processing, PRINT now removes any spaces from that key. For example, count(DISTINCT @@ids) becomes count(DISTINCT@@ids).

v3.9.3+

Betweenness Centrality algorithm: reverse_edge_type (STRING) parameter changed to reverse_edge_type_set (SET<STRING>), to be consistent with edge_type_set and similar algorithms.

v3.9.2+

For vertices with string-type primary IDs, vertices whose ID is an empty string will now be rejected.

v3.9.2+

The default mode for the Kafka Connector changed from EOF="false" to EOF="true".

v3.9.2+

The default retention time for two monitoring services Informant.RetentionPeriodDays and TS3.RetentionPeriodDays has reduced from 30 to 7 days.

v3.9.2+

The filter for /informant/metrics/get/cpu-memory now accepts a list of ServiceDescriptors instead of a single ServiceDescriptor.

v3.9.2+

Some user-defined functions (UDFs) may no longer be accepted due to increased security screening.

  • UDFs may no longer be called to_string(). This is now a built-in GSQL function.

  • UDF names may no longer use the tg_ prefix. Any user-defined function that began with tg_ must be renamed or removed in ExprFunctions.hpp.

v3.9+

Deprecations

Description Deprecated Removed

The --meta option for backup is no longer needed because metadata is now included automatically with backup files.

3.9.2

4.2.0

Streaming connector for external Kafka (3.6 to 3.9.2 version)

3.9.3

4.2.0

The format for tuple structures in CDC messages will change in a future version. The future format is likely to be similar to the new format for maps.

4.1.1

4.2

Release notes for previous versions