Currently, atomic mutations and checks are each limited to 10. This is very low and easily hit in a non-trivial atomic mutation.
The reason is likely to ensure performance. But it should be up to the user to decide if decreased performance is acceptable instead of an arbitrarily hard API limit that makes non-trivial atomic mutations impossible.
A workaround to chain multiple API calls besides being less performant and error prone can only increase the limit to 20 atomic mutations. 10 in the first call due to max 10 mutation limit, 10 in the second call due to max 10 check limit, since the checks are needed to ensure consistency with all previous mutations.
This makes it currently impossible to do any non-trivial atomic mutations with Deno KV.
Limited workaround to increase atomic mutations from 10 to 20, where the second call needs to add consistency checks for every mutation from the first call.
🔍
Type of feedback
General feedback
Description
Currently, atomic mutations and checks are each limited to 10. This is very low and easily hit in a non-trivial atomic mutation.
The reason is likely to ensure performance. But it should be up to the user to decide if decreased performance is acceptable instead of an arbitrarily hard API limit that makes non-trivial atomic mutations impossible.
A workaround to chain multiple API calls besides being less performant and error prone can only increase the limit to 20 atomic mutations. 10 in the first call due to max 10 mutation limit, 10 in the second call due to max 10 check limit, since the checks are needed to ensure consistency with all previous mutations.
This makes it currently impossible to do any non-trivial atomic mutations with Deno KV.
Steps to reproduce (if applicable)
Expected behavior (if applicable)
no error
Possible solution (if applicable)
Limited workaround to increase atomic mutations from 10 to 20, where the second call needs to add consistency checks for every mutation from the first call.
Additional context
No response