mapbox / mapbox/tilelive-multicache
Handle long keys in memcache
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Memcache has a 250 character key limit. If we continue to use memcache we should have a better sense of what happens when key is over this length, as well as have a sense of how often it happens. Currently any operation on long key will fail, be logged and we'll fall back to non-cached behavior.
If we want to support long keys we'll need to add mapping records based on a hash of the long key and indicate where the real key lives. However, first things first:
- [ ] Add test for long keys
- [ ] Determine if we have any super long keys
- [ ] [Maybe] support long keys
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 locating the memcache key handling and the existing tests for cache operations. Add coverage for keys over 250 characters, then inspect available usage or logs to determine whether such keys occur. Done means the long-key behavior is tested and its frequency is understood; support for long keys remains optional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, memcached
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100