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.

Sign up for GitHub

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

Jump to bottom

[Bug]: FlinkRunner does not correctly implement bundle requirements #28649

Open
1 of 15 tasks
je-ik opened this issue Sep 25, 2023 · 0 comments
Open
1 of 15 tasks

[Bug]: FlinkRunner does not correctly implement bundle requirements #28649

je-ik opened this issue Sep 25, 2023 · 0 comments
Labels
bug flink P2

Comments

@je-ik
Copy link
Contributor

je-ik commented Sep 25, 2023 •
edited
Loading

What happened?

FlinkRunner needs to constraint output watermark to min(timestamp of already processed elements in bundle). This is needed to fulfill requirements for holding watermark of elements cached between calls to @StartBundle and @FinishBundle.

ML threads for reference:
https://lists.apache.org/thread/k81fq301ypwmjowknzyqq2qc63844rbd
https://lists.apache.org/thread/40x17r8xpfwdf6jlnt5j6jzx330h1ptn

Issue Priority

Priority: 3 (minor)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • 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
Assignees
No one assigned
Labels
bug flink P2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@je-ik