-
Notifications
You must be signed in to change notification settings - Fork 10
Open
Description
I was thinking about a situation of doing a 'live' map-reduce operation — where you group multiple log values under a key (this is the map function, choosing the key), and then reducing to get the value for that key. In order to get the previous reduced value from the leveldb though, you would need to read the current value for this key, which is an async operation.
I have a feeling that it could get weird when you try to keep all the constraints we want, like atomic writes, and also optimizing the writes by batching a number of input values. I haven't thought this through too much yet, but figured it wouldn't hurt to think out loud.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels