From c1b87719b540961122d34c2ac3f30a61a19873bd Mon Sep 17 00:00:00 2001 From: Lea Shalev Date: Mon, 19 Oct 2026 10:57:38 +0300 Subject: [PATCH] remove dedup promise from EG --- data-explorer/ingest-data-event-grid-overview.md | 1 - 1 file changed, 1 deletion(-) diff --git a/data-explorer/ingest-data-event-grid-overview.md b/data-explorer/ingest-data-event-grid-overview.md index 5dd9aff176..f4018f2620 100644 --- a/data-explorer/ingest-data-event-grid-overview.md +++ b/data-explorer/ingest-data-event-grid-overview.md @@ -127,7 +127,6 @@ You can create a blob from a local file, set ingestion properties to the blob me > * Triggering ingestion following a `CopyBlob` operation isn't supported for storage accounts that have the hierarchical namespace feature enabled on them. > * When the event hub endpoint doesn't acknowledge receipt of an event, Azure Event Grid activates a retry mechanism. If this retry delivery fails, Event Grid can deliver the undelivered events to a storage account using a process of *dead-lettering*. For more information, see [Event Grid message delivery and retry](/azure/event-grid/delivery-and-retry#retry-schedule-and-duration). > * Using the "OpenWrite" API to write to a blob isn't recommended, as it triggers a notification for an empty blob and causes an empty-blob error. Additionally, flush the stream only once to prevent duplicate notifications and multiple ingestions of the same blob. -> * Azure Data Explorer tries to filter out duplicate notifications for the same blob sent by upstream services like Event Grid or Storage. When it detects a duplicate event, it skips ingestion and logs the error `BlobAlreadyReceived_DuplicateEventGridNotification`, which means the blob is already processed. ## Rename blobs