8000 Nanosecond time data being sent even if time_precision set to something else · Issue #221 · influxdata/influxdb-python · GitHub
[go: up one dir, main page]

Skip to content 8000
This repository was archived by the owner on Oct 29, 2024. It is now read-only.
This repository was archived by the owner on Oct 29, 2024. It is now read-only.
Nanosecond time data being sent even if time_precision set to something else #221
Closed
@dschallis

Description

@dschallis

In 2.7.1, if I have e.g.:

data = [{'fields': {'value': 12629},
             'time': '2015-07-27T12:55:48.165231Z',
             'measurement': 'foo'}]
client.write_points(data, time_precision='u')

Then the 'precision' field is correctly set, but the timestamp is sent as a nanosecond integer value, e.g. the above is sent with:

POST /write?db=test&precision=u
...skipped other headers here....
foo value=12629 1438001748165231104\n

This leads to it being silently rejected by InfluxDB (i.e. after the above, a SELECT * FROM foo returns 0 results), which is probably a bug on their side too (though they don't document very well what should happen in this case).

(apologies for the many tickets by the way, I'm in the process of switching to this module from a reasonably sized code base, so starting to use this module quite heavily :) )

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0