-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Regex query doesn't parse with another where clause #1799
Comments
dgnorton
added a commit
that referenced
this issue
Mar 2, 2015
Change the regex delimiter from single quotes to back ticks (`) and make the scanner recognize regex tokens. Single quotes are used for string literals. Using a unique delimiter for regular expression literals allows the scanner to recognize regular expression tokens, which is inline with the way the rest of the scanner / parser work.
dgnorton
added a commit
that referenced
this issue
Mar 3, 2015
dgnorton
added a commit
that referenced
this issue
Mar 3, 2015
dgnorton
added a commit
that referenced
this issue
Mar 3, 2015
dgnorton
added a commit
that referenced
this issue
Mar 4, 2015
fix #1799: make scanner recognize regex
mark-rushakoff
pushed a commit
that referenced
this issue
Jan 11, 2019
feat(http/paging): add paging implementation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Write in data to a measurement called
cpu
with aregion
andhost
tag. Then do a query like thisAnd you get a parsing error: {"error":"error parsing query: left operand of operator =~ must be an identifier"}
The text was updated successfully, but these errors were encountered: