Skip to content

Repo sync for protected branch #2845

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
learn-build-service-prod merged 6 commits into from
Feb 11, 2026
Merged

Repo sync for protected branch #2845

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
b1e8dac
Add Python plugin as a limitation for UP
vplauzon Feb 10, 2026
c38b725
.
vplauzon Feb 10, 2026
b7336f6
.
vplauzon Feb 11, 2026
d9a45a5
Fix Python plugin link in ingestion documentation
spelluru Feb 11, 2026
1fc6308
Merge pull request #7328 from vplauzon/vpl/up-python-streaming
JillGrant615 Feb 11, 2026
f8ea5da
Merge pull request #7378 from MicrosoftDocs/main
learn-build-service-prod[bot] Feb 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions data-explorer/ingest-data-streaming.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: Configure Streaming Ingestion on Your Azure Data Explorer Cluster
description: Learn how to configure your Azure Data Explorer cluster and start loading data with streaming ingestion.
ms.reviewer: alexefro
ms.topic: how-to
ms.date: 07/30/2025
ms.date: 02/10/2026
---

# Configure streaming ingestion on your Azure Data Explorer cluster
Expand Down Expand Up @@ -560,9 +560,11 @@ class Program

* [Data mappings](/kusto/management/mappings?view=azure-data-explorer&preserve-view=true) must be [pre-created](/kusto/management/create-ingestion-mapping-command?view=azure-data-explorer&preserve-view=true) for use in streaming ingestion. Individual streaming ingestion requests don't accommodate inline data mappings.
* [Extent tags](/kusto/management/extent-tags?view=azure-data-explorer&preserve-view=true) can't be set on the streaming ingestion data.
* [Update policy](/kusto/management/update-policy?view=azure-data-explorer&preserve-view=true). The update policy can reference only the newly ingested data in the source table and not any other data or tables in the database.
* For cascading [update policies](/kusto/management/update-policy?view=azure-data-explorer&preserve-view=true) that include a `join` operator, you must disable streaming ingestion on all upstream tables. For example, consider cascading update policies where Table1 updates Table2, Table2 updates Table3, and Table3 updates Table4. If Table4's update policy includes a join, you must disable streaming ingestion on Table1, Table2, and Table3.
* When an update policy with a [transactional policy](/kusto/management/update-policy?view=azure-data-explorer&preserve-view=true#handling-failures) fails, the retries fall back to batch ingestion.
* [Update policy](/kusto/management/update-policy?view=azure-data-explorer&preserve-view=true)
* The update policy can only reference newly ingested data in the source table and not any other data or tables in the database
* [Python plugin](/kusto/query/python-plugin) isn't supported
* When an update policy with a [transactional policy](/kusto/management/update-policy?view=azure-data-explorer&preserve-view=true#handling-failures) fails, the retries fall back to batch ingestion.
* For cascading [update policies](/kusto/management/update-policy?view=azure-data-explorer&preserve-view=true) that include a `join` operator, you must disable streaming ingestion on all upstream tables. For example, consider cascading update policies where Table1 updates Table2, Table2 updates Table3, and Table3 updates Table4. If Table4's update policy includes a join, you must disable streaming ingestion on Table1, Table2, and Table3.
* If streaming ingestion is enabled on a cluster used as a leader for [follower databases](follower.md), streaming ingestion must be enabled on the following clusters as well to follow streaming ingestion data. Same applies whether the cluster data is shared via [Data Share](data-share.md).

## Related content
Expand Down