Skip to content

branch-4.0: [Improve](streaming job) support postgres partition table sync #60560#60614

Open
JNSimba wants to merge 4 commits intoapache:branch-4.0from
JNSimba:pick-pg-partition
Open

branch-4.0: [Improve](streaming job) support postgres partition table sync #60560#60614
JNSimba wants to merge 4 commits intoapache:branch-4.0from
JNSimba:pick-pg-partition

Conversation

@JNSimba
Copy link
Member

@JNSimba JNSimba commented Feb 9, 2026

What problem does this PR solve?

Cherry-picked from #60560, #60624

Release note

None

Check List (For Author)

  • Test

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

…e#60560)

### What problem does this PR solve?

Related PR: apache#59461 

To enhance partition table synchronization, add
`publish_via_partition_root` when creating a PUBLICATION instance,
specifically for PG 13+.
@JNSimba JNSimba requested a review from yiguolei as a code owner February 9, 2026 07:51
@Thearas
Copy link
Contributor

Thearas commented Feb 9, 2026

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?

@JNSimba
Copy link
Member Author

JNSimba commented Feb 9, 2026

run buildall

@JNSimba
Copy link
Member Author

JNSimba commented Feb 9, 2026

run external

2 similar comments
@JNSimba
Copy link
Member Author

JNSimba commented Feb 9, 2026

run external

@JNSimba
Copy link
Member Author

JNSimba commented Feb 10, 2026

run external

@JNSimba
Copy link
Member Author

JNSimba commented Feb 10, 2026

run buildall

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

Increment line coverage 0.00% (0/2) 🎉
Increment coverage report
Complete coverage report

@JNSimba
Copy link
Member Author

JNSimba commented Feb 10, 2026

run external

@JNSimba
Copy link
Member Author

JNSimba commented Feb 10, 2026

run nonConcurrent

@JNSimba
Copy link
Member Author

JNSimba commented Feb 10, 2026

run buildall

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

Increment line coverage 0.00% (0/2) 🎉
Increment coverage report
Complete coverage report

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.

3 participants