You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make CEL environment setup consistent across CEL implementations, I propose to add a program option to set maximum RE2 program. This option should work similar to CelOptions#maxRegexProgramSize(int) in CEL-Java and InterpreterOptions.regex_max_program_size in CEL-Cpp (see nuances below).
Implementation details
To support this option, cel-go will have to switch its regexp implementation from the regex package to the regexp/syntax (both in standard go library). In latter, the instruction count is available as the length of regexp/syntax#Prog.Inst.
RE2 program size should be verified when the CEL program is created from the AST (AFAIK this is how cel-cpp works). If this is not possible, java-style implementation where the error is raised during program execution is acceptable as well.
Nuances
The program size represents a very approximate measure of a regexp's "cost". There are no guarantees on the implementation details or claims about the properties of the program size (except "larger numbers are more expensive than smaller numbers").
Currently the program size is the same as the number of instructions of the regex program. However, the number of instructions in a regex depends on the concrete RE2 implementation. The implication of using the number of instructions as the program size is that:
Important
There's no guarantee that RE2 program size has the exact same value in CPP, Go and Java.
We should communicate this in the docs.
Feature request checklist
Change
To make CEL environment setup consistent across CEL implementations, I propose to add a program option to set maximum RE2 program. This option should work similar to
CelOptions#maxRegexProgramSize(int)
in CEL-Java andInterpreterOptions.regex_max_program_size
in CEL-Cpp (see nuances below).Implementation details
Nuances
The program size represents a very approximate measure of a regexp's "cost". There are no guarantees on the implementation details or claims about the properties of the program size (except "larger numbers are more expensive than smaller numbers").
Currently the program size is the same as the number of instructions of the regex program. However, the number of instructions in a regex depends on the concrete RE2 implementation. The implication of using the number of instructions as the program size is that:
Important
There's no guarantee that RE2 program size has the exact same value in CPP, Go and Java.
We should communicate this in the docs.
For example:
Example
Related
CelOptions.maxRegexProgramSize(int)
to limit RE2 program size cel-java#545The text was updated successfully, but these errors were encountered: