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
That regular expression has not changed for a long time, so fixing it is probably not necessary for correctness, but it will avoid questions on forums/issues/support cases if it could be fixed before release of 7.5.
The text was updated successfully, but these errors were encountered:
This prevents the following warning from being printed to console:
`regular expression has redundant nested repeat operator + /%\{(?<name>(?<pattern>[A-z0-9]+)(?::(?<subname>[[:alnum:]@\[\]_:.-]+))?)(?:=(?<definition>(?:(?:[^{}]+|\.+)+)+))?\}/`
The current grok expression is not failing, but just this warning is being printed.
The warning started being printed after upgrading joni (elastic#47374).
Closeselastic#47861
This prevents the following warning from being printed to console:
`regular expression has redundant nested repeat operator + /%\{(?<name>(?<pattern>[A-z0-9]+)(?::(?<subname>[[:alnum:]@\[\]_:.-]+))?)(?:=(?<definition>(?:(?:[^{}]+|\.+)+)+))?\}/`
The current grok expression is not failing, but just this warning is being printed.
The warning started being printed after upgrading joni (#47374).
Closes#47861
This prevents the following warning from being printed to console:
`regular expression has redundant nested repeat operator + /%\{(?<name>(?<pattern>[A-z0-9]+)(?::(?<subname>[[:alnum:]@\[\]_:.-]+))?)(?:=(?<definition>(?:(?:[^{}]+|\.+)+)+))?\}/`
The current grok expression is not failing, but just this warning is being printed.
The warning started being printed after upgrading joni (#47374).
Closes#47861
Following the Joni upgrade in #47374 the following warning is printed on Elasticsearch startup:
I guess it means there is a non-fatal inefficiency in this regex:
elasticsearch/libs/grok/src/main/java/org/elasticsearch/grok/Grok.java
Lines 50 to 63 in f6f249b
That regular expression has not changed for a long time, so fixing it is probably not necessary for correctness, but it will avoid questions on forums/issues/support cases if it could be fixed before release of 7.5.
The text was updated successfully, but these errors were encountered: