he first column are the timestamps of the data. In your submitted data, you are creating a tag or field named "time" and giving it a value, but that is not a timestamp to the database. Because the points are arriving without an explicit timestamp, the system is generating one (in nanoseconds) and assigning it. The numbers are all the same because the points are arriving in the same batch.
You don't identify the version of the database or API library you are using for the writes so I can't say why your points are missing explicit timestamps. On Wed, Jul 6, 2016 at 1:57 PM, <[email protected]> wrote: > Hi All, > Having this problem with inserting data in an influx db measurement. > > Data structure getting pushed to the data base is as follows. > > [ { value: 612 }, { time: 1467823200 } ] > [ { value: 609 }, { time: 1467823500 } ] > [ { value: 609 }, { time: 1467823800 } ] > [ { value: 610 }, { time: 1467824100 } ] > [ { value: 608 }, { time: 1467824400 } ] > [ { value: 610 }, { time: 1467824700 } ] > > However, the data getting added into the database is > > 1467824902363000000 1467741300 587 > 1467824902363000000 1467741000 589 > 1467824902363000000 1467740700 590 > 1467824902363000000 1467740400 590 > 1467824902363000000 1467740100 589 > 1467824902363000000 1467739800 586 > 1467824902363000000 1467739500 585 > 1467824902363000000 1467739200 584 > 1467824902363000000 1467738900 579 > > The first column is an additional column which I dont require. > > The statement to add data to the DB is as follows. > > client.writePoints('POC_CP9', allElements, > function(done){console.log(done)}); > > Output of "allElements" is > > [ { value: 612 }, { time: 1467823200 } ] > [ { value: 609 }, { time: 1467823500 } ] > [ { value: 609 }, { time: 1467823800 } ] > [ { value: 610 }, { time: 1467824100 } ] > [ { value: 608 }, { time: 1467824400 } ] > [ { value: 610 }, { time: 1467824700 } ] > > > Can you guys please provide some ideas as to what is causing this? > > Thanks for the help > > > -- > Remember to include the InfluxDB version number with all issue reports > --- > You received this message because you are subscribed to the Google Groups > "InfluxDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/influxdb. > To view this discussion on the web visit > https://groups.google.com/d/msgid/influxdb/16fbaed5-40a6-48a5-89ec-455b4c068b41%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- Sean Beckett Director of Support and Professional Services InfluxDB -- Remember to include the InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/CALGqCvPO0rvnZS6s2GRkH3w5QHmP44S-9kGQcWNG%2BmzFkStOwg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
