---
title: "TigerGraph DB Release Notes"
description: "Release notes for TigerGraph 4.2"
component: "tigergraph-server"
version: "4.2"
module: "release-notes"
html_url: "/tigergraph-server/4.2/release-notes/"
canonical_url: "https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/"
markdown_url: "https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md"
---

[View as HTML](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/)

# TigerGraph DB Release Notes

Table of Contents

* [Key New Features](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_key_new_features)
* [Detailed List of New and Modified Features](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_detailed_list_of_new_and_modified_features)  
   * [System Management Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_system_management_enhancements)  
   * [Security and Access Control Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_security_and_access_control_enhancements)  
   * [Output to Cloud Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_output_to_cloud_enhancements)  
   * [API Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_api_enhancements)  
   * [Query Language Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_query_language_enhancements)  
   * [Data Streaming/Connector Enhancements](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_data_streamingconnector_enhancements)  
   * [Performance Improvements](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_performance_improvements)  
   * [GraphStudio, Admin Portal, and Insights](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_graphstudio_admin_portal_and_insights)
* [Fixed issues](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_fixed_issues)  
   * [Fixed and Improved in 4.2.6](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_fixed_and_improved_in_4_2_6)  
   * [Fixed and Improved in 4.2.5](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_fixed_and_improved_in_4_2_5)  
   * [Fixed and Improved in 4.2.4](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_fixed_and_improved_in_4_2_4)  
   * [Fixed and Improved in 4.2.3](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_fixed_and_improved_in_4_2_3)  
   * [Fixed and Improved in 4.2.2](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_fixed_and_improved_in_4_2_2)  
   * [Fixed and Improved in 4.2.1](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_fixed_and_improved_in_4_2_1)  
   * [Fixed and Improved in 4.2.0](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_fixed_and_improved_in_4_2_0)
* [Known Issues and Limitations](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_known_issues_and_limitations)  
   * [Compatibility Issues](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_compatibility_issues)  
   * [Deprecations and Removals](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_deprecations_and_removals)
* [Release notes for previous versions](https://www.tigergraph.com/docs/tigergraph-server/4.2/release-notes/index.md#_release_notes_for_previous_versions)

[TigerGraph Server 4.2.6](https://dl.tigergraph.com/?tab=enterprise) LTS was released on November 11, 2026.

[TigerGraph Server 4.2.5](https://dl.tigergraph.com/?tab=enterprise) LTS was released on September 2, 2026.

[TigerGraph Server 4.2.4](https://dl.tigergraph.com/?tab=enterprise) LTS was released on July 20, 2026.

[TigerGraph Server 4.2.3](https://dl.tigergraph.com/?tab=enterprise) LTS was released on June 5, 2026.

[TigerGraph Server 4.2.2](https://dl.tigergraph.com/?tab=enterprise) LTS was released on September 30, 2025.

[TigerGraph Server 4.2.1](https://dl.tigergraph.com/?tab=enterprise) LTS was released on September 5, 2025.

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

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

> [!NOTE]
> 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

* **[Hybrid Vector Search](https://www.tigergraph.com/docs/gsql-ref/4.2/vector/index.md)**: Scalable storage and similarity search for vector attributes associated with vertices.  
   * New `VECTOR` attribute data type with real-time updates  
   * Fast approximate nearest neighborhood (ANN), with automatic indexing, incremental indexing  
   * hybrid graph + vector search in GSQL
* **[Incremental Backup](https://www.tigergraph.com/docs/tigergraph-server/4.2/backup-and-restore/incremental-backup.md)** which efficiently backs up only what has changed since the last backup/restore event.
* **[Rolling Upgrades of maintenance versions](https://www.tigergraph.com/docs/tigergraph-server/4.2/installation/upgrade.md#_rolling_upgrade)** for HA clusters (Preview).
* **[GQL/OpenCypher path pattern syntax](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/select-statement/index.md#_from_clause)**, within GSQL syntax
* **Run ad hoc queries directly** ([non-procedural interpreted queries](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/query-modes.md))
* **[Community Edition of TigerGraph Database](https://www.tigergraph.com/docs/tigergraph-server/4.2/intro/comparison-of-editions.md)**:  
   * Up to 200GB graph data + 100GB vector data, single server only  
   * Some enterprise features not included. Community support only  
   * See the full [comparison of editions](https://www.tigergraph.com/docs/tigergraph-server/4.2/intro/comparison-of-editions.md).  
   * \[4.2.1\] [Combined graph and vector data size](https://www.tigergraph.com/docs/tigergraph-server/4.2/intro/comparison-of-editions.md#_database_features) limit for Community Edition, allowing flexible allocation of up to 300 GB for graph and vector storage.

## Detailed List of New and Modified Features

### System Management Enhancements

* **[Incremental Backup](https://www.tigergraph.com/docs/tigergraph-server/4.2/backup-and-restore/incremental-backup.md)** which efficiently backs up only what has changed since the last backup/restore event.
* **[Rolling Upgrades of maintenance versions](https://www.tigergraph.com/docs/tigergraph-server/4.2/installation/upgrade.md#_rolling_upgrade)** for HA clusters (Preview).
* **[Restore option \--keepusers](https://www.tigergraph.com/docs/tigergraph-server/4.2/backup-and-restore/restore-backup-same.md#_options_for_restore)** to keep the database users in the current database, not the ones from the backup file.
* **Backup to [Azure](https://www.tigergraph.com/docs/tigergraph-server/4.2/backup-and-restore/configurations.md#_backup_to_abs_azure_blob_storage) and [GCP](https://www.tigergraph.com/docs/tigergraph-server/4.2/backup-and-restore/configurations.md#_backup_to_gcs_google_cloud_storage) cloud storage**, analogous to existing support for backup to AWS S3.
* **More graceful [user-initiated shutdown](https://www.tigergraph.com/docs/tigergraph-server/4.2/system-management/manage-services.md#_graceful_shutdown_of_restpp)** of RESTPP and GPE services.
* **Backup HA Enhancement**: backup can still work even if a node is down or a region is down.
[Kubernetes Operator update to v1.5.0](https://github.com/tigergraph/ecosys/blob/master/k8s/README.md) with numerous new features 

* CRR replication, Auto cluster monitoring during creation, upgrade pre-check support, rolling upgrades, backoff delay for job retries to improve resilience

* **[gadmin status -v](https://www.tigergraph.com/docs/tigergraph-server/4.2/system-management/management-commands.md#_gadmin_status)** now displays Role information, with support for GPE, GSE, and GSQL.
* After applying a new license key, dependent services (GSE and GSQL) are automatically restarted.
* \[4.2.1\] **[New ZK.SnapCount configuration](https://www.tigergraph.com/docs/tigergraph-server/4.2/reference/configuration-parameters.md#_zk)** enables users to fine-tune the number of committed ZooKeeper transactions that trigger a snapshot, enhancing memory management and stability under high transaction loads.
* \[4.2.3\] Added support for **[Amazon Linux 2023](../installation/hw-and-sw-requirements#%5Fcertified%5Foperating%5Fsystems )** and **[Ubuntu 24.04](../installation/hw-and-sw-requirements#%5Fcertified%5Foperating%5Fsystems )**.  
* Installation on Ubuntu 24.04 and later requires the `binutils` package.
* \[4.2.3\] Increased the default maximum HTTP request header size from 20 KB to 64 KB to better support large request headers (such as LDAP/SSO scenarios), and introduced a new configuration parameter `GSQL.MaxHttpRequestHeaderSizeKB`.  
* You can use [GSQL.MaxHttpRequestHeaderSizeKB](https://www.tigergraph.com/docs/tigergraph-server/4.2/reference/configuration-parameters.md#_gsql) to customize the maximum HTTP request header size.  
* When set to `0` (default), the system uses the default value of 64 KB.  
* Requests exceeding the configured limit now return HTTP status `431 Request Header Fields Too Large` instead of `400 Bad Request`.
* \[4.2.3\] Upgraded embedded NGINX to version 1.28.2 for upstream security and reliability fixes.
* \[4.2.3\] **[Query installation logs](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/run-manage-queries.md#_log_output)** now include a completion summary, elapsed time, and a failure report listing any skipped or failed queries. These logs are also shown during a TigerGraph upgrade.
* \[4.2.4\] Upgraded embedded NGINX to version 1.30.2 for upstream security and reliability fixes.
* \[4.2.5\] Upgraded embedded NGINX to version 1.30.4 for upstream security and reliability fixes.

### Security and Access Control Enhancements

* **[JWT authentication](https://www.tigergraph.com/docs/tigergraph-server/4.2/user-access/jwt-token.md#_user_guide_overview) for all REST endpoints**, including GSQL endpoints.
* **New [built-in role](https://www.tigergraph.com/docs/tigergraph-server/4.2/user-access/access-control-model.md#_built_in_roles): globalobserver**, used in Savanna, for minimal privileges: `READ_SCHEMA` and `READ_LOADINGJOB`.
* **Two new [access privileges](https://www.tigergraph.com/docs/tigergraph-server/4.2/user-access/rbac-row-policy/row-policy-privileges-table.md): READ\_LOG and APP\_ACCESS\_LOG** to grant read-only access to log files. `APP_ACCESS_LOG` is specifically designed for [access from GraphStudio or Savanna](https://www.tigergraph.com/docs/gui/4.2/admin-portal/monitoring/log-viewer.md#_privilges).
* \[4.2.1\] Added the `Security.JWT.JWKS.URL` **[configuration parameter](https://www.tigergraph.com/docs/tigergraph-server/4.2/user-access/jwt-token.md#_setup_jwt_token_gadmin_configuration)**, to allow JWT certificates to be fetched using the Key ID (kid) from a JWKS (JSON Web Key Set) URL.
* \[4.2.1\] [ACL privilege migrations](https://www.tigergraph.com/docs/tigergraph-server/4.2/user-access/query-privilege-migration.md#_migrate_acl_privileges) are prevented if the the ACL catalog contains the query contents.
* \[4.2.3\] Added support for configuring **[default READ and EXECUTE roles](https://www.tigergraph.com/docs/tigergraph-server/4.2/user-access/fine-grained-query-privileges.md#_default_roles_for_query_level_privileges)** at the graph level for query privileges.
* \[4.2.3\] Added graph-level **[READ\_DATA](https://www.tigergraph.com/docs/tigergraph-server/4.2/API/built-in-endpoints.md#_abort_a_query)** privilege requirement for the `/query_result` and `/query_status` endpoints.
* \[4.2.3\] [SAML SSO](https://www.tigergraph.com/docs/gui/4.2/admin-portal/security/sso.md#_x509_certificate_and_private_key) now supports full X.509 certificate chains for both Service Provider (SP) and Identity Provider (IdP) certificates. Certificate chains can include server, intermediate, and root certificates in a single uploaded file.
* \[4.2.3\] Nginx now supports TLS 1.3 hybrid [post-quantum key exchange](https://www.tigergraph.com/docs/tigergraph-server/4.2/security/encrypting-connections.md#_post_quantum_hybrid_tls_key_exchange) (`X25519MLKEM768`) through the bundled OpenSSL 3.5\. This support is enabled by default when SSL is enabled.
* \[4.2.4\] Added the `Security.JWT.UserClaim` **[configuration parameter](https://www.tigergraph.com/docs/tigergraph-server/4.2/user-access/jwt-token.md#_optional_configurations)** to specify which JWT claim resolves the TigerGraph username during JWT/OIDC authentication.
* \[4.2.6\] Added the `ProxyUserPermissionMerge` **[environment variable](https://www.tigergraph.com/docs/tigergraph-server/4.2/user-access/ldap.md#_merge_local_user_privileges_into_proxy_users)** for RESTPP. When set to `true`, an existing proxy user also receives the privileges of the local user with the same name, and no new proxy user is created for that user. By default, a proxy user holds only the privileges granted to it directly.

### Output to Cloud Enhancements

* **[Writing query output to an S3 object](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/data-types.md#_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.
* \[4.2.1\] Writing **[query output](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/write-output-to-cloud.md)** to S3-compatible storage (such as Ceph, MinIO, and Wasabi) is now supported using a configurable `s3_endpoint`, enabling integration with non-AWS storage systems.
* \[4.2.3\] Added support for specifying the S3 region using the **[s3\_region](https://www.tigergraph.com/docs/savanna/main/graph-development/advanced-features/write2-s3.md)** session parameter when writing **[query output](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/write-output-to-cloud.md)** to S3-compatible storage.

### API Enhancements

* **New endpoints to [fetch schema information and sample data from Snowflake](https://www.tigergraph.com/docs/tigergraph-server/4.2/API/gsql-endpoints.md#_get_schema_information_from_a_snowflake_data_source)**.
* Added a **REST endpoint to [delete user-defined function files](https://www.tigergraph.com/docs/tigergraph-server/4.2/API/gsql-endpoints.md#_delete_udt_files)**.
* The **Interpret Query endpoint `POST /gsql/v1/queries/interpret`** can now be used with queries that have a [datetime parameter](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/run-manage-queries.md#_complex_type_parameter_passing).
* The **Edge Upsert endpoint** now supports [upserting the multiple edges of a discriminated edge](https://www.tigergraph.com/docs/tigergraph-server/4.2/API/upsert-rest.md#_upserting_multi_edges_with_discriminators) in a single API request.
* \[4.2.1\] **[RESTPP endpoints /query\_status, /query\_result, /showprocesslist/{graph\_name}, and /showprocesslistall](https://www.tigergraph.com/docs/tigergraph-server/4.2/API/built-in-endpoints.md)** now report query status and results across all server nodes in a distributed cluster, not just the node receiving the request. Use the optional `disallow_redirect` parameter to query only the local node, if desired.
* \[4.2.3\] Added a **[new Informant endpoint](https://www.tigergraph.com/docs/tigergraph-server/4.2/API/built-in-endpoints.md#_get_license_info_and_usage)** `GET /informant/licenseinfo` to retrieve license information and usage.
* \[4.2.6\] Added support for **[gzip-compressed query responses](https://www.tigergraph.com/docs/tigergraph-server/4.2/API/index.md#_compressed_responses)** from RESTPP to the client, reducing transfer size for large results over low-bandwidth connections.
* \[4.2.6\] Added support for **[zstd-compressed query responses](https://www.tigergraph.com/docs/tigergraph-server/4.2/API/index.md#_compressed_responses)** from RESTPP to the client. Zstd compression can be requested through the RESTPP query endpoint or the GSQL `RUN QUERY` command.

### Query Language Enhancements

* Multiple enhancements to **Syntax V3**, which combines GSQL + OpenCypher + GQL Pattern Matching:  
   * **[GQL/OpenCypher path pattern syntax](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/select-statement/index.md#_from_clause)**, within GSQL syntax  
   * **Run ad hoc OpenCypher queries and single GSQL SELECT blocks directly** ([non-procedural interpreted queries](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/query-modes.md))  
   * **[comparison operators \= and <>](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/operators-and-expressions.md#_comparison_operators_and_conditions)** as alternatives to `==` and `!=` in WHERE conditions.  
   * **[OPTIONAL MATCH](https://github.com/tigergraph/ecosys/blob/master/tutorials/Cypher.md#optional-match), COALESCE, and IS \[NOT\] NULL** (OpenCypher)  
   * **[type() and labels() functions](https://www.tigergraph.com/docs/gsql-ref/4.2/openCypher-in-gsql/index.md#_opencypher_features_in_gsql)** (OpenCypher)
* **[Map and List query parameter types](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/data-types.md#_query_parameter_types)** are now supported.
* **LIKE: [<string1> LIKE <string pattern>](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/operators-and-expressions.md#_like)** can be used anywhere a condition is allowed, and <string pattern> can include functions.
* **[Simple CASE expressions and Searched CASE expressions](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/operators-and-expressions.md#_case_expressions)**
* **Bitwise Accumulators**: official support for [comparison and bitwise logic operators](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/accumulators.md#_bitwise_comparison_and_logic_operators).
* **[Configuation parameter GSQL.Github.Enabled](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/func/query-user-defined-functions.md#_use_github_to_store_udfs)** to enable retrieving UDFs from a Github repository.
* **[Query Profiler](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/query-optimizer/query-profiling.md)** to analyze query execution and performance.
* \[4.2.1\] Added support for the **["configs"](https://www.tigergraph.com/docs/tigergraph-server/4.2/API/gsql-endpoints.md#_run_a_loading_job)** object in loading jobs, enabling additional configuration **[parameters](https://www.tigergraph.com/docs/gsql-ref/4.2/ddl-and-loading/running-a-loading-job.md#_parameters)** via the REST API.
* \[4.2.1\] Added two new timestamp conversion functions, **[gsql\_ts\_to\_epoch\_seconds\_legacy()](https://www.tigergraph.com/docs/gsql-ref/4.2/ddl-and-loading/functions/token/gsql_ts_to_epoch_legacy.md)** and **[gsql\_ts\_to\_epoch\_seconds\_signed()](https://www.tigergraph.com/docs/gsql-ref/4.2/ddl-and-loading/functions/token/gsql_ts_to_epoch_signed.md)**, providing enhanced flexibility for date handling in loading jobs, including support for pre-1970 dates.
* \[4.2.1\] Added support for the [PRINT vt TO\_CSV f syntax](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/output-statements-and-file-objects.md#_printing_csv_to_a_file_object) to allow printing a vertex set directly to a CSV file.
* \[4.2.1\] File objects can now be created with an optional [file permission parameter](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/declaration-and-assignment-statements.md#_file_objects), allowing users to specify permissions using a Linux octal-encoded file permission code.

### Data Streaming/Connector Enhancements

* **[Improved connector for loading from external Kafka source](https://www.tigergraph.com/docs/tigergraph-server/4.2/data-loading/load-from-kafka.md)**: new configuration details. Older connector to[Load from External Kafka using MirrorMaker (Deprecated)](https://www.tigergraph.com/docs/tigergraph-server/4.2/data-loading/load-from-kafka-mm.md) is still available.
* **[Multi-character separators between data fields](https://www.tigergraph.com/docs/gsql-ref/4.2/ddl-and-loading/creating-a-loading-job.md#_using_clause)** in loading jobs.

* **[Schema Change options](https://www.tigergraph.com/docs/gsql-ref/4.2/ddl-and-loading/modifying-a-graph-schema.md#_run_schema_change_options)** `-force` and `-warn` to specify the behavior when loading jobs run during a schema change.
* **Introduced [DISABLED Loading Job status](https://www.tigergraph.com/docs/gsql-ref/4.2/ddl-and-loading/modifying-a-graph-schema.md#_side_effects_of_schema_change)** for jobs which have a schema conflict as a result of a Schema Change.
* Spark Connector supports **[OAuth2 authentication](https://www.tigergraph.com/docs/tigergraph-server/4.2/data-loading/load-from-spark-dataframe.md#_common_options)**, enabling seamless JWT token retrieval from third-party IdPs like Azure AD and Auth0 for improved **[security and token management](https://www.tigergraph.com/docs/tigergraph-server/4.2/data-loading/load-from-spark-dataframe.md#_authentication_methods)**.

### Performance Improvements

* **[Query Plan Caching](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/query-optimizer/query-plan-cache.md)**, to speed up the run time of repeated queries.

### GraphStudio, Admin Portal, and Insights

* Added a new page for changing passwords in **[TigerGraph Suite](https://www.tigergraph.com/docs/gui/4.2/admin-portal/management/user-management.md)**.
* See the **[release notes for Insights 4.2](https://www.tigergraph.com/docs/insights/4.2/release-notes/index.md)**.
* \[4.2.1\] **[Added a new entry on the GraphStudio homepage](https://www.tigergraph.com/docs/gui/4.2/graphstudio/export-and-import-solution.md#_install_a_pre_built_solution)** to browse and download pre-built solutions, making it easy to import and start projects with common graph use cases.
* \[4.2.1\] Added support in Insights for global parameters, enabling application-level variables to be defined once and shared across multiple pages.
* \[4.2.3\] Updated access control for the **[Query Monitoring](https://www.tigergraph.com/docs/gui/4.2/admin-portal/monitoring/queries.md#_access_control)** page to use privilege-based access instead of role-based access.  
   * `READ_DATA` privilege controls query visibility across all or specific graphs; users without access see an appropriate error message.  
   * Users with `DELETE_DATA` privilege can abort queries running on a graph.

---

## Fixed issues

### Fixed and Improved in 4.2.6

#### Functionality

* Fixed an issue where queries with default values for DATETIME parameters failed to compile (GLE-13743).
* Fixed an issue where stale graph entries in role mappings could block a TigerGraph upgrade (GLE-13657).
* Fixed an issue where the pre-upgrade check could fail with a NullPointerException while uploading catalog metadata (GLE-13638).
* Fixed an issue where the Upsert Data endpoint did not report the skipped count when `atomic` mode was enabled (CORE-6000).
* Fixed an issue where all segment data could be deleted after migrating to Savanna (CORE-6061).
* Fixed an issue where the Informant (IFM) service could take several minutes to start, causing upgrades to fail with an `Unable to talk to ifm` error. The service now reports a `WARMUP` status until it is ready (TP-11015).
* Added the `ProxyUserPermissionMerge` environment variable for RESTPP. When set to `true`, an existing proxy user also receives the permissions of the local user with the same name, and a new proxy user is not created for that user. By default, proxy users hold only the permissions granted to them directly (GLE-13590).
* Fixed an issue where loading jobs from Azure Data Lake Storage Gen2 using service principal authentication failed the account permission check when the service principal had only the Storage Blob Data Reader role (GLE-13481).

#### Security

* Fixed an issue where data source GET endpoints exposed credentials in their responses (GLE-13529).
* Third-party Vulnerabilities NOT impacting TigerGraph:  
Fixed the following security vulnerabilities: CVE-2026-106449, CVE-2026-106450, CVE-2026-106452, CVE-2026-106453, CVE-2026-108106, CVE-2026-116590, CVE-2026-13506, CVE-2026-19032, CVE-2026-33818, CVE-2026-39821, CVE-2026-39822, CVE-2026-39824, CVE-2026-42505, CVE-2026-46600, CVE-2026-47884, CVE-2026-47890, CVE-2026-49844, CVE-2026-54399, CVE-2026-54428, CVE-2026-55856, CVE-2026-55857, CVE-2026-55858, CVE-2026-56740, CVE-2026-56741, CVE-2026-56851, CVE-2026-56852, CVE-2026-56853, CVE-2026-56854, CVE-2026-56855, CVE-2026-56857, CVE-2026-56858, CVE-2026-56859, CVE-2026-56860, CVE-2026-56862, CVE-2026-56866, CVE-2026-59903, CVE-2026-59949, CVE-2026-63209, CVE-2026-64607, CVE-2026-65182, CVE-2026-65905, CVE-2026-68497, CVE-2026-68525, CVE-2026-75595, CVE-2026-75596, CVE-2026-78659, CVE-2026-78660, CVE-2026-78662, CVE-2026-78663, CVE-2026-78667, CVE-2026-78669, CVE-2026-83557, CVE-2026-86597, CVE-2026-8763, CVE-2026-89407, CVE-2026-89425, CVE-2026-91776, CVE-2026-91777, CVE-2026-93451, CVE-2026-94439, CVE-2026-94440, CVE-2026-94448, CVE-2026-97030, CVE-2026-97031, CVE-2026-97032, GHSA-hrxh-6v49-42gf, and GHSA-w67g-5rqw-f597.  
Third-party Vulnerability impacting TigerGraph: None.

### Fixed and Improved in 4.2.5

#### Functionality

* Fixed an issue where rebuilt graph data could fail to load correctly when deleted attributes had non-default values (CORE-5887).
* Fixed an issue where integer primary IDs with leading zeros were treated as different vertices during data loading (GLE-11687).
* Fixed an issue where newly expanded nodes in GraphStudio Explore Graph were not automatically centered, making parts of the graph difficult to view (APPS-4489).
* Fixed an issue where queries using certain user-defined functions (UDFs) could fail during query creation after upgrading from earlier releases (GLE-11304).
* Fixed an issue where the engine job listener could stop receiving updates after a ZeroMQ connection remained idle for an extended period (CORE-5906).
* Fixed an issue where loading jobs using Azure Data Lake Storage Gen2 service principal authentication failed because the connector incorrectly required a storage account key (GLE-13224).
* Fixed an issue where customer NGINX configuration customizations could be lost or newer-version settings could remain after downgrading TigerGraph (CORE-5939).

#### Security

* Fixed a local file inclusion vulnerability in the GraphQL `SearchFile` API that allowed users with database access to read files owned by the database service account.
* Fixed a secret disclosure vulnerability in the GraphQL `Config` query that returned decrypted `gadmin` configuration values to superusers.
* Third-party Vulnerabilities NOT impacting TigerGraph:  
Fixed the following security vulnerabilities: CVE-2024-13009, CVE-2024-23944, CVE-2024-31033, CVE-2024-6763, CVE-2025-11143, CVE-2025-14813, CVE-2025-67721, CVE-2025-67735, CVE-2025-68161, CVE-2026-0636, CVE-2026-1002, CVE-2026-22007, CVE-2026-22013, CVE-2026-22016, CVE-2026-22021, CVE-2026-22732, CVE-2026-22737, CVE-2026-24281, CVE-2026-24308, CVE-2026-24734, CVE-2026-24880, CVE-2026-25679, CVE-2026-25680, CVE-2026-27139, CVE-2026-27145, CVE-2026-29146, CVE-2026-29181, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-3293, CVE-2026-32990, CVE-2026-33186, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-33870, CVE-2026-33871, CVE-2026-34268, CVE-2026-34282, CVE-2026-34477, CVE-2026-34478, CVE-2026-34480, CVE-2026-34483, CVE-2026-34487, CVE-2026-34500, CVE-2026-39820, CVE-2026-39822, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39827, CVE-2026-39829, CVE-2026-39835, CVE-2026-39836, CVE-2026-41284, CVE-2026-41417, CVE-2026-42055, CVE-2026-42198, CVE-2026-42499, CVE-2026-42504, CVE-2026-42505, CVE-2026-42507, CVE-2026-42577, CVE-2026-42578, CVE-2026-42579, CVE-2026-42580, CVE-2026-42581, CVE-2026-42583, CVE-2026-42584, CVE-2026-42585, CVE-2026-42587, CVE-2026-42945, CVE-2026-43513, CVE-2026-44249, CVE-2026-45205, CVE-2026-45416, CVE-2026-45536, CVE-2026-46597, CVE-2026-46598, CVE-2026-46917, CVE-2026-46968, CVE-2026-47010, CVE-2026-47021, CVE-2026-47027, CVE-2026-47059, CVE-2026-47063, CVE-2026-47244, CVE-2026-47838, CVE-2026-48043, CVE-2026-48142, CVE-2026-50010, CVE-2026-50020, CVE-2026-50560, CVE-2026-54291, CVE-2026-54512, CVE-2026-54513, CVE-2026-54514, CVE-2026-54515, CVE-2026-54516, CVE-2026-54517, CVE-2026-55831, CVE-2026-55833, CVE-2026-5588, CVE-2026-56740, CVE-2026-56741, CVE-2026-56745, CVE-2026-56746, CVE-2026-59889, CVE-2026-59901, CVE-2026-59921, CVE-2026-60147, CVE-2026-62574, CVE-2026-6790, and CVE-2026-6860.  
Third-party Vulnerability impacting TigerGraph: None

### Fixed and Improved in 4.2.4

#### Functionality

* Fixed an issue where custom NGINX configuration changes could be overwritten during cluster upgrades instead of being preserved automatically (CORE-5785).
* Fixed an issue where long-running query installation requests submitted through a follower node could appear to hang if the client connection timed out before the operation completed (GLE-13080).
* Fixed an issue where failed query installation or reinstallation could leave the query lock unreleased, preventing subsequent query operations until the service was restarted (GLE-13094).
* Fixed an issue where cluster expansion or shrink operations could continue after a core data import failure instead of stopping with an error (TP-10680).

#### Security

* Fixed an issue where SAML SSO ignored the configuration to disable certificate validation (GLE-13060).
* Third-party Vulnerabilities NOT impacting TigerGraph:  
Fixed the following security vulnerabilities: CVE-2024-13009, CVE-2024-23944, CVE-2024-31033, CVE-2024-6763, CVE-2025-11143, CVE-2025-14813, CVE-2025-67030, CVE-2025-67721, CVE-2025-67735, CVE-2025-68161, CVE-2026-0636, CVE-2026-1002, CVE-2026-22007, CVE-2026-22013, CVE-2026-22016, CVE-2026-22018, CVE-2026-22021, CVE-2026-22732, CVE-2026-22735, CVE-2026-22737, CVE-2026-2332, CVE-2026-24051, CVE-2026-24281, CVE-2026-24308, CVE-2026-24734, CVE-2026-24880, CVE-2026-25679, CVE-2026-25680, CVE-2026-25854, CVE-2026-27139, CVE-2026-27142, CVE-2026-27145, CVE-2026-29145, CVE-2026-29146, CVE-2026-29181, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-3293, CVE-2026-32990, CVE-2026-33186, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-33870, CVE-2026-33871, CVE-2026-34268, CVE-2026-34282, CVE-2026-34477, CVE-2026-34478, CVE-2026-34480, CVE-2026-34483, CVE-2026-34487, CVE-2026-34500, CVE-2026-39820, CVE-2026-39822, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39827, CVE-2026-39828, CVE-2026-39829, CVE-2026-39830, CVE-2026-39831, CVE-2026-39832, CVE-2026-39833, CVE-2026-39834, CVE-2026-39835, CVE-2026-39836, CVE-2026-39883, CVE-2026-41284, CVE-2026-41293, CVE-2026-41417, CVE-2026-42198, CVE-2026-42498, CVE-2026-42499, CVE-2026-42504, CVE-2026-42505, CVE-2026-42507, CVE-2026-42508, CVE-2026-42577, CVE-2026-42578, CVE-2026-42579, CVE-2026-42580, CVE-2026-42581, CVE-2026-42583, CVE-2026-42584, CVE-2026-42585, CVE-2026-42587, CVE-2026-42945, CVE-2026-43512, CVE-2026-43513, CVE-2026-43514, CVE-2026-43515, CVE-2026-44249, CVE-2026-45205, CVE-2026-45416, CVE-2026-45536, CVE-2026-45673, CVE-2026-45674, CVE-2026-46595, CVE-2026-46597, CVE-2026-46598, CVE-2026-47244, CVE-2026-47691, CVE-2026-47838, CVE-2026-48043, CVE-2026-50010, CVE-2026-50020, CVE-2026-50560, CVE-2026-54512, CVE-2026-54513, CVE-2026-54514, CVE-2026-54515, CVE-2026-54516, CVE-2026-54517, CVE-2026-54518, CVE-2026-5588, and CVE-2026-6860.  
Third-party Vulnerability impacting TigerGraph: None

### Fixed and Improved in 4.2.3

#### Functionality

* Fixed an issue where binary files were still written during segment rebuild even after the segment was deleted, causing unnecessary disk usage (CORE-5356).
* Fixed an issue where gcollect could panic when encountering malformed NGINX log entries during log processing (TP-9128).
* Fixed an issue where log access in the Admin Portal required both `APP_ACCESS_LOG` and `APP_ACCESS_DATA` privileges instead of `APP_ACCESS_LOG` exclusively (APPS-3253).
* Fixed an issue where repeated backups took progressively longer despite minimal data growth, caused by inefficient processing of schema changes (CORE-5360).
* Fixed an issue where partition configuration recovery could result in schema inconsistencies when config.yaml was missing but segment data existed (CORE-5376, CORE-5381).
* Fixed an issue that caused intermittent errors during legacy token validation (GLE-11715).
* Fixed an issue where token generation could become unresponsive during schema change operations by optimizing the workflow (GLE-11727).
* Fixed an issue where requests on port 14240 could not be routed directly to a specific RESTPP node when direct node-level access was required (TP-9198).
* Fixed an issue where password policies intended for native users were incorrectly enforced on LDAP proxy users (GLE-11850).

#### Security

* Third-party Vulnerabilities NOT impacting TigerGraph:  
Fixed the following security vulnerabilities: CVE-2024-6763, CVE-2025-11143, CVE-2025-67030, CVE-2025-67721, CVE-2026-1002, CVE-2026-2332, CVE-2026-22007, CVE-2026-22013, CVE-2026-22016, CVE-2026-22018, CVE-2026-22021, CVE-2026-22732, CVE-2026-22735, CVE-2026-22737, CVE-2026-24051, CVE-2026-24281, CVE-2026-24308, CVE-2026-24734, CVE-2026-24880, CVE-2026-25679, CVE-2026-25854, CVE-2026-27139, CVE-2026-27142, CVE-2026-29145, CVE-2026-29146, CVE-2026-32280, CVE-2026-32281, CVE-2026-32282, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-3293, CVE-2026-32990, CVE-2026-33186, CVE-2026-33810, CVE-2026-33811, CVE-2026-33814, CVE-2026-33870, CVE-2026-33871, CVE-2026-34268, CVE-2026-34282, CVE-2026-34478, CVE-2026-34480, CVE-2026-34483, CVE-2026-34487, CVE-2026-34500, CVE-2026-39820, CVE-2026-39823, CVE-2026-39825, CVE-2026-39826, CVE-2026-39836, CVE-2026-41284, CVE-2026-41293, CVE-2026-41417, CVE-2026-42198, CVE-2026-42498, CVE-2026-42499, CVE-2026-42577, CVE-2026-42578, CVE-2026-42579, CVE-2026-42580, CVE-2026-42581, CVE-2026-42583, CVE-2026-42584, CVE-2026-42585, CVE-2026-42587, CVE-2026-43512, CVE-2026-43513, CVE-2026-43514, CVE-2026-43515, and CVE-2026-45205.  
Third-party Vulnerability impacting TigerGraph: None

### Fixed and Improved in 4.2.2

#### Functionality

* Fixed schema change failures during retry of DSCApply and restart caused by a schema inconsistency from deprecated or corrupted shared libraries for installed queries (CORE-5250).
* Fixed an issue where `/query_status` could report incorrect statuses and `/query_result` could fail to return results across cluster nodes (CORE-5211, GLE-11494).
* Fixed issue where the `pre_upgrade_check_gsql.sh` script failed silently, preventing error messages from being displayed during upgrade checks (GLE-11481).

#### Security

* Third-party Vulnerabilities NOT impacting TigerGraph:  
Fixed the following security vulnerabilities: CVE-2025-41249, CVE-2025-58056, CVE-2025-58057  
Third-party Vulnerability impacting TigerGraph: None

### Fixed and Improved in 4.2.1

#### Functionality

* 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).
* Improved the upgrade process by performing query and token bank compilation checks during pre‑upgrade instead of post-upgrade (GLE‑9459).
* Fixed an issue that could prevent GSQL from starting during upgrades due to errors while loading and validating required libraries and 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).
* Fixed an Out-of-Memory (OOM) issue that caused RESTPP to crash during timeout checks on asynchronous queries (CORE-4994).

#### Improvements

* 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](https://www.tigergraph.com/docs/tigergraph-server/4.2/installation/upgrade.md#_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](https://www.tigergraph.com/docs/gsql-ref/4.2/vector/index.md) 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).

#### Security

* 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).
* Third-party Vulnerabilities NOT impacting TigerGraph:  
Addressed multiple upstream and OS-level security vulnerabilities through package upgrades and dependency patching. Fixed the following security vulnerabilities: **CVE-2016-20013, CVE-2016-2781** CVE-2017-11164, CVE-2017-7475 **CVE-2018-18064** CVE-2019-6461 **CVE-2020-8908, CVE-2020-29582** CVE-2021-31879 **CVE-2022-27943, CVE-2022-3219, CVE-2022-41409, CVE-2022-4899** CVE-2023-29383, CVE-2023-2976, CVE-2023-34969, CVE-2023-37769, **CVE-2023-4039, CVE-2023-45288, CVE-2023-45289, CVE-2023-45290,** CVE-2023-45918, CVE-2023-48161, CVE-2023-50495, CVE-2023-7008  
   * CVE-2024-10041, CVE-2024-2236, CVE-2024-23337, CVE-2024-23454, CVE-2024-23944,  
   CVE-2024-24783, CVE-2024-24784, CVE-2024-24785, CVE-2024-24789, CVE-2024-24790, CVE-2024-24791,  
   CVE-2024-34155, CVE-2024-34156, CVE-2024-34158, CVE-2024-41996, CVE-2024-45336, CVE-2024-45341,  
   CVE-2024-52005, CVE-2024-52615, CVE-2024-52616, CVE-2024-56406, CVE-2024-56433, CVE-2024-6763, CVE-2024-8176  
   * CVE-2025-0167, CVE-2025-0913, CVE-2025-1352, CVE-2025-1376, CVE-2025-22233, CVE-2025-22234, CVE-2025-22235,  
   CVE-2025-22866, CVE-2025-22870, CVE-2025-22871, CVE-2025-22872, CVE-2025-22874, CVE-2025-23022,  
   CVE-2025-27496, CVE-2025-27613, CVE-2025-27817, CVE-2025-27818, CVE-2025-27819, CVE-2025-29088, CVE-2025-30204,  
   CVE-2025-32728, CVE-2025-32988, CVE-2025-32989, CVE-2025-32990, CVE-2025-3576, CVE-2025-41234, CVE-2025-41242,  
   CVE-2025-4598, CVE-2025-4673, CVE-2025-46701, CVE-2025-46835, CVE-2025-46836, CVE-2025-47907, CVE-2025-48060,  
   CVE-2025-48734, CVE-2025-48924, CVE-2025-48988, CVE-2025-48989, CVE-2025-49125, CVE-2025-49146, CVE-2025-49574,  
   CVE-2025-52520, CVE-2025-53506, CVE-2025-55163, CVE-2025-6069, CVE-2025-6395, CVE-2025-7345, CVE-2025-8176  
   Third-party Vulnerability impacting TigerGraph: None

### 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).
* 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).

#### Improvements

* 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.

#### Security

* Third-party Vulnerabilities NOT impacting TigerGraph:  
Fixed the following security vulnerabilities: CVE-2023-45288, CVE-2024-24790, CVE-2024-34156, and CVE-2024-45337.  
Third-party Vulnerability impacting TigerGraph: None

## Known Issues and Limitations

| Description | Found In | Workaround | Fixed In |
| --- | --- | --- | --- |
| GraphStudio may over-enforce `READ_DATA` access controls, preventing users from executing path/search built-ins in Explore Graph when the traversal includes intermediate vertex or edge types for which they do not have `READ_DATA` access. | 4.2.3 | Use GSQL as a workaround, as it supports type-level `READ_DATA` access controls and is not subject to this over-enforcement. |  |
| The presence of a forward slash (`/`) in a vertex ID can prevent certain operations, including editing vertex attributes, deleting vertices in Explore Graph, and adding edges to or from vertices containing `/`. In some cases, the UI may also freeze. | 4.2.2 | When calling RESTPP endpoints that include vertex IDs containing URL characters, percent-encode the characters in the vertex ID (for example, `%2F` for `/`). There is no workaround for the other affected operations. | TBD |
| When performing a rolling upgrade from a version between 4.2.0 and 4.2.2 to a later 4.2.x version with `Nginx.SSL.Enable=true`, the upgrade may fail while blocking GSQL long-running operations due to an internal HTTPS request failure. | 4.2.0\~4.2.2 | Since rolling upgrade is a preview feature in 4.2.x, users with `Nginx.SSL.Enable=true` should use a regular upgrade as the recommended upgrade path. Regular upgrade works with SSL enabled and does not require disabling any security configuration. If users still choose to use rolling upgrade, temporarily disable `Nginx.SSL.Enable`, apply the configuration, and restart GSQL and NGINX services before performing the rolling upgrade. After the upgrade completes successfully, re-enable SSL, apply the configuration, and restart GSQL and NGINX services. | 4.2.3 |
| If a non-procedural query has a syntax error, the GSQL interpreter ignored the invalid portion and executed the partial query before the error, without raising an error. | 4.2.0 | Check the full query before accepting it. | 4.2.1 |
| A NullPointerException occurs when performing a code check for queries using statements other than a = vt.\* or a = {vt.\*}, causing query creation to fail. | 4.1.3 | TBD | TBD |
| When `pulldict` fails, an empty debug log is generated, as the log level for debug is not enabled by default. | 4.1.3 | TBD | TBD |
| After upgrading, the system fails to detect `to_string()` in the UDF file, leading to query compilation errors. This issue occurs because the system doesn't report parsing errors during file uploads. | 4.1.3 | TBD | TBD |
| When using `set(index, value)` and `flip(index)` with BitwiseOrAccum<1000>, the task fails due to lack of support for bit operators `(&, \|, ~)` in bitwise accumulation. | 4.1.3 | TBD | TBD |
| Using [.flip()](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/accumulators.md#_bitwiseandaccum_bitwiseoraccum) on `BitwiseAndAccum` or `BitwiseOrAccum` inside a `PRINT` block may produce different results in UDF mode versus Single/Distributed mode. | 4.1.3 | Move the `.flip()` logic to the POST-ACCUM block for consistent behavior. | TBD |
| After a cluster expansion, the GPE service may remain in the warmup state. | 4.1.1 | If this happens, run `gadmin restart gse -y` to release the GPE. | TBD |
| When upgrading or performing cross-version database export/import from a version earlier than 4.1.0 to 4.1.0 or later, existing graph-level secrets are migrated to global-level secrets, and tokens associated with those secrets are removed. Cross-version database export/import across this version boundary is not recommended. | 4.1.0+ | TBD | TBD |
| The `EXECUTE_QUERY` privilege is not enforced on RESTPP endpoints. That is, users who lack `EXECUTE_QUERY` can still run a query via `POST /restpp/query/{graph_name}/{query_name}` | 4.1 | Use legacy methods for access control: Define separate graphs which span the same data but have different queries and users. | TBD |
| If a RESTPP request is for a graph operation and thus sent to the GPE then fails inside the GPE, the RESTPP will interpret the response from the GPE as success and report SUCCEED in the audit log. | 4.1 | Use a `/gsql` endpoint instead of a `/restpp` endpoint. | TBD |
| When [upgrading](https://www.tigergraph.com/docs/tigergraph-server/4.2/installation/upgrade.md#_upgrading_from_3_x), possible permission error for destination folder. | 3.10.1 | Manually grant permission to `/var/tmp` | TBD |
| [Export](https://www.tigergraph.com/docs/tigergraph-server/4.2/backup-and-restore/database-import-export.md) does not include LDAP proxy groups | 3.9+ | Manually recreate the proxy groups on the imported database. |  |

### Compatibility Issues

> [!NOTE]
> These Release Notes describe changes in this release.
> 
> For upgrade checks across versions, see the [Compatibility and Migration](https://www.tigergraph.com/docs/home/compatibility/index.md) pages.

| Description | Version Introduced |
| --- | --- |
| Many REST API endpoints were updated, including consolidation, path prefix changes, and token authentication support. See the [REST API reference](https://www.tigergraph.com/docs/tigergraph-server/4.1/API/index.md) page. | v4.1.0 |
| To apply a [File Input Policy](https://www.tigergraph.com/docs/tigergraph-server/4.2/security/gsql-file-input-policy.md) or [File Output Policy](https://www.tigergraph.com/docs/tigergraph-server/4.2/security/file-output-policy.md) change, now both `gsql` and `restpp` servers must be restarted: `gadmin restart gsql restpp -y` | v4.1.3, v4.2.0 |
| The [\--incremental option for backup](https://www.tigergraph.com/docs/tigergraph-server/4.2/backup-and-restore/incremental-backup.md) now performs a true incremental backup instead of a differential backup. | v4.2.0 |
| In [CDC messages](https://www.tigergraph.com/docs/tigergraph-server/4.2/system-management/change-data-capture/cdc-message-example.md#_message_examples), 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](https://www.tigergraph.com/docs/tigergraph-server/4.2/system-management/change-data-capture/cdc-message-example.md#_message_examples) generated by the TigerGraph CDC service. | v3.11.0, v4.1.1 |
| In [CDC messages](https://www.tigergraph.com/docs/tigergraph-server/4.2/system-management/change-data-capture/cdc-message-example.md#_message_examples), 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.](https://www.tigergraph.com/docs/tigergraph-server/4.2/security/gsql-file-input-policy.md#_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](https://www.tigergraph.com/docs/tigergraph-server/4.2/security/index.md#_udf_file_scanning). * 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 and Removals

| 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](https://www.tigergraph.com/docs/tigergraph-server/4.2/system-management/change-data-capture/cdc-message-example.md#_cdc_message_with_type_edge). | 4.1.1 | 4.2 |
| Access Control Lists (ACLs) are no longer supported. When upgrading from 3.x to 4.x, [ACL privileges will be automatically migrated to object-based privileges](https://www.tigergraph.com/docs/tigergraph-server/4.2/user-access/query-privilege-migration.md). | 4.1.0 | 4.1.0 |
| The use of plaintext tokens in [authentication](https://www.tigergraph.com/docs/tigergraph-server/4.2/API/authentication.md) is deprecated. Use [OIDC JWT Authentication](https://www.tigergraph.com/docs/tigergraph-server/4.2/user-access/jwt-token.md) instead. | 3.10.0 | TBD |
| **Vertex-level Access Control** (VLAC) and VLAC Methods are removed and are no longer available. | 3.10.0 | 4.1.0 |
| The command `gbar` is removed and is no longer available. It has been replaced by `gadmin backup`. | 3.7 | 3.10 |
| [Spark Connection via JDBC Driver](https://www.tigergraph.com/docs/tigergraph-server/4.2/data-loading/spark-connection-via-jdbc-driver.md) is now deprecated and will no longer be supported. | 3.10.0 | TBD |
| `Build Graph Patterns` is deprecated and will not be updated or supported and instead we are focusing on [Insights](https://www.tigergraph.com/docs/insights/4.2/widgets/index.md) as the tool of choice for building visual queries. | 3.9.3 | TBD |
| Kubernetes classic mode (non-operator) is deprecated. | 3.9 | TBD |
| The `WRITE_DATA` RBAC privilege is deprecated. | 3.7 | 4.1 |

## Release notes for previous versions

* [Release notes - TigerGraph 4.1](https://www.tigergraph.com/docs/tigergraph-server/4.1/release-notes/index.md)
* [Release notes - TigerGraph 3.11](https://www.tigergraph.com/docs/tigergraph-server/3.11/release-notes/index.md)
* [Release notes - TigerGraph 3.10](https://www.tigergraph.com/docs/tigergraph-server/3.10/release-notes/index.md)
