-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Add "native_expression.max_compiled_regexes" session property. #24282
Add "native_expression.max_compiled_regexes" session property. #24282
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
...n/java/com/facebook/presto/sessionpropertyproviders/NativeWorkerSessionPropertyProvider.java
Outdated
Show resolved
Hide resolved
ae04ea5
to
2a37c35
Compare
NATIVE_EXPRESSION_MAX_COMPILED_REGEXES, | ||
"Native Execution only. Controls maximum number of compiled regular expression patterns " + | ||
"per regular expression function instance per thread of execution.", | ||
100, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks to be standard for all nativeWorkerSessionProperties, so not requesting a change. but why do we define a default value in the session property vs. have the default value be determined by a config property like we do with everything else.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe because there is no corresponding config property.
Not sure if one must have such.
There is just a corresponding velox query config property, which is per query.
Description
Add "native_expression.max_compiled_regexes" session property.
It can be used to control the limitation of Prestissimo's implementation of regular expression functions.