Add force_map_call option to get, delete and other crud methods
Open
Nobody has claimed this yet.
customer
feature
- Dominant language
- Lua
- Stars
- 43
- Forks
- 17
- Avg merge
- 28m
- Merged PRs (30d)
- 2
Description
In cases when sharding_keys and primary key parts are not the same it's quite annoying to point primary keys and sharding keys to perform get, delete and other operations so seems it's time to implement map_call for get, delete and other crud methods when force_map_call=true.
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
Start by tracing the existing get, delete, and other CRUD entry points that handle sharding_keys and primary keys. Determine how force_map_call should affect those operations when the key parts differ, then define coverage for the option across the affected methods; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- backend-api-design, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100