---
title: "Compatibility among TigerGraph 4 versions"
description: "lists the compatibility issues between different versions of TigerGraph 4, for users who plan to migrate"
component: "home"
version: "master"
module: "compatibility"
html_url: "/home/compatibility/changes-among-tg4"
canonical_url: "https://www.tigergraph.com/docs/home/compatibility/changes-among-tg4"
markdown_url: "https://www.tigergraph.com/docs/home/compatibility/changes-among-tg4.md"
---

[View as HTML](https://www.tigergraph.com/docs/home/compatibility/changes-among-tg4)

# Compatibility among TigerGraph 4 versions

This page lists the discontinued features or other incompatible changes from one TigerGraph 4.x version to another TigerGraph 4.x version.

> [!NOTE]
> The list does not include bug fixes where a feature was not working correctly before and now is working according to the specification. Those issues are listed on the Release Notes page.

## TigerGraph Compatibility changes from 4.1 to 4.2

| Version | Description | Recommendation |
| --- | --- | --- |
| 4.2.0 | [File Input](https://www.tigergraph.com/docs/tigergraph-server/4.2/security/gsql-file-input-policy.md) and [File Output](https://www.tigergraph.com/docs/tigergraph-server/4.2/security/file-output-policy.md) Policy changes require restarting `gsql` and `restpp` servers. | Restart `gsql` and `restpp` with `gadmin restart gsql restpp -y` after policy updates. |
| 4.2.0 | The `--incremental` backup option now performs true incremental backups. | Plan [backup and restore](https://www.tigergraph.com/docs/tigergraph-server/4.2/backup-and-restore/incremental-backup.md) processes accordingly. |
| 4.2.0 | In CDC messages, the format of **tuple values** has changed. | Update your applications that consume [CDC messages](https://www.tigergraph.com/docs/tigergraph-server/4.2/system-management/change-data-capture/cdc-message-example.md#_message_examples) to handle the new format for tuple values. |
| 4.2.0 | The response field returned when submitting an [asynchronous query](https://www.tigergraph.com/docs/gsql-ref/4.2/querying/run-manage-queries.md#_detached_mode_async_option) was changed from `request_id` to `requestid` to align with query management APIs such as `/query_status`, `/query_result`, and query cancellation endpoints. | Update scripts, applications, log parsers, and automation that extract the asynchronous query identifier from API responses to use `requestid` instead of `request_id`. |
| 4.2.0 | `SelectVertex()` no longer allows relative filepaths. | Use absolute filepaths in `SelectVertex()` calls. |
| 4.2.0 | The `--meta` option for backup is no longer needed because metadata is included automatically. | Remove the `--meta` option from your `gadmin` backup commands |
| 4.2.0 | External Kafka streaming connector (3.6 to 3.9.2) is no longer supported. | Switch to supported Kafka connectors or newer versions. |

See also [Compatibility between TigerGraph 3.10 and TigerGraph 4.1](https://www.tigergraph.com/docs/home/compatibility/changes-from-tg3.10-to-tg4.1.md)
