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: KafkaIO emits MAX_WATEMARK #30050

Closed
1 of 16 tasks
je-ik opened this issue Jan 19, 2024 · 4 comments · Fixed by #30066
Closed
1 of 16 tasks

[Bug]: FlinkRunner: KafkaIO emits MAX_WATEMARK #30050

je-ik opened this issue Jan 19, 2024 · 4 comments · Fixed by #30066
Assignees

Comments

@je-ik
Copy link
Contributor

je-ik commented Jan 19, 2024

What happened?

When reading data from Kafka with legacy Read, MAX_WATERMARK is emitted when the source is not completed.

Issue Priority

Priority: 3 (minor)

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
@je-ik
Copy link
Contributor Author

je-ik commented Jan 19, 2024

Probably related to #29563.

@je-ik
Copy link
Contributor Author

je-ik commented Jan 19, 2024

Probably related to #29563.

Reverting the commit seems not to resolve the issue.

@Abacn
Copy link
Contributor

Abacn commented Jan 19, 2024

Could this be related to #29902 or would integrating #29993 resolve the issue?

@Abacn Abacn removed the P3 label Jan 19, 2024
@je-ik
Copy link
Contributor Author

je-ik commented Jan 20, 2024

I don't think it relates. This bug manifests on Beam 2.53.0, Beam 2.52.0 seems to work fine.

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.

2 participants