Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
…orer-docs-pr (branch live)
  • Loading branch information
Learn Build Service GitHub App authored and Learn Build Service GitHub App committed Dec 18, 2024
2 parents 9d82e1d + aab04e0 commit e263b2e
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions data-explorer/kusto/management/update-policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: Update policy overview
description: Learn how to trigger an update policy to add data to a source table.
ms.reviewer: orspodek
ms.topic: reference
ms.date: 08/11/2024
ms.date: 12/18/2024
---
# Update policy overview

Expand All @@ -21,7 +21,7 @@ The following diagram depicts a high-level view of an update policy. It shows tw
An update policy is subject to the same restrictions and best practices as regular ingestion. The policy scales-out according to the cluster size, and is more efficient when handling bulk ingestion.
::: moniker-end
:::moniker range="microsoft-fabric"
An update policy is subject to the same restrictions and best practices as regular ingestion. The policy scales-out according to the eventhouse size, and is more efficient when handling bulk ingestion.
An update policy is subject to the same restrictions and best practices as regular ingestion. The policy scales-out according to the Eventhouse size, and is more efficient when handling bulk ingestion.
::: moniker-end

> [!NOTE]
Expand All @@ -38,6 +38,7 @@ If the update policy is defined on the target table, multiple queries can run on
### Query limitations

:::moniker range="azure-data-explorer"

* The policy-related query can invoke stored functions, but:
* It can't perform cross-cluster queries.
* It can't access external data or external tables.
Expand All @@ -51,7 +52,7 @@ If the update policy is defined on the target table, multiple queries can run on
* It can't access external data or external tables.
* It can't make callouts (by using a plugin).
* The query doesn't have read access to tables that have the [RestrictedViewAccess policy](restricted-view-access-policy.md) enabled.
* For update policy limitations in streaming ingestion, see [streaming ingestion limitations](/azure/data-explorer/ingest-data-streaming#limitations).
* By default, the [Streaming ingestion policy](streaming-ingestion-policy.md) is enabled for all tables in the Eventhouse. To use functions with the [`join`](../query/join-operator.md) operator in an update policy, the streaming ingestion policy must be disabled. Use the `.alter` `table` *TableName* `policy` `streamingingestion` *PolicyObject* command to disable it.
::: moniker-end

> [!WARNING]
Expand Down

0 comments on commit e263b2e

Please sign in to comment.