Merging changes synced from https://github.com/MicrosoftDocs/dataexplorer-docs-pr (branch live)

Author: Learn Build Service GitHub App

data-explorer/includes/media/data-explorer-ingestion-wizard-types/from-container-with-filter.png

@@ -365,7 +365,7 @@ items:
     items:
     - name: Capacity policy
       href: /kusto/management/capacity-policy?view=azure-data-explorer&preserve-view=true
-      displayName: IngestionCapacity, ExtentsMergeCapacity, ExtentsPurgeRebuildCapacity, ExportCapacity, ExtentsPartitionCapacity, MaterializedViewsCapacity, StoredQueryResultsCapacity, ingestion, extents,
+      displayName: IngestionCapacity, ExtentsMergeCapacity, ExtentsPurgeRebuildCapacity, ExportCapacity, ExtentsPartitionCapacity, MaterializedViewsCapacity, StoredQueryResultsCapacity, QueryAccelerationCapacity, ingestion, extents,
         purge, partition
     - name: .alter cluster policy capacity command
       href: /kusto/management/alter-capacity-policy-command?view=azure-data-explorer&preserve-view=true

data-explorer/kusto-tocs/management/toc.yml

@@ -97,6 +97,10 @@ Alter the capacity policy. The resulting policy is the properties in the command
   },
   "PeriodicStorageArtifactsCleanupCapacity": {
     "MaximumConcurrentOperationsPerCluster": 1
+  },
+  "QueryAccelerationCapacity": {
+    "ClusterMaximumConcurrentOperations": 100,
+    "CoreUtilizationCoefficient": 0.5
   }
 },
 "ChildEntities": ,

data-explorer/kusto/functions-library/media/series-rate-fl/all-disks-write-rate-2-bins.png

@@ -26,6 +26,7 @@ The capacity policy is made of the following components:
 * [StreamingIngestionPostProcessingCapacity](#streaming-ingestion-post-processing-capacity)
 * [PurgeStorageArtifactsCleanupCapacity](#purge-storage-artifacts-cleanup-capacity)
 * [PeriodicStorageArtifactsCleanupCapacity](#periodic-storage-artifacts-cleanup-capacity)
+* [QueryAccelerationCapacity](#query-acceleration-capacity)
 
 To view the capacity of your cluster, use the [.show capacity](show-capacity-command.md) command.
 
@@ -179,6 +180,19 @@ The [.show capacity](show-capacity-command.md) command returns the cluster's per
 
 `MaximumConcurrentOperationsPerCluster`
 
+### Query Acceleration capacity
+
+| Property | Type | Description |
+|--|--|--|
+| `ClusterMaximumConcurrentOperations` | `long` | The maximum number of concurrent query acceleration caching operations in a cluster. This value caps the total query acceleration caching capacity, as shown in the following formula. |
+| `CoreUtilizationCoefficient` | `long` | Determines the percentage of cores to use in the query acceleration caching capacity calculation. |
+
+**Formula**
+
+The [.show capacity](show-capacity-command.md) command returns the cluster's query acceleration caching capacity based on the following formula:
+
+`Minimum(ClusterMaximumConcurrentOperations` `,` *Number of nodes in cluster* `*` `Maximum(1,` *Core count per node* `*`  `CoreUtilizationCoefficient))`
+
 ## Defaults
 
 The default capacity policy has the following JSON representation:
@@ -223,6 +237,10 @@ The default capacity policy has the following JSON representation:
   },
   "PeriodicStorageArtifactsCleanupCapacity": {
     "MaximumConcurrentOperationsPerCluster": 2
+  },
+  "QueryAccelerationCapacity": {
+    "ClusterMaximumConcurrentOperations": 100,
+    "CoreUtilizationCoefficient": 0.5
   }
 }
 ```
@@ -247,6 +265,8 @@ Kusto limits the number of concurrent requests for the following user-initiated
   * The [purge rebuild capacity](#extents-purge-rebuild-capacity) is used internally to determine the number of concurrent rebuild operations during purge commands. Purge commands aren't blocked or throttled because of this process, but completes faster or slower depending on the purge rebuild capacity.
 * **Exports**
   * The limit is as defined in the [export capacity](#export-capacity).
+* **Query Acceleration**
+  * The limit is as defined in the [query acceleration capacity](#query-acceleration-capacity).
 
 When the cluster detects that an operation exceeded the limit on concurrent requests:
 

data-explorer/kusto/management/alter-capacity-policy-command.md

@@ -29,11 +29,14 @@ To enable query acceleration in the Fabric UI, see [Query acceleration over OneL
 * The feature assumes delta tables with static advanced features, for example column mapping doesn't change, partitions don't change, and so on. To change advanced features, first disable the policy, and once the change is made, re-enable the policy.
 * Schema changes on the delta table must also be followed with the respective `.alter` external delta table schema, which might result in acceleration starting from scratch if there was breaking schema change.
 * Index-based pruning isn't supported for partitions.
-* Parquet files with a compressed size higher than 6 GB won't be cached.
+* Parquet files larger than 1 GB won't be cached.
 ::: moniker range="azure-data-explorer"
 * Query acceleration isn't supported for external tables with impersonation authentication.
 ::: moniker-end
 
+> [!NOTE]
+> The query acceleration caching operations are limited by the available query acceleration capacity of your cluster. Run the [.show capacity command](show-capacity-command.md) to view the total, consumed, and remaining query acceleration capacity.
+
 ## Known issues
 
 * Data in the external delta table that is optimized with the [OPTIMIZE](/azure/databricks/sql/language-manual/delta-optimize) function will need to be reaccelearted.

data-explorer/kusto/management/capacity-policy.md

@@ -367,7 +367,7 @@ items:
         items:
           - name: Capacity policy
             href: capacity-policy.md
-            displayName: IngestionCapacity, ExtentsMergeCapacity, ExtentsPurgeRebuildCapacity, ExportCapacity, ExtentsPartitionCapacity, MaterializedViewsCapacity, StoredQueryResultsCapacity, ingestion, extents, purge, partition
+            displayName: IngestionCapacity, ExtentsMergeCapacity, ExtentsPurgeRebuildCapacity, ExportCapacity, ExtentsPartitionCapacity, MaterializedViewsCapacity, StoredQueryResultsCapacity, QueryAccelerationCapacity, ingestion, extents, purge, partition
           - name: .alter cluster policy capacity command
             href: alter-capacity-policy-command.md
             displayName: .alter cluster capacity policy command

data-explorer/kusto/management/query-acceleration-policy.md

@@ -42,4 +42,4 @@ print result = regex_quote('(so$me.Te^xt)')
 
 | result |
 |---|
-| `\(so\\$me\\.Te\\^xt\\)` |
+| `\(so\$me\.Te\^xt\)` |