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-cassandra.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -262,9 +262,9 @@ When copying data from Cassandra, the following mappings are used from Cassandra
262
262
> The length of Binary Column and String Column lengths cannot be greater than 4000.
263
263
>
264
264
265
-
## Work with collections using original type when using version 2.0
265
+
## Work with collections when using version 2.0
266
266
267
-
There are no virtual tables for collection types, you can copy a source table to sink in its original type.
267
+
When using version 2.0 to copy data from your Cassandra database, no virtual tables for collection types are created. You can copy a source table to the sink in its original type in JSON format.
268
268
269
269
### Example
270
270
@@ -275,7 +275,7 @@ For example, the following "ExampleTable" is a Cassandra database table that con
No need to create any virtual tables. You can directly read data from a source table and treat complex type column values as its original type, as shown in the following table:
278
+
The data can be directly read from a source table, and the column values are preserved in their original types in JSON format, as illustrated in the following table:
279
279
280
280
| pk_int | Value | List | Map | StringSet |
281
281
| --- | --- | --- | --- | --- |
@@ -355,7 +355,7 @@ The Cassandra connector version 2.0 offers new functionalities and is compatible
355
355
| --- | --- |
356
356
| Support CQL query. | Support SQL-92 query or CQL query. |
357
357
| Support specifying `keyspace` and `tableName` separately in dataset. | Support editing `keyspace` when you select enter manually table name in dataset. |
358
-
|There are no virtual tables for collection types, refer to [Work with collections using original type when using version 2.0](#work-with-collections-using-original-type-when-using-version-20) section. |For collection types, refer to[Work with Cassandra collection types using virtual table when using version 1.0](#work-with-collections-using-virtual-table-when-using-version-10) section. |
358
+
|No virtual tables are created for collection types. For more information, see [Work with collections when using version 2.0](#work-with-collections-when-using-version-20) section. |Virtual tables are created for collection types. For more information, see[Work with Cassandra collection types using virtual table when using version 1.0](#work-with-collections-using-virtual-table-when-using-version-10) section. |
359
359
| The following mappings are used from Cassandra data types to interim service data type. <br><br> DATE -> IDate <br> SMALLINT -> Short <br> TINYINT -> SByte | The following mappings are used from Cassandra data types to interim service data type. <br><br> DATE -> DateTime <br> SMALLINT -> Int16 <br> TINYINT -> Int16 |
0 commit comments