Skip to content

Repo sync for protected branch #2646

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
Jun 6, 2025
Merged

Repo sync for protected branch #2646

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f7cd19f
(AzureCXP) fixes MicrosoftDocs/dataexplorer-docs-pr#439080
TPavanBalaji Jun 6, 2025
1529669
Merge pull request #6907 from TPavanBalaji/patch-18
prmerger-automator[bot] Jun 6, 2025
2a126c9
Merge pull request #6908 from MicrosoftDocs/main
Taojunshen Jun 6, 2025
ce009e0
Merging changes synced from https://github.com/MicrosoftDocs/dataexpl…
Jun 6, 2025
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
2 changes: 1 addition & 1 deletion data-explorer/kusto/management/dup-next-ingest.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ ms.date: 08/11/2024

Use the `.dup-next-ingest` command for on-demand troubleshooting of your data ingestion pull flow.

Run `.dup-next-ingest` before the ingestion you wish to watch. After running the command, the successfully downloaded ingestion source file(s) and a file containing metadata on the ingestion request will be uploaded to the specified storage container. Since this command only watches one subsequent ingestion, run this command each time you want to watch the next ingestion.
Run `.dup-next-ingest` before starting the ingestion you want to monitor. After running the command, the successfully downloaded ingestion source file(s) and a file containing metadata on the ingestion request will be uploaded to the specified storage container. Since this command only watches one subsequent ingestion, run this command each time you want to watch the next ingestion.

The file uploads to the storage container and the ingestion are performed by the same node. If there are admin node changes between running the command and the next ingestion, you'll need to rerun the command since the duplication configuration isn't persisted. Watch the storage container to know when the duplication is completed.

Expand Down