Merge pull request #296402 from MicrosoftDocs/main

PhilKang0704 · web-flow · commit 49e059f1458f · 2025-03-17T13:31:44.000+08:00
3/17/2025 11:00 AM IST Publish
diff --git a/articles/azure-sql-edge/deploy-onnx.md b/articles/azure-sql-edge/deploy-onnx.md
@@ -2,9 +2,9 @@
 title: Deploy and make predictions with ONNX
 titleSuffix: SQL machine learning
 description: Learn how to train a model, convert it to ONNX, deploy it to Azure SQL Edge, and then run native PREDICT on data using the uploaded ONNX model.
-author: WilliamDAssafMSFT
-ms.author: wiassaf
-ms.reviewer: hudequei, randolphwest
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: hudequei, vanto
 ms.date: 09/21/2024
 ms.service: sql
 ms.subservice: machine-learning
diff --git a/articles/azure-sql-edge/onnx-overview.md b/articles/azure-sql-edge/onnx-overview.md
@@ -1,9 +1,9 @@
 ---
 title: Machine learning and AI with ONNX in Azure SQL Edge
 description: Machine learning in Azure SQL Edge supports models in the Open Neural Network Exchange (ONNX) format. ONNX is an open format you can use to interchange models between various machine learning frameworks and tools.
-author: WilliamDAssafMSFT
-ms.author: wiassaf
-ms.reviewer: hudequei, randolphwest
+author: rwestMSFT
+ms.author: randolphwest
+ms.reviewer: hudequei, vanto, kendalv
 ms.date: 09/21/2024
 ms.service: azure-sql-edge
 ms.subservice: machine-learning
diff --git a/articles/data-factory/connector-cassandra.md b/articles/data-factory/connector-cassandra.md
@@ -6,7 +6,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 02/28/2025
+ms.date: 03/07/2025
 ms.author: jianleishen
 ---
 # Copy data from Cassandra using Azure Data Factory or Synapse Analytics
