From 27581871dd2c4c0f776bb6b49c435348a505be7f Mon Sep 17 00:00:00 2001 From: Sreedhar Pelluru <6722422+spelluru@users.noreply.github.com> Date: Tue, 16 Jun 2026 14:23:45 -0400 Subject: [PATCH 1/2] Update continuous-data-export.md From 8cb00041bf5a6142b6dfc98f317eff6576ac7ef2 Mon Sep 17 00:00:00 2001 From: Sreedhar Pelluru <6722422+spelluru@users.noreply.github.com> Date: Tue, 16 Jun 2026 14:25:19 -0400 Subject: [PATCH 2/2] Fix formatting and clarify continuous export limitations --- .../kusto/management/data-export/continuous-data-export.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data-explorer/kusto/management/data-export/continuous-data-export.md b/data-explorer/kusto/management/data-export/continuous-data-export.md index b2c20e41c0..3d8af36a19 100644 --- a/data-explorer/kusto/management/data-export/continuous-data-export.md +++ b/data-explorer/kusto/management/data-export/continuous-data-export.md @@ -142,8 +142,8 @@ To define continuous export to a delta table, do the following steps: * The following formats are allowed on target tables: `CSV`, `TSV`, `JSON`, and `Parquet`. * Continuous export isn't designed to work over [materialized views](../materialized-views/materialized-view-overview.md), since a materialized view might be updated, while data exported to storage is always appended and never updated. -* Continuous export can't be created on [follower databases](/azure/data-explorer/follower) since follower databases are read-only and continuous export requires write operations. * Continuous export to `Parquet` can experience reduced performance for tables with a large number of columns due to per-column encoding overhead. +* Continuous export can't be created on [follower databases](/azure/data-explorer/follower) since follower databases are read-only and continuous export requires write operations. * Records in source table must be ingested to the table directly, using an [update policy](../update-policy.md), or [ingest from query commands](../data-ingestion/ingest-from-query.md). If records are moved into the table using [.move extents](../move-extents.md) or using [.rename table](../rename-table-command.md), continuous export might not process these records. See the limitations described in the [Database Cursors](../database-cursor.md#restrictions) page. * If the artifacts used by continuous export are intended to trigger Event Grid notifications, see the [known issues section in the Event Grid documentation](/azure/data-explorer/ingest-data-event-grid-overview#known-event-grid-issues).