Skip to content

Always process the freshest record when ordered by key #902

@mert-kirpici

Description

@mert-kirpici

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions