datafusion-contrib / datafusion-contrib/liquid-cache
Current focus of LiquidCache: reliability
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 452
- Forks
- 51
- Avg merge
- 3h 10m
- Merged PRs (30d)
- 12
Description
Thank you for your attention on this!
The current development theme of LiquidCache is reliability.
There're three lines of work going forward:
- Polish existing features so that they works as intended. We will add tests, add fuzzing, add verifications, restructure code, fix bugs, fix regressions.
- We'll improve LiquidCache observability. Allow users to understand exactly what's going on with LiquidCache states, see how cached data changes its states, see where LiquidCache spends most memory and CPU.
- We'll explore determinism. We'd like to explore ways to provide deterministic concurrency and deterministic IO, such that with the same input and hardware, user should expect exact same output and performance.
Let me know your thoughts below!
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Read the discussion and choose one narrowly scoped reliability task from the three proposed workstreams; define its expected behavior and verification before starting. Done should mean that the selected task has a concrete scope and tests or other checks demonstrating the intended reliability improvement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100