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

update integer output to new line protocol format #99

Closed
beckettsean opened this issue Aug 7, 2015 · 8 comments
Closed

update integer output to new line protocol format #99

beckettsean opened this issue Aug 7, 2015 · 8 comments
Labels
bug unexpected problem or unintended behavior

Comments

@beckettsean
Copy link
Contributor

With 0.9.3, the line protocol has changed for integers: influxdata/influxdb#3526

This change means that current telegraf users who upgrade to 0.9.3 cannot write a number of values, because they are integer fields in the db but the current telegraf sends them without the trailing i, meaning they parse as floats. That causes a type mismatch and a write failure.

@beckettsean
Copy link
Contributor Author

influxdata/influxdb#3589 for the relevant issue

@sparrc
Copy link
Contributor

sparrc commented Aug 7, 2015

To summarize an email thread, this will simply require a re-build of telegraf using the 0.9.3 release of InfluxDB.

Currently the head of influxdb will not work with telegraf unless you build it from source.

@sparrc sparrc added the bug unexpected problem or unintended behavior label Aug 9, 2015
@sparrc
Copy link
Contributor

sparrc commented Aug 11, 2015

closing this out because it should be fixed with any newer build of telegraf

@sparrc sparrc closed this as completed Aug 11, 2015
@beckettsean
Copy link
Contributor Author

@sparrc is there a plan to issue new telegraf builds in conjunction with new influxdb builds?

@sparrc
Copy link
Contributor

sparrc commented Aug 11, 2015

@beckettsean Not at the moment, but the CircleCI job is now building binaries as well as .deb and .rpm files, so one can find an updated package there if need be https://circleci.com/gh/influxdb/telegraf/tree/master

I believe that it was decided that Telegraf would release on it's own schedule unless there was a release of another product (such as InfluxDB) that introduced a breaking change.

@beckettsean
Copy link
Contributor Author

I believe that it was decided that Telegraf would release on it's own schedule unless there was a release of another product (such as InfluxDB) that introduced a breaking change.

@sparrc I agree with and support the decision about releases in general, but this issue was about a specific case of the "breaking change" mentioned. I would like to know that we will have a coordinated release of telegraf and InfluxDB with the integer write change. An issue seems like a good place to track that so we don't forget on launch day.

@sparrc
Copy link
Contributor

sparrc commented Aug 11, 2015

@beckettsean fair enough, I'll keep it open

@sparrc sparrc reopened this Aug 11, 2015
@sparrc
Copy link
Contributor

sparrc commented Aug 18, 2015

This is fixed and ready in 0.1.5

@sparrc sparrc closed this as completed Aug 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants