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
@sethm thanks for this report. I think I know where the issue is. As a workaround for the moment you could, as you suggest, use =~ /(?i)^SANTA_MONICA/ or =~ /(?i)SANTA_MONICA$/ or =~ /(?i)SANTA_MONICA/ if any of those are precise enough for you.
Fixes#7906
In an attempt to reduce the overhead of using regex for exact matches,
the query parser will replace `=~ /^thing$/` with `== 'thing'`, but the
conditions being checked would ignore if any flags were set on the
expression, so `=~ /(?i)^THING$/` was replaced with `== 'THING'`, which
will fail unless the case was already exact. This change ensures that no
flags have been changed from those defaulted by the parser.
Bug report
System info: InfluxDB 1.2.0 on OS X 10.12.2 (installed with Homebrew)
Steps to reproduce:
Create a test database
Populate with test data
Attempt to use a case-insensitive regular expression with anchors:
Expected behavior: Should return four rows
Actual behavior: Returns no rows
Additional info: Note that leaving off EITHER anchor returns the expected rows. Replacing either anchor with
\b
also returns expected rows.The text was updated successfully, but these errors were encountered: