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

release-23.1: sql: fix pausable portal execution of apply joins with subqueries #106728

Merged
merged 1 commit into from
Jul 12, 2023

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Jul 12, 2023

Backport 1/1 commits from #106659 on behalf of @yuzefovich.

/cc @cockroachdb/release


Previously, when executing a query with an apply join with "inner" subqueries via pausable portals model we would crash because we'd incorrectly apply the "pausable portal" execution model to those "inner" subqueries (even though they need to be executed completely). We already disabled this execution model for the main "inner" query, but it should be disabled for the whole apply join iteration.

I decided to not include a release note given that pausable portals are disabled by default and apply joins with inner subqueries seem like an edge case.

Epic: None

Release note: None


Release justification: bug fix.

Previously, when executing a query with an apply join with "inner"
subqueries via pausable portals model we would crash because we'd
incorrectly apply the "pausable portal" execution model to those "inner"
subqueries (even though they need to be executed completely). We already
disabled this execution model for the main "inner" query, but it should
be disabled for the whole apply join iteration.

I decided to not include a release note given that pausable portals are
disabled by default and apply joins with inner subqueries seem like an
edge case.

Release note: None
@blathers-crl blathers-crl bot requested review from a team as code owners July 12, 2023 22:40
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-106659 branch from 34e1bd5 to 33d9ef8 Compare July 12, 2023 22:40
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Jul 12, 2023
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-106659 branch from 1e8670e to 52aa57f Compare July 12, 2023 22:40
@blathers-crl
Copy link
Author

blathers-crl bot commented Jul 12, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@yuzefovich yuzefovich requested a review from rharding6373 July 12, 2023 22:44
Copy link
Collaborator

@rharding6373 rharding6373 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @yuzefovich)

@yuzefovich yuzefovich merged commit adee57f into release-23.1 Jul 12, 2023
@yuzefovich yuzefovich deleted the blathers/backport-release-23.1-106659 branch July 12, 2023 23:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants