Skip to content
This repository was archived by the owner on Oct 29, 2024. It is now read-only.

DataFrameClient.write_points returns HTTP 400 error for "invalid number" #669

Open
PatternMatching opened this issue Jan 4, 2019 · 1 comment

Comments

@PatternMatching
Copy link

I don't have any NaN's in my data and I'm using the line protocol to be safe, so I'm sure that it can't be #195.

Just to make it a bit easier to read, I called using line='json' to make the error a bit more readable:

{"error":
   "unable to parse 'Px.Ercot.RealTimeSettlementPointPrice.UsdPerMWh,SettlementPointName=AEEC DSTFlag=False,DeliveryDate=2019-01-03 00:00:00,DeliveryHour=19i,DeliveryInterval=1i,HourBeginning=18i,QuarterHour=0i,SettlementPointPrice=33.03,SettlementPointType=\"RN\" 1546560000000000000': invalid number
    unable to parse 'Px.Ercot.RealTimeSettlementPointPrice.UsdPerMWh,SettlementPointName=AEEC DSTFlag=False,DeliveryDate=2019-01-03 00:00:00,DeliveryHour=19i,DeliveryInterval=2i,HourBeginning=18i,QuarterHour=1i,SettlementPointPrice=33.91,SettlementPointType=\"RN\" 1546560900000000000': invalid number
    unable to parse 'Px.Ercot.RealTimeSettlementPointPrice.UsdPerMWh,SettlementPointName=AEEC DSTFlag=False,DeliveryDate=2019-01-03 00:00:00,DeliveryHour=19i,DeliveryInterval=3i,HourBeginning=18i,QuarterHour=2i,SettlementPointPrice=33.02,SettlementPointType=\"RN\" 1546561800000000000': invalid number
    unable to parse 'Px.Ercot.RealTimeSettlementPointPrice.UsdPerMWh,SettlementPointName=AEEC DSTFlag=False,DeliveryDate=2019-01-03 00:00:00,DeliveryHour=19i,DeliveryInterval=4i,HourBeginning=18i,QuarterHour=3i,SettlementPointPrice=34.18,SettlementPointType=\"RN\" 1546562700000000000': invalid number
    unable to parse 'Px.Ercot.RealTimeSettlementPointPrice.UsdPerMWh,SettlementPointName=AEEC DSTFlag=False,DeliveryDate=2019-01-03 00:00:00,DeliveryHour=20i,DeliveryInterval=1i,HourBeginning=19i,QuarterHour=0i,SettlementPointPrice=31.05,SettlementPointType=\"RN\" 1546563600000000000': invalid number"
}

I'm using InfluxDB 1.7 and influxdb-python 5.2.1, for what it is worth.

Any ideas as to what I may be doing wrong, or if this is an expected error?

@siegenthalerroger
Copy link

For me getting rid of any datetime objects solved the issue. Only as a pandas index did a datetime work. Unsure why though

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants