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
|*SerializedArrayOfPolicyObjects*|`string`|:heavy_check_mark:| A serialized array of JSON policy objects. See [callout policy](callout-policy.md) for policy properties. |
27
+
| Name | Type | Required | Description |
28
+
|--|--|--|--|
29
+
|*SerializedArrayOfPolicyObjects*|`string`|:heavy_check_mark:| A serialized array of JSON policy objects. See [callout policy](callout-policy.md) for policy properties. |
|*SerializedPartialPolicy*|`string`|:heavy_check_mark:| Define a serialized JSON policy. For policy properties, see [request classification policy](request-classification-policy.md). |
39
-
|*ClassificationFunctionBody*|`string`|:heavy_check_mark:| The body of the function to use for classifying requests.|
36
+
| Name | Type | Required | Description |
37
+
|--|--|--|--|
38
+
|*SerializedPartialPolicy*|`string`|:heavy_check_mark:| Define a serialized JSON policy. For policy properties, see [request classification policy](request-classification-policy.md). |
39
+
|*ClassificationFunctionBody*|`string`|:heavy_check_mark:| The body of the function to use for classifying requests. |
40
40
41
41
## Returns
42
42
43
43
:::moniker range="azure-data-explorer"
44
44
The command returns one row showing the details of the cluster request classification policy.
45
45
::: moniker-end
46
46
:::moniker range="microsoft-fabric"
47
-
The command returns one row showing the details of the eventhouse request classification policy.
47
+
The command returns one row showing the details of the Eventhouse request classification policy.
@@ -14,7 +14,7 @@ Changes the database streaming ingestion policy. The [streaming policy](../manag
14
14
15
15
Streaming ingestion is best suited for low latency scenarios where the ingestion time is under 10 seconds for varying data volume. It can optimize processing for multiple tables across one or more databases, especially when the tables receive only a few records per second but the ingestion volume is thousands of records per second.
16
16
17
-
However, when the amount of data grows beyond 4 Gb per hour per table, it's recommended to switch to classic bulk ingestion instead of streaming ingestion.
17
+
However, when the amount of data grows beyond 4 GB per hour per table, we recommend switching to classic bulk ingestion instead of streaming ingestion.
18
18
19
19
To learn how to implement streaming ingestion, see [streaming ingestion](/azure/data-explorer/ingest-data-streaming).
20
20
Streaming ingestion must be enabled at the cluster level before it can be used at the database level.
@@ -48,3 +48,12 @@ The following command enables streaming ingestion and determines the suggestion
0 commit comments