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

[Backport] Only use ExprEval in ConstantExpr if its known that it will be safe (#15694) #16100

Merged
merged 1 commit into from
Mar 12, 2024

Conversation

cryptoe
Copy link
Contributor

@cryptoe cryptoe commented Mar 11, 2024

Only use ExprEval in ConstantExpr if its known that it will be safe (#15694)

  • which creates a singleThreaded version of the actual expression (caching ExprEval is allowed)
  • to make a whole subtree of expressions 'singleThreaded' - uses to create the new expression tree
  • creates a specialized which does cache the
  • some annotations were added to make it more likely to notice that there might be something off if a similar change will be made around here for some reason

(cherry picked from commit 27d7c30)

…pache#15694)

*  which creates a singleThreaded version of the actual expression (caching ExprEval is allowed)
*  to make a whole subtree of expressions 'singleThreaded' - uses  to create the new expression tree
*  creates a specialized  which does cache the
* some  annotations were added to make it more likely to notice that there might be something off if a similar change will be made around here for some reason

(cherry picked from commit 27d7c30)
@cryptoe cryptoe added this to the 29.0.1 milestone Mar 11, 2024
@cryptoe cryptoe merged commit 51c8f65 into apache:29.0.1 Mar 12, 2024
79 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants