update

Author: Lucky-Wang16

articles/data-factory/connector-amazon-redshift.md

@@ -7,7 +7,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 06/12/2025
+ms.date: 06/16/2025
 ---
 
 # Copy data from Amazon Redshift using Azure Data Factory or Synapse Analytics
@@ -289,24 +289,22 @@ When you copy data from Amazon Redshift, the following mappings apply from Amazo
 
 To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
 
-## Upgrade the Amazon Redshift connector
+## <a name="differences-between-amazon-redshift-connector-version-20-and-version-10"></a> Amazon Redshift connector lifecycle and upgrade
 
-Here are steps that help you upgrade the Amazon Redshift connector:
+The following table shows the release stage and change logs for different versions of the Impala connector:
+
+| Version | Release stage | Change log |
+| :----------- | :------- | :------- |
+| Version 1.0 | End of support announced | / |
+| Version 2.0 (Preview) | Preview version available | • Only support the self-hosted integration runtime with version 5.54.0.0 or above. <br><br>• BOOLEAN is read as Boolean data type.  |
+
+### <a name="upgrade-the-amazon-redshift-connector"></a> Upgrade the Amazon Redshift connector from version 1.0 to version 2.0 (Preview)
 
 1. In **Edit linked service** page, select version 2.0 (Preview) and configure the linked service by referring to [linked service properties](#linked-service-properties).
 
 2. The data type mapping for the Amazon Redshift linked service version 2.0 (Preview) is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Amazon Redshift](#data-type-mapping-for-amazon-redshift).
 
 3. Apply a self-hosted integration runtime with version 5.54.0.0 or above. Azure integration runtime is not supported by version 2.0 (Preview).
 
-## <a name="differences-between-amazon-redshift-connector-version-20-and-version-10"></a>Differences between Amazon Redshift connector version 2.0 (Preview) and version 1.0
-
-The Amazon Redshift connector version 2.0 (Preview) offers new functionalities and is compatible with most features of version 1.0. The following table shows the feature differences between version 2.0 (Preview) and version 1.0.
-
-| Version 2.0 (Preview) | Version 1.0 |
-| :----------- | :------- |
-| Only support the self-hosted integration runtime with version 5.54.0.0 or above. | Support the Azure integration runtime and self-hosted integration runtime. |
-| The following mappings are used from Amazon Redshift data types to interim service data type.<br><br>BOOLEAN -> Boolean | The following mappings are used from Amazon Redshift data types to interim service data type.<br><br>BOOLEAN -> String |  
-
 ## Related content
 For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).

articles/data-factory/connector-hive.md

@@ -6,7 +6,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 05/27/2025
+ms.date: 06/16/2025
 ms.author: jianleishen
 ---
 
@@ -330,27 +330,21 @@ When you copy data from and to Hive, the following interim data type mappings ar
 
 To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
 
-## Upgrade the Hive connector 
 
-Here are steps that help you upgrade the Hive connector: 
+## <a name="differences-between-hive-version-20-and-version-10"></a> Hive connector lifecycle and upgrade
 
