-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[0.9.3-HEAD] Quoted measurement names fail #3681
Comments
@yvesf I cannot reproduce this on 0.9.2, the writes succeed for me just fine. Using
using the CLI:
I cannot successfully query those measurements because the parser is upset with the double-quote, but that's different from not being able to write the point. |
Opened #3698 for the query bug. |
Hi @beckettsean, you are right it's working fine in v0.9.2. However, in current HEAD it's not working. I think it's failing since cb7f0b8. |
Still working in the most recent nightly:
@jwilder is this commit: cb7f0b8 in the most recent 0.9.3 nightly? |
In my case it also succeed using the 'influx' client because it packs a whitespace at the beginning. Compare the to requests in the following
success using
(note content length 28 = 26 + space + newline) |
If the measurement started with a quote, a panic would happen. This is a reegression due to cb7f0b8. This also uncovered that measurement names were being escaped incorrectly. The escape codes for tag and fields also includes `=` and '"` which should not be escaped for measurement names. Fixes #3681
If the measurement started with a quote, a panic would happen. This is a reegression due to cb7f0b8. This also uncovered that measurement names were being escaped incorrectly. The escape codes for tag and fields also includes `=` and '"` which should not be escaped for measurement names. Fixes #3681
The document lists this example
However, already this smaller one fails:
Every line starting with
"
fails because thescanLine
function intsdb/points.go
tries to find out if it was quoted (line 710), thus raising aruntime error: index out of range
The text was updated successfully, but these errors were encountered: