question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

field type conflict

See original GitHub issue

Expected Behavior

Ability to write points to remote influxdb

Actual Behavior

On writing a simple measurement like this

[ { measurement: 'orma_ambiance',
    tags: { sensor_id: '70:b3:d5:47:50:10:03:d9', endpoint_id: 16 },
    fields:
     { temperature: 25.16, humidity: 25, co2: 732, presence: 2990 },
    timestamp: 2019-05-15T20:01:14.000Z } ]

we get this error: { Error: A 400 Bad Request error occurred: {"error":"partial write: field type conflict: input field \"co2\" on measurement \"orma_ambiance\" is type float, already exists as type integer dropped=1"}

But the problem is as you can see co2 field is 732 which is already an integer number. It seems client use ALWAYS float instead of integer on writing points.

Some ideas?

Specifications

  • Version: 5.4.0
  • Platform: macOS 10.14.5
  • Subsystem:

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
mburger81commented, Jul 18, 2019

Okay, that resolved me our problem.

Not sure why this is was working before. We test also first 5.0.0 version, but also there we have the problem. So not sure in which condition we was before.

But setting schema resolves me the problem!!! I didn’t knew this. Thx a lot!

0reactions
bencevanscommented, Jul 17, 2019

2de6675e58a9ef53f7d08ec91054444656483f7f is somewhat related but not sure it’d trigger your issue. A summarised changelog can be found at https://github.com/node-influx/node-influx/releases or more detail at https://github.com/node-influx/node-influx/commits/master

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to solve type conflicts - InfluxDB 2
Hi, I'm using the influxdb-php lib to read from and write to influx. ... write failed: field type conflict: input field "value" on ......
Read more >
InfluxDB Error "field type conflict: input field value on ...
InfluxDB Error "field type conflict: input field value on measurement is type integer, already exists as type float dropped=1".
Read more >
InfluxDBClientError: 400 ("error":"partial write: field type conflict)
According to influxdb doc : " by default, InfluxDB assumes all numerical field values are floats." > INSERT weather,location=us-midwest temperature=82 ...
Read more >
Kibana conflict type field - Elastic Discuss
I have a few fields (bytesSent, bytesReceived, timetaken) that show mapping conflicts, and thus I cannot visualize them in Kibana.
Read more >
What's the difference between an Elasticsearch mapping ...
Kibana mapping conflicts occur when the fields don't match the type saved in the index pattern. This can be fixed by updating the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found