-
Notifications
You must be signed in to change notification settings - Fork 5.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
Influx parser fails to parse but returns no error #2297
Comments
Can you confirm that InfluxDB accepts metrics without newlines (besides via the HTTP service, which in telegraf is also still adding a newline) |
Not sure what you mean by "besides via the HTTP service". Why wouldn't that be a valid case of InfluxDB not needing a newline? But in the case of UDP, yes, it accepts points without newlines:
|
well, the problem really is that we haven't ever defined out line-protocol data format very well. A newline is supposed to be required but apparently we don't enforce that very consistently. I'll try to get a fix in for that and cherry-pick it into 1.2 |
Bug report
Expected behavior:
Actual behavior:
Additional info:
It parses fine only if there is a trailing newline.
This is a regression. I noticed this while trying to update PR #2094. Code that was previously working is now failing. While I would argue that a trailing newline should not be required to parse, at the very least if it does not parse, it should return an error.
The text was updated successfully, but these errors were encountered: