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

bug(engine): collector cannot be used after a SHUFFLE step #181

Open
leosmerling-hopeit opened this issue Apr 9, 2024 · 0 comments
Open

Comments

@leosmerling-hopeit
Copy link
Collaborator

leosmerling-hopeit commented Apr 9, 2024

There might be cases where in a list of steps, a collector step is needed for async concurrent execution of tasks.
Collector allows these, but it was intended only to work as the initial step for an event.
There is a case though, that sequential steps need to be executed before the collector, and a SHUFFLE could be
interleaved to distribute the execution. In this case the engine fails to call the collector with the deserialized payload
from a stream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant