You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-factory/connector-lifecycle-overview.md
+47-1Lines changed: 47 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,17 +72,63 @@ In addition to major and minor version updates, the service also delivers new fe
72
72
73
73
In addition to providing [tools](connector-upgrade-advisor.md) and [best practices](connector-upgrade-guidance.md) to help users manually upgrade their connectors, the service now also provides a more streamlined upgrade process for some cases where applicable. This is designed to help users adopt the most reliable and supported connector versions with minimal disruption.
74
74
75
-
The following section outlines the general that the service takes for automatic upgrades. While this provides a high-level overview, it is strongly recommended to review the documentation specific to each connector to understand which scenarios are supported and how the upgrade process applies to your workloads.
75
+
The following section outlines the general approach that the service takes for automatic upgrades. While this provides a high-level overview, it is strongly recommended to review the documentation specific to each connector to understand which scenarios are supported and how the upgrade process applies to your workloads.
76
76
77
77
In cases where certain scenarios running on the latest GA connector version are fully backward compatible with the previous version, the service will automatically upgrade existing workloads (such as Copy, Lookup, and Script activities) to a compatibility mode that preserves the behavior of the earlier version.
78
78
79
79
These auto-upgraded workloads are not affected by the announced removal date of the older version, giving users additional time to evaluate and transition to the latest GA version without facing immediate failures.
80
80
81
81
You can identify which activities have been automatically upgraded by inspecting the activity output, where relevant upgrade information is recorded.
82
82
83
+
Example:
84
+
85
+
Copy activity output
86
+
87
+
```json
88
+
"source": {
89
+
"type": "AmazonS3",
90
+
"autoUpgrade": "true",
91
+
"compatibleWithVersion": "1.0"
92
+
}
93
+
94
+
"sink": {
95
+
"type": "AmazonS3",
96
+
"autoUpgrade": "true",
97
+
"compatibleWithVersion": "1.0"
98
+
}
99
+
```
100
+
101
+
Lookup activity output
102
+
103
+
```json
104
+
"source": {
105
+
"type": "AmazonS3",
106
+
"autoUpgrade": "true",
107
+
"compatibleWithVersion": "1.0"
108
+
}
109
+
```
110
+
111
+
112
+
Script activity output
113
+
114
+
```json
115
+
"source": {
116
+
"type": "AmazonS3",
117
+
"autoUpgrade": "true",
118
+
"compatibleWithVersion": "1.0"
119
+
}
120
+
```
121
+
83
122
> [!NOTE]
84
123
> While compatibility mode offers flexibility, we strongly encourage users to upgrade to the latest GA version as soon as possible to benefit from ongoing improvements, optimizations, and full support.
85
124
125
+
You can find more details from the table below on the connector list that is planned for the automatic upgrade.
126
+
127
+
| Connector | Scenario |
128
+
|------------------|----------|
129
+
| Google BigQuery | Scenario that does not rely on below capability in Google BigQuery V1:<br><br> • Use `trustedCertsPath`, `additionalProjects`, `requestgoogledrivescope` connection properties.<br> • Set `useSystemTrustStore` connection property as `false`.<br> • Use **STRUCT** and **ARRAY** data types. |
130
+
| Teradata | Scenario that does not rely on below capability in Teradata (version 1.0):<br><br> • Set below value for **CharacterSet**:<br> - BIG5 (TCHBIG5_1R0)<br> - EUC (Unix compatible, KANJIEC_0U)<br> - GB (SCHGB2312_1T0)<br> - IBM Mainframe (KANJIEBCDIC5035_0I)<br> - NetworkKorean (HANGULKSC5601_2R4)<br> - Shift-JIS (Windows, DOS compatible, KANJISJIS_0S)|
0 commit comments