Skip to content
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

Fix handling of escapes within fieldset #3003

Merged
merged 1 commit into from
Jul 11, 2017
Merged

Conversation

danielnelson
Copy link
Contributor

Line protocol does not require or allow escaping of backslash, the only
requirement for a byte to be escaped is if it is an escapable char and
preceeded immediately by a slash.

closes #3001

Required for all PRs:

  • Signed CLA.
  • Associated README.md updated.
  • Has appropriate unit tests.

Line protocol does not require or allow escaping of backslash, the only
requirement for a byte to be escaped is if it is an escapable char and
preceeded immediately by a slash.
@danielnelson danielnelson added this to the 1.3.4 milestone Jul 11, 2017
@danielnelson danielnelson merged commit 945446b into master Jul 11, 2017
@danielnelson danielnelson deleted the fix-field-escaping branch July 11, 2017 02:05
danielnelson added a commit that referenced this pull request Jul 11, 2017
Line protocol does not require or allow escaping of backslash, the only
requirement for a byte to be escaped is if it is an escapable char and
preceeded immediately by a slash.
(cherry picked from commit 945446b)
@danielnelson danielnelson changed the title Fix error handling escaped field strings Fix handling of escapes within fieldset Jul 11, 2017
jeichorn pushed a commit to jeichorn/telegraf that referenced this pull request Jul 24, 2017
Line protocol does not require or allow escaping of backslash, the only
requirement for a byte to be escaped is if it is an escapable char and
preceeded immediately by a slash.
maxunt pushed a commit that referenced this pull request Jun 26, 2018
Line protocol does not require or allow escaping of backslash, the only
requirement for a byte to be escaped is if it is an escapable char and
preceeded immediately by a slash.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

service crash with panic: slice bounds out of range
1 participant