Skip to content

Add a session property to disable ReplicateSemiJoinInDelete optimizer#25256

Merged
feilong-liu merged 1 commit intoprestodb:masterfrom
feilong-liu:semi_delete
Jun 6, 2025
Merged

Add a session property to disable ReplicateSemiJoinInDelete optimizer#25256
feilong-liu merged 1 commit intoprestodb:masterfrom
feilong-liu:semi_delete

Conversation

@feilong-liu
Copy link
Contributor

Description

This ReplicateSemiJoinInDelete enforce broadcast for semi join, however we may not want it if the build side is large.

Motivation and Context

As described above

Impact

As described above

Test Plan

Easy change, default behavior stays the same

Contributor checklist

  • Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
  • PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
  • Documented new properties (with its default value), SQL syntax, functions, or other functionality.
  • If release notes are required, they follow the release notes guidelines.
  • Adequate tests were added if applicable.
  • CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* Add a session property to disable the ReplicateSemiJoinInDelete optimizer

@feilong-liu feilong-liu requested a review from a team as a code owner June 6, 2025 00:57
@feilong-liu feilong-liu requested a review from ZacBlanco June 6, 2025 00:57
@prestodb-ci prestodb-ci added the from:Meta PR from Meta label Jun 6, 2025
@feilong-liu feilong-liu merged commit 9852c1e into prestodb:master Jun 6, 2025
98 checks passed
@feilong-liu feilong-liu deleted the semi_delete branch June 6, 2025 04:00
@prestodb-ci prestodb-ci mentioned this pull request Jul 28, 2025
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

from:Meta PR from Meta

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants