Skip to content

[fix](routineload) Honor explicit Kafka partition pins - #67517

Open
0AyanamiRei wants to merge 1 commit into
apache:masterfrom
0AyanamiRei:fix/doris-25343-kafka-partition-pin
Open

[fix](routineload) Honor explicit Kafka partition pins#67517
0AyanamiRei wants to merge 1 commit into
apache:masterfrom
0AyanamiRei:fix/doris-25343-kafka-partition-pin

Conversation

@0AyanamiRei

Copy link
Copy Markdown
Contributor

What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: ALTER ROUTINE LOAD with explicit Kafka partitions and offsets updated only those offsets while leaving the previous consumed partition set intact. After resume, omitted partitions could still be scheduled, and cloud progress replay could reintroduce their stale offsets. Replace the active partition state with the explicit definition and filter replayed cloud progress to that pin.

Release note

Explicit Kafka partition and offset alterations now restrict routine load consumption to the specified partitions across replay and resume.

Check List (For Author)

  • Test: Unit tests added; not run as requested
  • Behavior changed: Yes. Explicit Kafka partition alters now replace the consumed partition set.
  • Does this need documentation: No

### What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary: ALTER ROUTINE LOAD with explicit Kafka partitions and offsets updated only those offsets while leaving the previous consumed partition set intact. After resume, omitted partitions could still be scheduled, and cloud progress replay could reintroduce their stale offsets. Replace the active partition state with the explicit definition and filter replayed cloud progress to that pin.

### Release note

Explicit Kafka partition and offset alterations now restrict routine load consumption to the specified partitions across replay and resume.

### Check List (For Author)

- Test: Unit tests added; not run as requested
- Behavior changed: Yes. Explicit Kafka partition alters now replace the consumed partition set.
- Does this need documentation: No
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

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

Successfully merging this pull request may close these issues.

2 participants