negative timestamps not valid for line protocol

[beckettsean]

CLI, showing max positive int64 is valid, but the smallest negative integer fails.

> insert timestamps value=1 
> insert timestamps value=1 9023372036854775808
> insert timestamps value=1 -1
ERR: unable to parse ' timestamps value=1 -1': bad timestamp

> 

curl showing same issue (not sure why curl tops out at max int64 -1):

$ curl -XPOST 'http://localhost:8086/write?db=mydb' -d 'timestamps value=1 9223372036854775808'
unable to parse 'timestamps value=1 9223372036854775808': strconv.ParseInt: parsing "9223372036854775808": value out of range
$ curl -XPOST 'http://localhost:8086/write?db=mydb' -d 'timestamps value=1 9223372036854775807'
$ curl -XPOST 'http://localhost:8086/write?db=mydb' -d 'timestamps value=1 -1'
unable to parse 'timestamps value=1 -1': bad timestamp

[beckettsean]

@jwilder we used to support negative timestamps. Was there an explicit decision not to with the line protocol, or is there a parser bug that's not properly accepting - as a valid leading character for timestamps?

[jwilder]

Was not aware of that requirement so just a bug.