@@ -30,7 +30,7 @@ For a list of data stores that are supported as sources/sinks, see the [Supporte
 
 Specifically, this Cassandra connector supports:
 
-- Cassandra **versions 3.x.x and 4.x.x** for version 2.0. 
+- Cassandra **versions 3.x.x and 4.x.x** for version 2.0 (Preview). 
 - Cassandra **versions 2.x and 3.x** for version 1.0. 
 - Copying data using **Basic** or **Anonymous** authentication.
 
@@ -81,7 +81,7 @@ The following properties are supported for Cassandra linked service:
 | Property | Description | Required |
 |:--- |:--- |:--- |
 | type |The type property must be set to: **Cassandra** |Yes |
-| version | The version that you specify. The value is `2.0`. | Yes for version 2.0, not supported for version 1.0. |
+| version | The version that you specify. The value is `2.0`. | Yes for version 2.0 (Preview), not supported for version 1.0. |
 | host |One or more IP addresses or host names of Cassandra servers.<br/>Specify a comma-separated list of IP addresses or host names to connect to all servers concurrently. |Yes |
 | port |The TCP port that the Cassandra server uses to listen for client connections. |No (default is 9042) |
 | authenticationType | Type of authentication used to connect to the Cassandra database.<br/>Allowed values are: **Basic**, and **Anonymous**. |Yes |
@@ -233,20 +233,23 @@ If you use version 1.0 to copy data from Cassandra, set the source type in the c
 
 When copying data from Cassandra, the following mappings are used from Cassandra data types to interim data types used internally within the service. See [Schema and data type mappings](copy-activity-schema-and-type-mapping.md) to learn about how copy activity maps the source schema and data type to the sink.
 
-| Cassandra data type | Interim service data type (for version 2.0) | Interim service data type (for version 1.0) |
+| Cassandra data type | Interim service data type (for version 2.0 (Preview)) | Interim service data type (for version 1.0) |
 |:--- |:--- |:--- |
 | ASCII |String |String |
 | BIGINT |Int64 |Int64 |
 | BLOB |Byte[] |Byte[] |
 | BOOLEAN |Boolean |Boolean |
+| DATE | DateTime | DateTime |
 | DECIMAL |Decimal |Decimal |
 | DOUBLE |Double |Double |
 | FLOAT |Single |Single |
 | INET |String |String |
 | INT |Int32 |Int32 |
+| SMALLINT | Short | Int16 |
 | TEXT |String |String |
 | TIMESTAMP |DateTime |DateTime |
 | TIMEUUID |Guid |Guid |
+| TINYINT | SByte | Int16 |
 | UUID |Guid |Guid |
 | VARCHAR |String |String |
 | VARINT |Decimal |Decimal |
@@ -259,6 +262,26 @@ When copying data from Cassandra, the following mappings are used from Cassandra
 > The length of Binary Column and String Column lengths cannot be greater than 4000.
 >
 
+## Work with collections when using version 2.0 (Preview)
+
+When using version 2.0 (Preview) 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.
+
+### Example
+
+For example, the following "ExampleTable" is a Cassandra database table that contains an integer primary key column named "pk_int", a text column named value, a list column, a map column, and a set column (named "StringSet").
+
+| pk_int | Value | List | Map | StringSet |
+| --- | --- | --- | --- | --- |
+| 1 |"sample value 1" |["1", "2", "3"] |{"S1": "a", "S2": "b"} |{"A", "B", "C"} |
+| 3 |"sample value 3" |["100", "101", "102", "105"] |{"S1": "t"} |{"A", "E"} |
+
+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:
+
+| pk_int | Value | List | Map | StringSet |
+| --- | --- | --- | --- | --- |
+| 1 |"sample value 1" |["1", "2", "3"] |{"S1": "a", "S2": "b"} |["A", "B", "C"] |
+| 3 |"sample value 3" |["100", "101", "102", "105"] |{"S1": "t"} |["A", "E"] |
+
 ## Work with collections using virtual table when using version 1.0
 
 The service uses a built-in ODBC driver to connect to and copy data from your Cassandra database. For collection types including map, set and list, the driver renormalizes the data into corresponding virtual tables. Specifically, if a table contains any collection columns, the driver generates the following virtual tables:
@@ -324,25 +347,26 @@ The following tables show the virtual tables that renormalize the data from the
 
 To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
 
-## Differences between Cassandra version 2.0 and version 1.0 
+## Differences between Cassandra version 2.0 (Preview) and version 1.0 
 
-The Cassandra connector version 2.0 offers new functionalities and is compatible with most features of version 1.0. The table below shows the feature differences between version 2.0 and version 1.0. 
+The Cassandra connector version 2.0 (Preview) offers new functionalities and is compatible with most features of version 1.0. The table below shows the feature differences between version 2.0 (Preview) and version 1.0. 
 
-| version 2.0 | version 1.0 |
+| Version 2.0 (Preview) | Version 1.0 |
 | --- | --- |
 | Support CQL query. | Support SQL-92 query or CQL query. |
-| Support specifying `keyspace` and `tableName` separately in Cassandra dataset. | Support editing `keyspace` when you select enter manually table name in Cassandra dataset. |
-| There is no virtual tables for collection types. | For collection types (map, set, list, etc.), 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. |
+| Support specifying `keyspace` and `tableName` separately in dataset. | Support editing `keyspace` when you select enter manually table name in dataset. |
+| No virtual tables are created for collection types. For more information, see [Work with collections when using version 2.0 (Preview)](#work-with-collections-when-using-version-20-preview).  | 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). |
+| The following mappings are used from Cassandra data types to interim service data type. <br><br> SMALLINT -> Short <br> TINYINT -> SByte | The following mappings are used from Cassandra data types to interim service data type. <br><br> SMALLINT -> Int16 <br> TINYINT -> Int16 | 
 
 ## Upgrade the Cassandra connector
 
 Here are steps that help you upgrade the Cassandra connector:
 
-1. In **Edit linked service** page, select **2.0 (Preview)** under **Version** and configure the linked service by referring to [Linked service properties](#linked-service-properties).
+1. In **Edit linked service** page, select version 2.0 (Preview) and configure the linked service by referring to [Linked service properties](#linked-service-properties).
 
-2. If you use `query` in the copy activity source for version 2.0, see [Cassandra as source](#cassandra-as-source).
+2. In version 2.0 (Preview), the `query` in the copy activity source supports only CQL query, not SQL-92 query. For more information, see [Cassandra as source](#cassandra-as-source).
 
-3. The data type mapping for version 2.0 is different from that for version 1.0. To learn the latest data type mapping, see [Data type mapping for Cassandra](#data-type-mapping-for-cassandra).
+3. The data type mapping for version 2.0 (Preview) is different from that for version 1.0. To learn the latest data type mapping, see [Data type mapping for Cassandra](#data-type-mapping-for-cassandra). 
 
 ## Related content
 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).
diff --git a/articles/logic-apps/set-up-standard-workflows-hybrid-deployment-requirements.md b/articles/logic-apps/set-up-standard-workflows-hybrid-deployment-requirements.md
@@ -6,7 +6,7 @@ ms.service: azure-logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 03/10/2025
+ms.date: 03/13/2025
 # Customer intent: As a developer, I need to set up the requirements to host and run Standard logic app workflows on infrastructure that my organization owns, which can include on-premises systems, private clouds, and public clouds.
 ---
 
@@ -157,9 +157,10 @@ Your Kubernetes cluster requires inbound and outbound connectivity with the [SQL
    az login
    az account set --subscription $SUBSCRIPTION
    az provider register --namespace Microsoft.KubernetesConfiguration --wait
+   az provider register --namespace Microsoft.Kubernetes --wait
    az extension add --name k8s-extension --upgrade --yes
-   az group create
-      --name $AKS_CLUSTER_GROUP_NAME
+   az group create \
+      --name $AKS_CLUSTER_GROUP_NAME \
       --location $LOCATION
    az aks create \
       --resource-group $AKS_CLUSTER_GROUP_NAME \
@@ -179,7 +180,10 @@ Your Kubernetes cluster requires inbound and outbound connectivity with the [SQL
    For more information, see the following resources:
 
    - [Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using Azure CLI](/azure/aks/learn/quick-kubernetes-deploy-cli)
+   - [**az extension add**](/cli/azure/extension#az-extension-add)
+   - [Register the required namespaces](/azure/container-apps/azure-arc-enable-cluster?tabs=azure-cli#setup)
    - [**az account set**](/cli/azure/account#az-account-set)
+   - [**az provider register**](/cli/azure/provider#az-provider-register)
    - [**az group create**](/cli/azure/group#az-group-create)
    - [**az aks create**](/cli/azure/aks#az-aks-create)
 
@@ -219,6 +223,7 @@ To create your Azure Arc-enabled Kubernetes cluster, connect your Kubernetes clu
 
    ```azurecli
    az provider register --namespace Microsoft.ExtendedLocation --wait
+   az provider register --namespace Microsoft.Kubernetes --wait
    az provider register --namespace Microsoft.KubernetesConfiguration --wait
    az provider register --namespace Microsoft.App --wait
    az provider register --namespace Microsoft.OperationalInsights --wait
@@ -243,6 +248,24 @@ To create your Azure Arc-enabled Kubernetes cluster, connect your Kubernetes clu
    - [Set-ExecutionPolicy](/powershell/module/microsoft.powershell.security/set-executionpolicy)
    - [choco install kubernetes-cli](https://docs.chocolatey.org/en-us/choco/commands/install/)
 
+1. Test your connection to your cluster by getting the [**kubeconfig** file](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/):
+
+   ```azurecli
+   az aks get-credentials \
+      --resource-group $AKS_CLUSTER_GROUP_NAME \
+      --name $AKS_NAME \
+      --admin
+   kubectl get ns 
+   ```
+
+   By default, the **kubeconfig** file is saved to the path, **~/.kube/config**. This command applies to our example Kubernetes cluster and differs for other kinds of Kubernetes clusters.
+
+   For more information, see the following resources:
+
+   - [Create connected cluster](../container-apps/azure-arc-enable-cluster.md?tabs=azure-cli#create-a-connected-cluster)
+   - [**az aks get-credentials**](/cli/azure/aks#az-aks-get-credentials)
+   - [**kubectl get**](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_get/)
+
 1. Install the Kubernetes package manager named **Helm**:
 
    ```azurecli
@@ -280,24 +303,6 @@ To create your Azure Arc-enabled Kubernetes cluster, connect your Kubernetes clu
 
 ## Connect your Kubernetes cluster to Azure Arc
 
-1. Test your connection to your cluster by getting the [**kubeconfig** file](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/):
-
-   ```azurecli
-   az aks get-credentials \
-      --resource-group $AKS_CLUSTER_GROUP_NAME \
-      --name $AKS_NAME \
-      --admin
-   kubectl get ns 
-   ```
-
-   By default, the **kubeconfig** file is saved to the path, **~/.kube/config**. This command applies to our example Kubernetes cluster and differs for other kinds of Kubernetes clusters.
-
-   For more information, see the following resources:
-
-   - [Create connected cluster](../container-apps/azure-arc-enable-cluster.md?tabs=azure-cli#create-a-connected-cluster)
-   - [**az aks get-credentials**](/cli/azure/aks#az-aks-get-credentials)
-   - [**kubectl get**](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_get/)
-
 1. Based on your Kubernetes cluster deployment, set the following environment variable to provide a name to use for the Azure resource group that contains your Azure Arc-enabled cluster and resources:
 
    ```azurecli
