Skip to content

Fix AOSS delete-by-query pagination and progress logging - #303

Merged
jordanpadams merged 1 commit into
mainfrom
302-fix-aoss-dbq-pagination
Jul 21, 2026
Merged

Fix AOSS delete-by-query pagination and progress logging#303
jordanpadams merged 1 commit into
mainfrom
302-fix-aoss-dbq-pagination

Conversation

@jordanpadams

Copy link
Copy Markdown
Member

Summary

  • RestClientWrapper._performDBQRequest(): loop until the search page is empty rather than doing a single pass. AOSS eventual consistency means deleted docs remain visible to subsequent searches, so a single-pass search-then-delete silently leaves documents behind on every call.
  • Adds INFO-level progress logging (one line per batch of deletes); per-doc detail at DEBUG.

Test plan

  • Run registry-manager delete-dd -ns <namespace> against an AOSS node with multiple pages of docs for that namespace and confirm all are deleted (count reaches 0 and stays there)
  • Confirm no change in behaviour against a standard Elasticsearch/OpenSearch node

Fixes #302

🤖 Generated with Claude Code

AOSS eventual consistency means deleted docs can still appear in the
next search immediately after deletion, so a single-pass search-then-
delete only removes one page and reports success. Loop until the search
returns an empty page to guarantee full deletion.

Also adds INFO-level progress logging (one line per batch) and drops
redundant page-number messages to DEBUG.

Fixes #302

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@jordanpadams
jordanpadams merged commit d2f9e08 into main Jul 21, 2026
6 checks passed
@jordanpadams
jordanpadams deleted the 302-fix-aoss-dbq-pagination branch July 21, 2026 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant