{"push_id":803249580,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"758c9d25e92417f8c06328c3af7ea2ef0212c79f","before":"084e4e126211d74a79e8dbd2d0e604dd3c650822","commits":[{"sha":"83f6f54d12a418f5158ee7ee985b54eef8cc1cf0","author":{"email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@databricks.com","name":"Andrew Or"},"message":"[SPARK-10474] [SQL] Aggregation fails to allocate memory for pointer array (round 2)\n\nThis patch reverts most of the changes in a previous fix #8827.\n\nThe real cause of the issue is that in `TungstenAggregate`'s prepare method we only reserve 1 page, but later when we switch to sort-based aggregation we try to acquire 1 page AND a pointer array. The longer-term fix should be to reserve also the pointer array, but for now ***we will simply not track the pointer array***. (Note that elsewhere we already don't track the pointer array, e.g. [here](https://github.com/apache/spark/blob/a18208047f06a4244703c17023bb20cbe1f59d73/sql/core/src/main/java/org/apache/spark/sql/execution/UnsafeKVExternalSorter.java#L88))\n\nNote: This patch reuses the unit test added in #8827 so it doesn't show up in the diff.\n\nAuthor: Andrew Or <andrew@databricks.com>\n\nCloses #8888 from andrewor14/dont-track-pointer-array.","distinct":true,"url":"https://api.github.com/repos/dbtsai/spark/commits/83f6f54d12a418f5158ee7ee985b54eef8cc1cf0"},{"sha":"758c9d25e92417f8c06328c3af7ea2ef0212c79f","author":{"email":"5d14e010a5b345b784fd604efcc6cebb79f97468@gmail.com","name":"zsxwing"},"message":"[SPARK-10692] [STREAMING] Expose failureReasons in BatchInfo for streaming UI to clear failed batches\n\nSlightly modified version of #8818, all credit goes to zsxwing\n\nAuthor: zsxwing <zsxwing@gmail.com>\nAuthor: Tathagata Das <tathagata.das1565@gmail.com>\n\nCloses #8892 from tdas/SPARK-10692.","distinct":true,"url":"https://api.github.com/repos/dbtsai/spark/commits/758c9d25e92417f8c06328c3af7ea2ef0212c79f"}]}