[kerthans]

Related Issues

• No existing issue. Follow-up to fix: DeleteAllAsyncTest, DeleteByFilterAsyncTest, #10952, which added delete_all_documents_async but not delete_by_filter_async.

Proposed Changes:

InMemoryDocumentStore exposes an async counterpart for every public method (update_by_filter_async, count_documents_by_filter_async, delete_all_documents_async, ...), except delete_by_filter. The shared DeleteByFilterAsyncTest mixin in haystack/testing/document_store_async.py already exists, but it was not mixed into TestMemoryDocumentStore, so the gap went unnoticed.

This PR:

• adds InMemoryDocumentStore.delete_by_filter_async(filters) -> int, which runs the existing sync delete_by_filter in the store's thread-pool executor, following the same pattern as update_by_filter_async;
• adds DeleteByFilterAsyncTest to TestMemoryDocumentStore;
• adds a release note.

How did you test it?

• Added DeleteByFilterAsyncTest first and confirmed the new tests failed with AttributeError: 'InMemoryDocumentStore' object has no attribute 'delete_by_filter_async'.
• After the implementation: pytest test/document_stores/test_in_memory.py → 384 passed, 8 skipped (the new tests run for both the shared and non-shared store test classes).
• ruff check ., ruff format --check ., codespell, reno lint, and mypy on the changed modules pass.

Notes for the reviewer

The change is purely additive and delegates to the existing sync delete_by_filter, so filter validation and ValueError behavior are identical.

AI assistance was used to prepare this change; I reviewed and tested it.

Checklist

• I have read the contributors guidelines and the code of conduct.
• I have added unit tests and updated the docstrings.
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I have documented my code.
• I have added a release note file, following the contributors guidelines.
• I have run the checks behind the pre-commit hooks and fixed any issue.

[vercel]

@kerthans is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[HaystackBot]

Hi @kerthans, thanks a lot for your contribution! 🙏

We noticed that the Contributor License Agreement (CLA) check (license/cla) hasn't passed yet, so we've temporarily moved this PR to draft and paused the review assignment.

To get your PR reviewed, please sign the CLA via the link in the license/cla check below (or in the CLA bot comment). As soon as the check turns green, this PR will automatically be marked ready for review again and a reviewer will be re-assigned.

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[HaystackBot]

Thanks for signing the CLA, @kerthans! 🎉 This PR is now ready for review again and the reviewer has been re-assigned.