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]: FlinkRunner emits new output from Impulse after restoring from savepoint #30903

Closed
1 of 16 tasks
je-ik opened this issue Apr 9, 2024 · 0 comments · Fixed by #30905
Closed
1 of 16 tasks

[Bug]: FlinkRunner emits new output from Impulse after restoring from savepoint #30903

je-ik opened this issue Apr 9, 2024 · 0 comments · Fixed by #30905
Assignees

Comments

@je-ik
Copy link
Contributor

je-ik commented Apr 9, 2024

What happened?

Upon restoring from savepoint FlinkRunner emits new element from Impulse, which causes downstream SDF to be restarted from scratch.

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant