{"push_id":740670453,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"e78ec1a8fabfe409c92c4904208f53dbdcfcf139","before":"6662ee21244067180c1bcef0b16107b2979fd933","commits":[{"sha":"e78ec1a8fabfe409c92c4904208f53dbdcfcf139","author":{"email":"e5dd8a3899598b2e85930c5ff06b11c053ef654f@databricks.com","name":"Josh Rosen"},"message":"[SPARK-9421] Fix null-handling bugs in UnsafeRow.getDouble, getFloat(), and get(ordinal, dataType)\n\nUnsafeRow.getDouble and getFloat() return NaN when called on columns that are null, which is inconsistent with the behavior of other row classes (which is to return 0.0).\n\nIn addition, the generic get(ordinal, dataType) method should always return null for a null literal, but currently it handles nulls by calling the type-specific accessors.\n\nThis patch addresses both of these issues and adds a regression test.\n\nAuthor: Josh Rosen <joshrosen@databricks.com>\n\nCloses #7736 from JoshRosen/unsafe-row-null-fixes and squashes the following commits:\n\nc8eb2ee [Josh Rosen] Fix test in UnsafeRowConverterSuite\n6214682 [Josh Rosen] Fixes to null handling in UnsafeRow","distinct":true,"url":"https://api.github.com/repos/apache/spark/commits/e78ec1a8fabfe409c92c4904208f53dbdcfcf139"}]}