Skip to content
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.

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

[BUG] build_disk_index does not delete the mem_index.data files for one-shot build #555

Open
gopalrs opened this issue May 17, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@gopalrs
Copy link
Contributor

gopalrs commented May 17, 2024

As explained above, the mem_index* files remain after the disk index is created, unnecessarily consuming disk space.
This doesn't happen with sharded build.

@gopalrs gopalrs added the bug Something isn't working label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant