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-impala.md
+100-1Lines changed: 100 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: jianleishen
6
6
ms.subservice: data-movement
7
7
ms.custom: synapse
8
8
ms.topic: conceptual
9
-
ms.date: 10/20/2023
9
+
ms.date: 06/05/2025
10
10
ms.author: jianleishen
11
11
---
12
12
# Copy data from Impala using Azure Data Factory or Synapse Analytics
@@ -15,6 +15,9 @@ ms.author: jianleishen
15
15
16
16
This article outlines how to use Copy Activity in an Azure Data Factory or Synapse Analytics pipeline to copy data from Impala. It builds on the [Copy Activity overview](copy-activity-overview.md) article that presents a general overview of the copy activity.
17
17
18
+
> [!IMPORTANT]
19
+
> The Impala connector version 2.0 (Preview) provides improved native Impala support. If you are using the Impala connector version 1.0 in your solution, please [upgrade your Impala connector](#upgrade-the-impala-connector) before **September 30, 2025**. Refer to this [section](#differences-between-impala-version-20-and-version-10) for details on the difference between version 2.0 (Preview) and version 1.0.
20
+
18
21
## Supported capabilities
19
22
20
23
This Impala connector is supported for the following capabilities:
@@ -67,6 +70,62 @@ The following sections provide details about properties that are used to define
67
70
68
71
## Linked service properties
69
72
73
+
The Impala connector now supports version 2.0 (Preview). Refer to this [section](#upgrade-the-impala-connector) to upgrade your Impala connector version from version 1.0. For the property details, see the corresponding sections.
74
+
75
+
-[Version 2.0 (Preview)](#version-20)
76
+
-[Version 1.0](#version-10)
77
+
78
+
### <aname="version-20"></a> Version 2.0 (Preview)
79
+
80
+
The Impala linked service supports the following properties when apply version 2.0 (Preview):
81
+
82
+
| Property | Description | Required |
83
+
|:--- |:--- |:--- |
84
+
| type | The type property must be set to **Impala**. | Yes |
85
+
| version | The version that you specify. The value is `2.0`. | Yes |
86
+
| host | The IP address or host name of the Impala server (that is, 192.168.222.160). | Yes |
87
+
| port | The TCP port that the Impala server uses to listen for client connections. The default value is 21050. | No |
88
+
| thriftTransportProtocol | The transport protocol to use in the Thrift layer. Allowed values are: **Binary**, **HTTP**. The default value is Binary. | Yes |
89
+
| authenticationType | The authentication type to use. <br/>Allowed values are **Anonymous** and **UsernameAndPassword**. | Yes |
90
+
| username | The user name used to access the Impala server. | No |
91
+
| password | The password that corresponds to the user name when you use UsernameAndPassword. Mark this field as a SecureString to store it securely, or [reference a secret stored in Azure Key Vault](store-credentials-in-key-vault.md). | No |
92
+
| enableSsl | Specifies whether the connections to the server are encrypted by using TLS. The default value is true. | No |
93
+
| enableServerCertificateValidation | Specify whether to enable server SSL certificate validation when you connect. Always use System Trust Store. The default value is true. | No |
94
+
| connectVia | The [integration runtime](concepts-integration-runtime.md) to be used to connect to the data store. Learn more from [Prerequisites](#prerequisites) section. If not specified, it uses the default Azure Integration Runtime. |No |
95
+
96
+
**Example:**
97
+
98
+
```json
99
+
{
100
+
"name": "ImpalaLinkedService",
101
+
"properties": {
102
+
"type": "Impala",
103
+
"version": "2.0",
104
+
"typeProperties": {
105
+
"host" : "<host>",
106
+
"port" : "<port>",
107
+
"authenticationType" : "UsernameAndPassword",
108
+
"username" : "<username>",
109
+
"password": {
110
+
"type": "SecureString",
111
+
"value": "<password>"
112
+
},
113
+
"enableSsl": true,
114
+
"thriftTransportProtocol": "Binary",
115
+
"enableServerCertificateValidation": true
116
+
},
117
+
"connectVia": {
118
+
"referenceName": "<name of Integration Runtime>",
119
+
"type": "IntegrationRuntimeReference"
120
+
}
121
+
}
122
+
}
123
+
```
124
+
125
+
### Version 1.0
126
+
127
+
The following properties are supported for Impala linked service when apply version 1.0:
128
+
70
129
The following properties are supported for Impala linked service.
71
130
72
131
| Property | Description | Required |
@@ -184,10 +243,50 @@ To copy data from Impala, set the source type in the copy activity to **ImpalaSo
184
243
]
185
244
```
186
245
246
+
## Data type mapping for Impala
247
+
248
+
When you copy data from and to Impala, the following interim data type mappings are used within the service. To learn about how the copy activity maps the source schema and data type to the sink, see [Schema and data type mappings](copy-activity-schema-and-type-mapping.md).
249
+
250
+
| Impala data type | Interim service data type (for version 2.0 (Preview)) | Interim service data type (for version 1.0) |
251
+
|:--- |:--- |:--- |
252
+
| ARRAY | String | String |
253
+
| BIGINT | Int64 | Int64 |
254
+
| BOOLEAN | Boolean | Boolean |
255
+
| CHAR | String | String |
256
+
| DATE | DateTime | DateTime |
257
+
| DECIMAL | Decimal | Decimal |
258
+
| DOUBLE | Double | Double |
259
+
| FLOAT | Single | Single |
260
+
| INT | Int32 | Int32 |
261
+
| MAP | String | String |
262
+
| SMALLINT | Int16 | Int16 |
263
+
| STRING | String | String |
264
+
| STRUCT | String | String |
265
+
| TIMESTAMP | DateTimeOffset | DateTime |
266
+
| TINYINT | SByte | Int16 |
267
+
| VARCHAR | String | String |
268
+
187
269
## Lookup activity properties
188
270
189
271
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
190
272
273
+
## Upgrade the Impala connector
274
+
275
+
Here are steps that help you upgrade the Impala connector:
276
+
277
+
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).
278
+
279
+
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).
280
+
281
+
## <aname="differences-between-impala-version-20-and-version-10"></a> Differences between Impala version 2.0 (Preview) and version 1.0
282
+
283
+
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.
284
+
285
+
| Version 2.0 (Preview) | Version 1.0 |
286
+
|:--- |:--- |
287
+
| SASLUsername authentication type is not supported. | Support SASLUsername authentication type. |
288
+
| 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. |
289
+
| 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 |
191
290
192
291
## Related content
193
292
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).
0 commit comments