Always process the freshest record when ordered by key #902
Description
Hello, I have a use case where I need to process each key sequentially however when processing a record, if new records arrive for that key, I would like to skip over the ones that have already arrives and process the latest one next.
I tried to read and understand the documentation but I believe currently the library does not support this kind of behavior. Am I wrong? If not, is there a not so hacky way to achieve this?