meilisearch/MeiliSearch

Make sure payloads are effectively deleted on error

Open

#6,048 opened on Dec 11, 2025

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Rust (2,542 forks)batch import
Internal workaffects costsbuggood first issue

Repository metrics

Stars
 (57,572 stars)
PR merge metrics
 (Avg merge 11d 20h) (41 merged PRs in 30d)

Description

We found out that some payloads are not removed from the disk when an error occurs before we are able to put them in the FileStore. I would suggest we should create a temporary temporary file and extract it at the last moment.

Originally posted by @Kerollmops in https://github.com/meilisearch/meilisearch/pull/6000#discussion_r2602149151

Contributor guide

Research direction
Investigate where payloads are written and ensure cleanup on error. Implement a temp file strategy that moves to final location only on success.
Tech stack
rust
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustFile I/O
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60