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

Downsampling Telegraf type conflict #213

Open
1 of 3 tasks
TheOneValen opened this issue Dec 10, 2020 · 3 comments
Open
1 of 3 tasks

Downsampling Telegraf type conflict #213

TheOneValen opened this issue Dec 10, 2020 · 3 comments
Assignees
Labels
Template Issue A problem with a specific Template

Comments

@TheOneValen
Copy link

Template: Downsampling

Describe the problem
Tasks (all variety) fail regularly with a type conflict. To reproduce you can just use the smart_input template.

To Reproduce
Steps to reproduce the behavior:

  1. Import smart_input
  2. Let it run regularly
  3. See error

could not execute task run; Err: partial write: field type conflict: input field "raw_value" on measurement "smart_attribute" is type integer, already exists as type float dropped=677: partial write: field type conflict: input field "raw_value" on measurement "smart_attribute" is type integer, already exists as type float dropped=677

Expected behavior
No failed task.

How are you running InfluxDB?

  • InfluxDB Cloud platform
  • InfluxDB 2.0 on a remote server
  • InfluxDB 2.0 on my local machine
@TheOneValen TheOneValen added the Template Issue A problem with a specific Template label Dec 10, 2020
@TheOneValen
Copy link
Author

Also happening with other fields, like exit_status

@TheOneValen
Copy link
Author

Us there any news this?

@johntdyer
Copy link

yea, I get this all the time...

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Template Issue A problem with a specific Template
Projects
None yet
Development

No branches or pull requests

3 participants