-1. In **Edit linked service** page, select version 2.0 (Preview) and configure the linked service by referring to [Linked service properties version 2.0](#version-20). 
+The following table shows the release stage and change logs for different versions of the Hive connector:
 
-2. The data type mapping for the Hive linked service version 2.0 (Preview) is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Hive](#data-type-mapping-for-hive).
-
-## <a name="differences-between-hive-version-20-and-version-10"></a> Differences between Hive version 2.0 (Preview) and version 1.0 
+| Version | Release stage | Change log |
+| :----------- | :------- | :------- |
+| Version 1.0 | GA version available | / |
+| Version 2.0 (Preview) | Preview version available | • Using ';' to separate multiple hosts (only when serviceDiscoveryMode is enabled) is not supported. <br><br>• HiveServer1 and HiveThriftServer are not supported for `ServerType`.  <br><br>• Username authentication type is not supported. SASL transport protocol only supports UsernameAndPassword authentication type. Binary transport protocol only supports Anonymous authentication type. <br><br>• `serviceDiscoveryMode`, `zooKeeperNameSpace` and `useNativeQuery` are not supported. <br><br>• The default value of `enableSSL` is true. `trustedCertPath`, `useSystemTrustStore`, `allowHostNameCNMismatch` and `allowSelfSignedServerCert` are not supported.<br><br>`enableServerCertificateValidation` is supported. <br><br>• TINYINT is read as SByte data type. <br><br>• TIMESTAMP is read as DateTimeOffset data type. |
 
-The Hive connector version 2.0 (Preview) offers new functionalities and is compatible with most features of version 1.0. The following table shows the feature differences between version 2.0 (Preview) and version 1.0. 
+### <a name="upgrade-the-hive-connector"></a> Upgrade the Hive connector from version 1.0 to version 2.0 (Preview)
 
-| Version 2.0 (Preview) | Version 1.0 |
-|:--- |:--- |
-| Using ';' to separate multiple hosts (only when serviceDiscoveryMode is enabled) is not supported.| Using ';' to separate multiple hosts (only when serviceDiscoveryMode is enabled) is supported.|
-| HiveServer1 and HiveThriftServer are not supported for `ServerType`. | Support HiveServer1 and HiveThriftServer for `ServerType`. |
-| Username authentication type is not supported. <br><br>SASL transport protocol only supports UsernameAndPassword authentication type. Binary transport protocol only supports Anonymous authentication type. | Support Username authentication type. <br><br>SASL and Binary transport protocols support Anonymous, Username, UsernameAndPassword and WindowsAzureHDInsightService authentication types. |
-| `serviceDiscoveryMode`, `zooKeeperNameSpace` and `useNativeQuery` are not supported. | `serviceDiscoveryMode`, `zooKeeperNameSpace`, `useNativeQuery` are supported. |
-| The default value of `enableSSL` is true. `trustedCertPath`, `useSystemTrustStore`, `allowHostNameCNMismatch` and `allowSelfSignedServerCert` are not supported.<br><br>`enableServerCertificateValidation` is supported.| The default value of `enableSSL` is false. `trustedCertPath`, `useSystemTrustStore`, `allowHostNameCNMismatch` and `allowSelfSignedServerCert` are supported.<br><br>`enableServerCertificateValidation` is not supported.  |
-| The following mappings are used from Hive data types to interim service data type.<br><br>TINYINT -> SByte<br>TIMESTAMP -> DateTimeOffset | The following mappings are used from Hive data types to interim service data type.<br><br>TINYINT -> Int16 <br>TIMESTAMP -> DateTime |  
+1. In **Edit linked service** page, select version 2.0 (Preview) and configure the linked service by referring to [Linked service properties version 2.0](#version-20).
 
+2. The data type mapping for the Hive linked service version 2.0 (Preview) is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Hive](#data-type-mapping-for-hive).
 
 ## Related content
 For a list of data stores supported as sources and sinks by the copy activity, see [supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).

articles/data-factory/connector-impala.md

@@ -6,7 +6,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 06/05/2025
+ms.date: 06/16/2025
 ms.author: jianleishen
 ---
 # Copy data from Impala using Azure Data Factory or Synapse Analytics
@@ -270,23 +270,21 @@ When you copy data from and to Impala, the following interim data type mappings
 
 To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
 
-## Upgrade the Impala connector 
+## <a name="differences-between-impala-version-20-and-version-10"></a> Impala connector lifecycle and upgrade
 
-Here are steps that help you upgrade the Impala connector: 
+The following table shows the release stage and change logs for different versions of the Impala connector:
 
-1. In **Edit linked service** page, select version 2.0 (Preview) and configure the linked service by referring to [Linked service properties version 2.0](#version-20). 
+| Version | Release stage | Change log |
+| :----------- | :------- | :------- |
+| Version 1.0 | End of support announced | / |
+| Version 2.0 (Preview) | Preview version available | • SASLUsername authentication type is not supported. <br><br>• The default value of `enableSSL` is true. `trustedCertPath`, `useSystemTrustStore`, `allowHostNameCNMismatch` and `allowSelfSignedServerCert` are not supported.<br>`enableServerCertificateValidation` is supported.  <br><br>• TIMESTAMP is read as DateTimeOffset data type. <br><br>• TINYINT is read as SByte data type. |
 
-2. The data type mapping for the Impala linked service version 2.0 (Preview) is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Impala](#data-type-mapping-for-impala).
+### <a name="upgrade-the-impala-connector"></a> Upgrade the Impala connector from version 1.0 to version 2.0 (Preview)
 
-## <a name="differences-between-impala-version-20-and-version-10"></a> Differences between Impala version 2.0 (Preview) and version 1.0 
+1. In **Edit linked service** page, select version 2.0 (Preview) and configure the linked service by referring to [Linked service properties version 2.0](#version-20).
 
-The Impala connector version 2.0 (Preview) offers new functionalities and is compatible with most features of version 1.0. The following table shows the feature differences between version 2.0 (Preview) and version 1.0. 
+2. The data type mapping for the Impala linked service version 2.0 (Preview) is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Impala](#data-type-mapping-for-impala).
 
-| Version 2.0 (Preview) | Version 1.0 |
-|:--- |:--- |
-| SASLUsername authentication type is not supported. | Support SASLUsername authentication type. |
-| The default value of `enableSSL` is true. `trustedCertPath`, `useSystemTrustStore`, `allowHostNameCNMismatch` and `allowSelfSignedServerCert` are not supported.<br><br>`enableServerCertificateValidation` is supported.| The default value of `enableSSL` is false. `trustedCertPath`, `useSystemTrustStore`, `allowHostNameCNMismatch` and `allowSelfSignedServerCert` are supported.<br><br>`enableServerCertificateValidation` is not supported.  |
-| The following mappings are used from Impala data types to interim service data type.<br><br>TIMESTAMP -> DateTimeOffset <br>TINYINT -> SByte | The following mappings are used from Impala data types to interim service data type.<br><br>TIMESTAMP -> DateTime <br>TINYINT -> Int16 |  
 
 ## Related content
 For a list of data stores supported as sources and sinks by the copy activity, see [Supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).