Problem: Replicas need to know when mutable cached objects (like snapshots) are stale, and identical commits can produce different snapshot bytes causing needless churn.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue does not identify any files, tests, or entry points. Start by mapping cachew's ETag and mutable-resource handling, then resolve whether caller-specified ETags or content-hash ETags plus a separate content SHA should be supported; done requires an agreed design and implementation scope.
Written by the indexing model from the issue text.
Description
Still open: Whether the caller-specified ETag approach is worth the added complexity vs. just living with content-hash ETags and solving dedup separately as a "content SHA" attribute on mutable resources.
Trade-offs of caller-specified ETags — Content-hash ETags are simpler (every cache layer just hashes on write, no caller involvement), but caller-specified ETags better solve the dedup problem. Downside: can't leverage native S3 ETags, and the caller or cache impl needs to generate/supply the ETag upfront.
Upstream ETag passthrough — An additional advantage of caller-specified ETags: when proxying to upstream servers like Artifactory, cachew can directly use their ETag end-to-end without recomputing anything.
- Dominant language
- Go
- Stars
- 41
- Forks
- 14
- Avg merge
- 19h 28m
- Merged PRs (30d)
- 3
Getting set up
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.
More from block/cachew
-
etag-range-followup
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
priority: low 🌱 type: enhancement 💅🏼
Difficulty 2/5 Half a day Newbie friendliness 84/100
nebari-dev/llm-serving-pack#199 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
area/helm kind/bug priority/backlog triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lexfrei/cloudflare-tunnel-gateway-controller#889 ·
Maintainers usually reply within 1 day
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 1/5 Under an hour Newbie friendliness 90/100
wavefnd/wave-platform#140 ·
-
compiler/runtime
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day