comment about #676 fix

I reviewed the fix for #676 and have a comment about it. Unfortunately #676 cannot be reopened, so that is why the new ticket was open.

Why are `timestamp` and `sequence_number` still converted via `float64` ?
https://github.com/influxdb/influxdb/commit/dcc1c9a2e02c9a2a34a243b1a3439813f52bf24e#diff-5f4e7a2764de0f93aa09e2d68927b6aaR71
https://github.com/influxdb/influxdb/commit/dcc1c9a2e02c9a2a34a243b1a3439813f52bf24e#diff-5f4e7a2764de0f93aa09e2d68927b6aaR94
It seems at least superfluous and can cause the same bug (for example with user-generated `sequence_number`)
There's nothing stopping it from being a float. According to the json spec, there's no distinction between an int and a float. We try to do our best to parse it as an int and preserve the precision but we might have to fall back to float