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/automatic-connector-upgrade.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,9 +72,9 @@ You can find more details from the table below on the connector list that is pla
72
72
|[Google BigQuery](connector-google-bigquery.md)| Scenario that doesn't 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. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.58 or above. |
73
73
|[Greenplum](connector-greenplum.md)| If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.56 or above. |
74
74
|[Hive](connector-hive.md)| Scenario that doesn't rely on below capability in Hive (version 1.0):<br><br>• Use Username authentication type.<br>• Thrift transport protocol:<br> • HiveServer1<br>• Service discovery mode: True<br>• Use native query: True <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.59 or above.|
75
-
| [HubSpot](connector-hubspot.md) | The following HubSpot tables are supported for automatic upgrade:<br> Hubspot.Deal_Properties, Hubspot.Company_Properties, Hubspot.Deals, Hubspot.Deal_Associations_Associated_Vids, Hubspot.Contact_Properties, Hubspot.All_Deals, Hubspot.Contact_Lists, Hubspot.Deal_Properties_Options, Hubspot.Contact_Properties_Options, Hubspot.Companies_Properties_Values, Hubspot.Deal_Pipelines_Stages, Hubspot.Companies, Hubspot.Contacts, Hubspot.Deal_Properties_Values, Hubspot.Deal_Pipelines, CRM.Contact_Properties_Values, Hubspot.Deal_Associations_Associated_Company_Ids, Hubspot.Contacts_List_Memberships, Hubspot.Contacts_Identity_Profiles_Identities, Hubspot.TicketPipeLines, Hubspot.TicketPipeLinesStages, Hubspot.LineItemProperties, Hubspot.Deal_Property_Groups, Hubspot.CRMDealsPipeLinesStages, Hubspot.LineItemPropertiesOptions, Hubspot.Contact_Property_Groups, Hubspot.Contacts_Identity_Profiles, Hubspot.Users, Hubspot.EmailSubscriptions, Hubspot.CallEngagementDisposition, Hubspot.Tickets, Hubspot.Forms, CRM.CompanyProperties, CRM.DealProperties, CRM.Owners, CRM.LineItemProperties. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.64 or above. |
75
+
| [HubSpot](connector-hubspot.md) | The following HubSpot tables are supported for automatic upgrade:<br><br>Hubspot.Deal_Properties, Hubspot.Company_Properties, Hubspot.Deals, Hubspot.Deal_Associations_Associated_Vids, Hubspot.Contact_Properties, Hubspot.All_Deals, Hubspot.Contact_Lists, Hubspot.Deal_Properties_Options, Hubspot.Contact_Properties_Options, Hubspot.Companies_Properties_Values, Hubspot.Deal_Pipelines_Stages, Hubspot.Companies, Hubspot.Contacts, Hubspot.Deal_Properties_Values, Hubspot.Deal_Pipelines, CRM.Contact_Properties_Values, Hubspot.Deal_Associations_Associated_Company_Ids, Hubspot.Contacts_List_Memberships, Hubspot.Contacts_Identity_Profiles_Identities, Hubspot.TicketPipeLines, Hubspot.TicketPipeLinesStages, Hubspot.LineItemProperties, Hubspot.Deal_Property_Groups, Hubspot.CRMDealsPipeLinesStages, Hubspot.LineItemPropertiesOptions, Hubspot.Contact_Property_Groups, Hubspot.Contacts_Identity_Profiles, Hubspot.Users, Hubspot.EmailSubscriptions, Hubspot.CallEngagementDisposition, Hubspot.Tickets, Hubspot.Forms, CRM.CompanyProperties, CRM.DealProperties, CRM.Owners, CRM.LineItemProperties. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.64 or above. |
76
76
|[Impala](connector-impala.md)| Scenario that doesn't rely on below capability in Impala (version 1.0):<br><br>• Use SASL Username authentication type.<br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.59 or above. |
77
-
| [Jira](connector-jira.md) | Scenario that doesn't rely on below capability in Jira (version 1.0):<br><br>• Use `useEncryptedEndpoints`, `useHostVerification` and `usePeerVerification` as connection properties. <br>• Use `query`. <br><br>The following Jira tables are supported for automatic upgrade:<br> Platform.Api_Groups_Picker, Platform.Api_Issue_Type, Platform.Api_Project, Platform.Api_Field, Platform.Api_Status, Platform.Api_Status_Category, Platform.Api_Project_Type, Platform.Api_Resolution, Platform.Api_Priority, Platform.ApiAllUsers, Platform.Api_Issue_Link_Type, Platform.Api_Role, Platform.Api_Project_Versions, Platform.Api_Component, Platform.Api_Project_IssueTypes, Platform.Api_Issue, Agile.Agile_Board_Epic, Agile.Agile_Board, Agile.Agile_Board_Sprint, Agile.Column_Config_Columns, Agile.Agile_Board_Issue_Fields_Components, Agile.Agile_Board_Issue_Fields_Closed_Sprints, Agile.AgileBoardProjects. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.64 or above. |
77
+
| [Jira](connector-jira.md) | Scenario that doesn't rely on below capability in Jira (version 1.0):<br><br>• Use `useEncryptedEndpoints`, `useHostVerification` and `usePeerVerification` as connection properties. <br>• Use `query`. <br><br>The following Jira tables are supported for automatic upgrade:<br><br>Platform.Api_Groups_Picker, Platform.Api_Issue_Type, Platform.Api_Project, Platform.Api_Field, Platform.Api_Status, Platform.Api_Status_Category, Platform.Api_Project_Type, Platform.Api_Resolution, Platform.Api_Priority, Platform.ApiAllUsers, Platform.Api_Issue_Link_Type, Platform.Api_Role, Platform.Api_Project_Versions, Platform.Api_Component, Platform.Api_Project_IssueTypes, Platform.Api_Issue, Agile.Agile_Board_Epic, Agile.Agile_Board, Agile.Agile_Board_Sprint, Agile.Column_Config_Columns, Agile.Agile_Board_Issue_Fields_Components, Agile.Agile_Board_Issue_Fields_Closed_Sprints, Agile.AgileBoardProjects. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.64 or above. |
78
78
|[MariaDB](connector-mariadb.md)| If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.58 or above. |
79
79
|[MySQL](connector-mysql.md)| If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.58 or above. |
80
80
|[Netezza](connector-netezza.md)| If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.59 or above. |
@@ -88,7 +88,7 @@ You can find more details from the table below on the connector list that is pla
88
88
|[Spark](connector-spark.md)| Scenario that doesn't rely on below capability in Spark (version 1.0):<br><br>• Use Username authentication type. <br>• Thrift transport protocol:<br> • SASL<br> • Binary<br>• Thrift transport protocol:<br> • SharkServer<br> • SharkServer2<br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.59 or above.|
89
89
|[Teradata](connector-teradata.md)| Scenario that doesn't 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)<br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.58 or above.|
90
90
|[Vertica](connector-vertica.md)| Scenario that doesn't rely on below capability in Vertica (version 1.0):<br><br>• Linked service that uses Azure integration runtime.<br><br>Automatic upgrade is only applicable when the driver is installed in your machine that installs the self-hosted integration runtime (version 5.56 or above).<br><br> For more information, go to [Install Vertica ODBC driver for the version 2.0](connector-vertica.md#install-vertica-odbc-driver-for-the-version-20). |
91
-
| [Xero](connector-xero.md) | Scenario that doesn't rely on below capability in Xero (version 1.0):<br><br>• Use OAuth 1.0 authentication type. <br><br>The following Xero tables are supported for automatic upgrade: <br> Accounts, AssetSettings, AssetTypes, Associations, Bank_Transaction_Line_Item_Tracking, Bank_Transaction_Line_Items, Bank_Transactions, Bank_Transfers, BankFeedConnections, Branding_Themes, Budgets, Contact_Group_Contacts, Contact_Groups, Contacts, Contacts_Addresses, Contacts_Contact_Persons, Contacts_Phones, Contacts_Purchases_Tracking_Categories, Contacts_Sales_Tracking_Categories, Credit_Note_Line_Items, Credit_Notes, Credit_Notes_Allocations, Credit_Notes_Line_Items_Tracking, Currencies, Employees, Expense_Claim_Payments, Expense_Claim_Receipts, Expense_Claim_Validation_Errors, Expense_Claims, Files, Folders, Invoice_Line_Items, Invoices, Invoices_Credit_Notes, Invoices_Line_Items_Tracking, Invoices_Overpayments, Invoices_Prepayments, Items, Journal_Line_Tracking_Categories, Journal_Line_Tracking_Categories_Options, Journal_Lines, Journals, Manual_Journal_Line_Tracking, Manual_Journal_Lines, Manual_Journals, Organisation_Addresses, Organisation_External_Links, Organisation_Phones, Organisations, Overpayment_Line_Items, Overpayment_Line_Items_Tracking, Overpayments, Overpayments_Allocations, Payments, Prepayment_Line_Item_Tracking, Prepayment_Line_Items, Prepayments, Prepayments_Allocations, ProjectTasks, ProjectUsers, Projects, Purchase_Order_Line_Item_Tracking, Purchase_Order_Line_Items, Purchase_Orders, Quotes, Receipt_Line_Item_Tracking, Receipt_Line_Items, Receipt_Validation_Errors, Receipts, Repeating_Invoice_Line_Item_Tracking, Repeating_Invoice_Line_Items, Repeating_Invoices, Statements, Tax_Rate_Tax_Components, Tax_Rates, Time, Tracking_Categories, Tracking_Category_Options, Users. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.62 or above. |
91
+
| [Xero](connector-xero.md) | Scenario that doesn't rely on below capability in Xero (version 1.0):<br><br>• Use OAuth 1.0 authentication type. <br><br>The following Xero tables are supported for automatic upgrade: <br><br>Accounts, AssetSettings, AssetTypes, Associations, Bank_Transaction_Line_Item_Tracking, Bank_Transaction_Line_Items, Bank_Transactions, Bank_Transfers, BankFeedConnections, Branding_Themes, Budgets, Contact_Group_Contacts, Contact_Groups, Contacts, Contacts_Addresses, Contacts_Contact_Persons, Contacts_Phones, Contacts_Purchases_Tracking_Categories, Contacts_Sales_Tracking_Categories, Credit_Note_Line_Items, Credit_Notes, Credit_Notes_Allocations, Credit_Notes_Line_Items_Tracking, Currencies, Employees, Expense_Claim_Payments, Expense_Claim_Receipts, Expense_Claim_Validation_Errors, Expense_Claims, Files, Folders, Invoice_Line_Items, Invoices, Invoices_Credit_Notes, Invoices_Line_Items_Tracking, Invoices_Overpayments, Invoices_Prepayments, Items, Journal_Line_Tracking_Categories, Journal_Line_Tracking_Categories_Options, Journal_Lines, Journals, Manual_Journal_Line_Tracking, Manual_Journal_Lines, Manual_Journals, Organisation_Addresses, Organisation_External_Links, Organisation_Phones, Organisations, Overpayment_Line_Items, Overpayment_Line_Items_Tracking, Overpayments, Overpayments_Allocations, Payments, Prepayment_Line_Item_Tracking, Prepayment_Line_Items, Prepayments, Prepayments_Allocations, ProjectTasks, ProjectUsers, Projects, Purchase_Order_Line_Item_Tracking, Purchase_Order_Line_Items, Purchase_Orders, Quotes, Receipt_Line_Item_Tracking, Receipt_Line_Items, Receipt_Validation_Errors, Receipts, Repeating_Invoice_Line_Item_Tracking, Repeating_Invoice_Line_Items, Repeating_Invoices, Statements, Tax_Rate_Tax_Components, Tax_Rates, Time, Tracking_Categories, Tracking_Category_Options, Users. <br><br>If your pipeline runs on self-hosted integration runtime, it requires SHIR version 5.62 or above. |
0 commit comments