-
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
Invalid line protocol format crashes influxdb 0.9.6.1 #5407
Comments
Reading the documentation, I shouldn't have to escape the backslash. The problem is likely because the backslash is the last character in the tag value, immediately proceeded by a comma. |
#5382 looks like it should prevent the panic, but it's still not parseable. Looks like |
As @jwilder mentions, this won't panic as of Unfortunately the only workaround at the moment is to add another character to the tag value (which could be an escaped space, say), e.g., like this: |
Hmm, agreed. How easy would it be possible to either allow backslash to be escaped? Or would it be preferable to handle the backslash-as-last-character case? Should I file a new issue or just re-purpose this one? |
@e-dard @phalenor I think the line protocol would need to handle |
Yep, makes sense. I would be happy to look at this, if you like.
|
@e-dard If you have time to look at it that would great. Thanks! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions. |
This write is coming from graphios (which needs to be fixed to escape backslashes). This shouldn't crash influxd, though.
The text was updated successfully, but these errors were encountered: