Skip to content

Commit de4b6b3

Browse files
committed
update
1 parent 0e6a36d commit de4b6b3

File tree

1 file changed

+1
-81
lines changed

1 file changed

+1
-81
lines changed

articles/data-factory/connector-google-bigquery.md

Lines changed: 1 addition & 81 deletions
Original file line numberDiff line numberDiff line change
@@ -235,87 +235,7 @@ The following table shows the release stage and change logs for different versio
235235

236236
### <a name="upgrade-the-google-bigquery-linked-service"></a> Upgrade the Google BigQuery connector from V1 to V2
237237

238-
To upgrade the Google BigQuery connector from V1 to V2, you can do a side-by-side upgrade, or an in-place upgrade.
239-
240-
#### Side-by-side upgrade
241-
242-
To perform a side-by-side upgrade, complete the following steps:
243-
244-
1. Create a new Google BigQuery linked service and configure it by referring to the V2 linked service properties.
245-
1. Create a dataset based on the newly created Google BigQuery linked service.
246-
1. Replace the new linked service and dataset with the existing ones in the pipelines that targets the V1 objects.
247-
248-
#### In-place upgrade
249-
250-
To perform an in-place upgrade, you need to edit the existing linked service payload and update dataset to use the new linked service.
251-
252-
1. Update the type from **GoogleBigQuery** to **GoogleBigQueryV2**.
253-
1. Modify the linked service payload from its V1 format to V2. You can either fill in each field from the user interface after changing the type mentioned above, or update the payload directly through the JSON Editor. Refer to the [Linked service properties](#linked-service-properties) section in this article for the supported connection properties. The following examples show the differences in payload for the V1 and V2 Google BigQuery linked services:
254-
255-
**Google BigQuery V1 linked service JSON payload:**
256-
```json
257-
{
258-
"name": "GoogleBigQuery1",
259-
"type": "Microsoft.DataFactory/factories/linkedservices",
260-
"properties": {
261-
"annotations": [],
262-
"type": "GoogleBigQuery",
263-
"typeProperties": {
264-
"project" : "<project ID>",
265-
"additionalProjects" : "<additional project IDs>",
266-
"requestGoogleDriveScope" : true,
267-
"authenticationType" : "UserAuthentication",
268-
"clientId": "<id of the application used to generate the refresh token>",
269-
"clientSecret": {
270-
"type": "SecureString",
271-
"value":"<secret of the application used to generate the refresh token>"
272-
},
273-
"refreshToken": {
274-
"type": "SecureString",
275-
"value": "<refresh token>"
276-
}
277-
},
278-
"connectVia": {
279-
"referenceName": "AzureIntegrationRuntime",
280-
"type": "IntegrationRuntimeReference"
281-
}
282-
}
283-
}
284-
```
285-
286-
**Google BigQuery V2 linked service JSON payload:**
287-
```json
288-
{
289-
"name": "GoogleBigQuery2",
290-
"type": "Microsoft.DataFactory/factories/linkedservices",
291-
"properties": {
292-
"annotations": [],
293-
"type": "GoogleBigQueryV2",
294-
"typeProperties": {
295-
"projectId" : "<project ID>",
296-
"authenticationType" : "UserAuthentication",
297-
"clientId": "<client ID>",
298-
"clientSecret": {
299-
"type": "SecureString",
300-
"value":"<client secret>"
301-
},
302-
"refreshToken": {
303-
"type": "SecureString",
304-
"value": "<refresh token>"
305-
}
306-
},
307-
"connectVia": {
308-
"referenceName": "AutoResolveIntegrationRuntime",
309-
"type": "IntegrationRuntimeReference"
310-
}
311-
}
312-
}
313-
```
314-
315-
1. Update dataset to use the new linked service. You can either create a new dataset based on the newly created linked service, or update an existing dataset's type property from **GoogleBigQueryObject** to **GoogleBigQueryV2Object**.
316-
317-
>[!NOTE]
318-
>When transitioning linked services, the override template parameter section might only display database properties. You can resolve this by manually editing the parameters. After that the **Override template parameters** section will show the connection strings.
238+
To upgrade the Google BigQuery connector, create a new Google BigQuery linked service and configure it by referring to [Linked service properties](#linked-service-properties).
319239

320240
### Upgrade the Google BigQuery V2 connector from version 1.0 to version 1.1
321241

0 commit comments

Comments
 (0)