Skip to content

Conversation

@bobhan1
Copy link
Contributor

@bobhan1 bobhan1 commented Jun 29, 2024

Proposed changes

pick #36836

@doris-robot
Copy link

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

Since 2024-03-18, the Document has been moved to doris-website.
See Doris Document.

@bobhan1
Copy link
Contributor Author

bobhan1 commented Jun 29, 2024

run buildall

@github-actions
Copy link
Contributor

clang-tidy review says "All clean, LGTM! 👍"

@doris-robot
Copy link

TeamCity be ut coverage result:
Function Coverage: 36.32% (9144/25174)
Line Coverage: 27.87% (74598/267692)
Region Coverage: 26.78% (38476/143682)
Branch Coverage: 23.47% (19502/83084)
Coverage Report: http://coverage.selectdb-in.cc/coverage/1943c71df8102599ebb497280683d2852317147d_1943c71df8102599ebb497280683d2852317147d/report/index.html

dataroaring pushed a commit that referenced this pull request Jun 30, 2024
…ange node rather than on TabletWriter when using `TABLET_SINK_SHUFFLE_PARTITIONED` (#36836)

## Proposed changes

Issue Number: close #36638

#30914 add partition tablet sink
shuffle and the processing of auto_increment column should be handled on
exchange node raher than TabletWriter when using partition tablet sink
shuffle.

branch-2.1-pick: #37029
@dataroaring dataroaring merged commit 4210a6a into apache:branch-2.1 Jul 1, 2024
dataroaring pushed a commit that referenced this pull request Jul 2, 2024
…ange node rather than on TabletWriter when using `TABLET_SINK_SHUFFLE_PARTITIONED` (#36836)

## Proposed changes

Issue Number: close #36638

#30914 add partition tablet sink
shuffle and the processing of auto_increment column should be handled on
exchange node raher than TabletWriter when using partition tablet sink
shuffle.

branch-2.1-pick: #37029
@yiguolei yiguolei mentioned this pull request Jul 19, 2024
1 task
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