fs: file-level metadata
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 144
- Avg merge
- 12h 21m
- Merged PRs (30d)
- 146
Description
PR #370 updated the metadata handling to clean things up for fd and entry level metadata. However, as #374 shows, we might also want to have per-file metadata handling (_especially_ necessary once we have more multi-process support).
Thus, we should implement per-file level metadata (thus, we'd have a 3-level metadata handling system; fd, entry, file).
There are some complexities to keep in mind about what happens due to layering and migrations. So for example, what if some metadata is stored on a lower layer, and then the file is migrated to an upper layer.
Related: read https://github.com/microsoft/litebox/pull/374#issuecomment-3340691733
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading PR #370 for the existing fd- and entry-level metadata handling, then review issue #374 and its linked discussion. Define how a third, per-file metadata level should interact with layering and migrations, including metadata stored on a lower layer before a file moves to an upper layer; done means those cases are handled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100