You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current Behavior:
If I call writePoint two times in a row in rapid succession (e.g., right after each other or within milliseconds of each other), I see the values of the first point end up in the database more often than not.
Possible Solution:
If I put the second write into a setTimeout(() => writePoint(point), 5000), I correctly see the overwriting occur as expected.
Notice that if you do a bunch of these, 5 ends up in the database often.
Specifications:
Version: 2.0.4-Alpine
Platform: Docker
Notes:
I do not know where exactly the issue here is, and it might be an issue on the InfluxDB side of things, but I figured I would start with the JS library as that is what I am interfacing with.
The text was updated successfully, but these errors were encountered:
Expected Behavior:
When I submit two points with the same timestamp/tags/measurement but different values, based on https://docs.influxdata.com/influxdb/cloud/write-data/best-practices/duplicate-points/ I should expect to see the field values on the second point end up in the database and the field values from the first point overwritten.
Current Behavior:
If I call
writePoint
two times in a row in rapid succession (e.g., right after each other or within milliseconds of each other), I see the values of the first point end up in the database more often than not.Possible Solution:
If I put the second write into a
setTimeout(() => writePoint(point), 5000)
, I correctly see the overwriting occur as expected.Steps/Code to Reproduce the Problem:
Notice that if you do a bunch of these,
5
ends up in the database often.Specifications:
Notes:
I do not know where exactly the issue here is, and it might be an issue on the InfluxDB side of things, but I figured I would start with the JS library as that is what I am interfacing with.
The text was updated successfully, but these errors were encountered: