{"push_id":707267008,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"b5910cb3200990f265c9f40f63b54141fc38bd29","before":"4d2915b49e5e4a41ec70f3fb3d32bb5500d05df2","commits":[{"sha":"17432598b18d759efd857ea991239aa6a9815cb6","author":{"email":"68c46a606457643eab92053c1c05574abb26f861@influxdb.com","name":"Jason Wilder"},"message":"Prevent out of range ints and floats from being parsed sucessfully\n\nField values that were out of range for the type would panic the database\nwhen being inserted because the parser would allow them as valid points.\nThis change prevents those invalid values from being parsed and instead\nreturns an error.\n\nAn alternative fix considered was to handle the error and clamp the value\nto the min/max value for the type.  This would treat numeric range errors\nslightly differently than other type erros which might lead to confusion.\n\nThe simplest fix with the current parser would be to just convert each field\nto the type at parse time.  Unfortunately, this adds extra memory allocations\nand lowers throughput significantly.  Since out of range values are less common\nthan in-range values, some heuristics are used to determine when the more\nexpensive type parsing and range checking is performed.  Essentially, we only\ndo the slow path when we cannot determine that the value is in an acceptable\ntype range.\n\nFixes #3127","distinct":false,"url":"https://api.github.com/repos/influxdb/influxdb/commits/17432598b18d759efd857ea991239aa6a9815cb6"},{"sha":"b5910cb3200990f265c9f40f63b54141fc38bd29","author":{"email":"68c46a606457643eab92053c1c05574abb26f861@influxdb.com","name":"Jason Wilder"},"message":"Merge pull request #3140 from influxdb/jw-bounds\n\nPrevent out of range ints and floats from being parsed sucessfully","distinct":true,"url":"https://api.github.com/repos/influxdb/influxdb/commits/b5910cb3200990f265c9f40f63b54141fc38bd29"}]}