Skip to content

Add temporary escape hatch to allow unsafe pushdowns#22987

Merged
martint merged 1 commit intotrinodb:masterfrom
martint:pushdown-allow-unsafe
Aug 14, 2024
Merged

Add temporary escape hatch to allow unsafe pushdowns#22987
martint merged 1 commit intotrinodb:masterfrom
martint:pushdown-allow-unsafe

Conversation

@martint
Copy link
Copy Markdown
Member

@martint martint commented Aug 9, 2024

PR #21429 fixed an issue that might cause query failures due to aggressive pushdown of expressions that could fail on certain inputs.

Unfortunately, it resulted in a regression in use cases that were relying on this behavior (e.g., issue #22268). A proper fix is not trivial, so we introduce a temporary escape hatch to allow users to restore the old behavior until the final fix is in place.

Release notes

(x) Release notes are required, with the following suggested text:

# General
* TBD. ({issue}`...`)

PR trinodb#21429 fixed an issue that might cause query failures due to
aggressive pushdown of expressions that could fail on certain
inputs.

Unfortunately, it resulted in a regression in use cases that
were relying on this behavior (e.g., issue trinodb#22268). A proper fix
is not trivial, so we introduce a temporary escape hatch to
allow users to restore the old behavior until the final fix is
in place.
@martint martint force-pushed the pushdown-allow-unsafe branch from c977080 to 2eb423e Compare August 14, 2024 20:14
@martint martint merged commit e099383 into trinodb:master Aug 14, 2024
@martint martint deleted the pushdown-allow-unsafe branch August 14, 2024 22:48
@github-actions github-actions bot added this to the 454 milestone Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants