Skip to content

Repo sync for protected branch #2949

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 4 commits into from
Oct 19, 2026
Merged

Repo sync for protected branch #2949

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c1b8771
remove dedup promise from EG
Oct 19, 2026
72fcd96
Merge pull request #7622 from LeaShallev/user/leshalev/eg_remove_dedu…
prmerger-automator[bot] Oct 19, 2026
a5ebdff
Merge pull request #7623 from MicrosoftDocs/main
learn-build-service-prod[bot] Oct 19, 2026
797fc02
Merging changes synced from https://github.com/MicrosoftDocs/dataexpl…
Oct 19, 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
1 change: 0 additions & 1 deletion data-explorer/ingest-data-event-grid-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading