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

[Bugfix][Kafka] In kafka flow mode, stop offse should be Long.MAX_VALUE #7871

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

Carl-Zhou-CN
Copy link
Member

@Carl-Zhou-CN Carl-Zhou-CN commented Oct 18, 2024

Purpose of this pull request

Does this PR introduce any user-facing change?

How was this patch tested?

Current test

Check list

@liunaijie liunaijie changed the title [Bugfix][Kafka] In kafak flow mode, stop offse should be Long.MAX_VALUE [Bugfix][Kafka] In kafka flow mode, stop offse should be Long.MAX_VALUE Oct 18, 2024
@hailin0
Copy link
Member

hailin0 commented Oct 18, 2024

Please add test cases

@Hisoka-X Hisoka-X added this to the 2.3.9 milestone Oct 28, 2024
@weipengfei-sj
Copy link

weipengfei-sj commented Oct 31, 2024

image
When running tasks in a flow mode, an empty map array is returned, and a NullPointerException will occur at this location.

It also needs to be adjusted to the following format.
split.setEndOffset(
latestOffsets.getOrDefault(
split.getTopicPartition(), Long.MAX_VALUE));

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

Successfully merging this pull request may close these issues.

4 participants