Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Committable in place of CommittableOffset #96

Closed
blublinsky opened this issue Dec 23, 2019 · 7 comments
Closed

Using Committable in place of CommittableOffset #96

blublinsky opened this issue Dec 23, 2019 · 7 comments
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/enhancement New feature or request. priority/backlog Normal priority item. status:backlog Item has not been started and it is part of the backlog. It may require discussion to become ready.
Milestone

Comments

@blublinsky
Copy link

blublinsky commented Dec 23, 2019

Is your feature request related to a problem? Please describe.
Currently flowWithOffsetContext[T] is accepting CommittableOffset, which prevents one from introduction internal events (for example, timer) and still have input events commitable

Is your feature request related to a specific runtime of cloudflow or applicable for all runtimes?
This is only relevant for Akka Streams

Describe the solution you'd like
I would like flowWithOffsetContext[T] to accept Committable, so that for internal events I can use (v, CommittableOffsetBatch.empty) and I can merge internal and external events

Describe alternatives you've considered
The only alternative currently is to use plainSink, which means that kafka events are not committed and restartability of streamlet does not work

Additional context
None

@agemooij agemooij added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/enhancement New feature or request. priority/backlog Normal priority item. status:backlog Item has not been started and it is part of the backlog. It may require discussion to become ready. labels Jan 6, 2020
@agemooij agemooij added this to the 1.3.1 milestone Jan 6, 2020
@osleonard
Copy link
Contributor

Is someone working on this ?

@olofwalker
Copy link
Contributor

@osleonard I think @RayRoestenburg completed work on this but never closed the ticket.

@RayRoestenburg
Copy link
Contributor

RayRoestenburg commented Feb 7, 2020 via email

@RayRoestenburg
Copy link
Contributor

RayRoestenburg commented Feb 7, 2020 via email

@osleonard
Copy link
Contributor

Haa ok will look for something else to pick in the backlog :)

@RayRoestenburg
Copy link
Contributor

RayRoestenburg commented Feb 7, 2020 via email

@RayRoestenburg
Copy link
Contributor

This issue is linked to #100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. kind/enhancement New feature or request. priority/backlog Normal priority item. status:backlog Item has not been started and it is part of the backlog. It may require discussion to become ready.
Projects
None yet
Development

No branches or pull requests

5 participants