-
Notifications
You must be signed in to change notification settings - Fork 91
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
Enable ability to escape from combinatorial explosion early #36
Comments
Similar to this I'd like to enable Line 41 in c191199
but it isn't configurable. As an interface, these aren't even fields we can change https://stackoverflow.com/a/11070886/689119 . |
These seem like fine things to open up for configuration. |
FWIW I am guessing these config fields were added with the intent being that they'd eventually be configurable (otherwise why bother hardcoding them to false), so this would be a natural progression for the library. |
Anyone want to attempt a PR to add configuration items for these constants? It wouldn't be difficult since we already have some logic for configuration. |
…operties * note: used underscores instead of periods used in the joni.debug* options
[#36] allow changing almost everything in Config using System Properties
Fixed by #67. |
Moved to 2.2.0 because we're also landing some API changes. |
Joni's look-ahead/look-behind feature in evaluating regex matches can find themselves in large recursive loops causing things like elastic/elasticsearch#28731 to occur.
It would be nice to be able to enable
Config.CEC
so that combinatorial explosion heuristically checks can be applied to prevent certain matches to explode things.The ability to interrupt the engine thread is nice, but it would be great if one did not have to spawn a timer on a separate thread just to watch the engine and prevent it from taking up too many resources.
any thoughts?
The text was updated successfully, but these errors were encountered: