[BUG]: Prevent hnsw cleanup if use_direct_hnsw is true

[tanujnay112]

Description of changes

As titled.

• Improvements & Bug fixes
  • ...
• New functionality
  • ...

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Migration plan

Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?

Observability plan

What is the plan to instrument and monitor this change?

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[tanujnay112]

• [BUG]: Prevent hnsw cleanup if use_direct_hnsw is true #5933 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[propel-code-bot]

Skip HNSW temporary directory purge when using direct HNSW

Adds an early return in CompactionContext::cleanup to avoid purging temporary HNSW directories when the provider is operating in direct/in-memory mode. Also exposes the use_direct_hnsw flag on HnswIndexProvider so callers can inspect the configuration before attempting cleanup.

Key Changes

• Return early from CompactionContext::cleanup when self.hnsw_provider.use_direct_hnsw is true
• Make HnswIndexProvider::use_direct_hnsw a public field for external checks

Affected Areas

• rust/worker/src/execution/orchestration/compact.rs
• rust/index/src/hnsw_provider.rs

This summary was automatically generated by @propel-code-bot