Skip to content

Commit d0937a3

Browse files
authored
Merge pull request #270110 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents bfcb097 + 428f2e5 commit d0937a3

File tree

6 files changed

+17
-9
lines changed

6 files changed

+17
-9
lines changed

articles/ai-services/language-service/question-answering/concepts/best-practices.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -63,9 +63,9 @@ Custom question answering provides the flexibility to use synonyms at the projec
6363

6464
For better relevance, you need to provide a list of acronyms that the end user intends to use interchangeably. The following is a list of acceptable acronyms:
6565

66-
`MSFT` – Microsoft
67-
`ID` – Identification
68-
`ETA` – Estimated time of Arrival
66+
* `MSFT` – Microsoft
67+
* `ID` – Identification
68+
* `ETA` – Estimated time of Arrival
6969

7070
Other than acronyms, if you think your words are similar in context of a particular domain and generic language models won’t consider them similar, it’s better to add them as synonyms. For instance, if an auto company producing a car model X receives queries such as “my car’s audio isn’t working” and the project has questions on “fixing audio for car X”, then we need to add ‘X’ and ‘car’ as synonyms.
7171

articles/ai-services/language-service/question-answering/tutorials/active-learning.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ curl "https://github.com/Azure-Samples/cognitive-services-sample-data-files/blob
4040

4141
## Import file
4242

43-
From the edit project pane for your project, select the `...` (ellipsis) icon from the menu > **Import questions and answers** > **Import as TSV**. The select **Choose file** to browse to the copy of `SampleActiveLearning.tsv` that you downloaded to your computer in the previous step, and then select done.
43+
From the edit project pane for your project, select the `...` (ellipsis) icon from the menu > **Import questions and answers** > **Import as TSV**. Then, select **Choose file** to browse to the copy of `SampleActiveLearning.tsv` that you downloaded to your computer in the previous step, and then select done.
4444

4545
> [!div class="mx-imgBorder"]
4646
> [ ![Screenshot of edit project menu bar with import as TSV option displayed.]( ../media/active-learning/import-questions.png) ]( ../media/active-learning/import-questions.png#lightbox)

articles/iot-operations/manage-mqtt-connectivity/howto-configure-availability-scale.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,10 +36,11 @@ The `cardinality` field is a nested field that has these subfields:
3636

3737
- `frontend`: This subfield defines the settings for the frontend pods, such as:
3838
- `replicas`: The number of frontend pods to deploy. This subfield is required if the `mode` field is set to `distributed`.
39+
- `workers`: The number of workers to deploy per frontend, currently it must be set to `1`. This subfield is required if the `mode` field is set to `distributed`.
3940
- `backendChain`: This subfield defines the settings for the backend chains, such as:
4041
- `redundancyFactor`: The number of data copies in each backend chain. This subfield is required if the `mode` field is set to `distributed`.
4142
- `partitions`: The number of partitions to deploy. This subfield is required if the `mode` field is set to `distributed`.
42-
- `workers`: The number of workers to deploy, currently it must be set to `1`. This subfield is required if the `mode` field is set to `distributed`.
43+
- `workers`: The number of workers to deploy per backend, currently it must be set to `1`. This subfield is required if the `mode` field is set to `distributed`.
4344

4445
## Configure memory profile
4546

articles/migrate/appcat/dotnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Use the following steps to install it from inside Visual Studio. Alternatively,
4444

4545
### Prerequisites
4646

47-
- .NET SDK
47+
- .NET SDK (6 or greater)
4848

4949
### Installation steps
5050

articles/stream-analytics/write-to-delta-lake.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,8 +84,7 @@ At the failure of schema conversion, the job behavior will follow the [output da
8484

8585
### Delta Log checkpoints
8686

87-
88-
The Stream Analytics job will create Delta Log checkpoints periodically.
87+
The Stream Analytics job will create [Delta Log checkpoints](https://github.com/delta-io/delta/blob/master/PROTOCOL.md#checkpoints-1) periodically in the V1 format. Delta Log checkpoints are snapshots of the Delta Table and will typically contain the name of the data file generated by the Stream Analytics job. If the amount of data files is large, then this will lead to large checkpoints which can cause memory issues in the Stream Analytics Job.
8988

9089
## Limitations
9190

@@ -100,6 +99,14 @@ The Stream Analytics job will create Delta Log checkpoints periodically.
10099
- Writing to existing tables of Writer Version 7 or above with writer features will fail.
101100
- Example: Writing to existing tables with [Deletion Vectors](https://github.com/delta-io/delta/blob/master/PROTOCOL.md#deletion-vectors) enabled will fail.
102101
- The exceptions here are the [changeDataFeed and appendOnly Writer Features](https://github.com/delta-io/delta/blob/master/PROTOCOL.md#valid-feature-names-in-table-features).
102+
- When a Stream Analytics job writes a batch of data to a Delta Lake, it can generate multiple [Add File Action](https://github.com/delta-io/delta/blob/master/PROTOCOL.md#add-file-and-remove-file). When there are too many Add File Actions generated for a single batch, a Stream Analytics Job can be stuck.
103+
- The number of Add File Actions generated are determined by a number of factors:
104+
- Size of the batch. This is determined by the data volume and the batching parameters [Minimum Rows and Maximum Time](https://learn.microsoft.com/azure/stream-analytics/blob-storage-azure-data-lake-gen2-output#output-configuration)
105+
- Cardinality of the [Partition Column values](https://learn.microsoft.com/azure/stream-analytics/write-to-delta-lake#delta-lake-configuration) of the batch.
106+
- To reduce the number of Add File Actions generated for a batch the following steps can be taken:
107+
- Reduce the batching configurations [Minimum Rows and Maximum Time](https://learn.microsoft.com/azure/stream-analytics/blob-storage-azure-data-lake-gen2-output#output-configuration)
108+
- Reduce the cardinality of the [Partition Column values](https://learn.microsoft.com/azure/stream-analytics/write-to-delta-lake#delta-lake-configuration) by tweaking the input data or choosing a different partition column
109+
- Stream Analytics jobs can only read and write single part V1 Checkpoints. Multi-part checkpoints and the Checkpoint V2 format are not supported.
103110

104111
## Next steps
105112

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.reviewer: mimckitt
1313
# Azure Virtual Machine Scale Set automatic OS image upgrades
1414

1515
> [!NOTE]
16-
> Many of the steps listed in this document apply to Virtual Machine Scale Sets using Uniform Orchestration mode. We recommend using Flexible Orchestration for new workloads. For more information, see [Orchesration modes for Virtual Machine Scale Sets in Azure](virtual-machine-scale-sets-orchestration-modes.md).
16+
> Many of the steps listed in this document apply to Virtual Machine Scale Sets using Uniform Orchestration mode. We recommend using Flexible Orchestration for new workloads. For more information, see [Orchestration modes for Virtual Machine Scale Sets in Azure](virtual-machine-scale-sets-orchestration-modes.md).
1717
1818
Enabling automatic OS image upgrades on your scale set helps ease update management by safely and automatically upgrading the OS disk for all instances in the scale set.
1919

0 commit comments

Comments
 (0)