{"push_id":889022269,"size":4,"distinct_size":4,"ref":"refs/heads/master","head":"5349851f368a1b5dab8a99c0d51c9638ce7aec56","before":"d0d7ec533062151269b300ed455cf150a69098c0","commits":[{"sha":"9bb695b7a82d837e2c7a724514ea6b203efb5364","author":{"email":"9616cf314f60cbadfd3d5d51110130ad7923defb@databricks.com","name":"Xiangrui Meng"},"message":"[SPARK-12000] do not specify arg types when reference a method in ScalaDoc\n\nThis fixes SPARK-12000, verified on my local with JDK 7. It seems that `scaladoc` try to match method names and messed up with annotations.\n\ncc: JoshRosen jkbradley\n\nAuthor: Xiangrui Meng <meng@databricks.com>\n\nCloses #10114 from mengxr/SPARK-12000.2.","distinct":true,"url":"https://api.github.com/repos/zzcclp/spark/commits/9bb695b7a82d837e2c7a724514ea6b203efb5364"},{"sha":"ae402533738be06ac802914ed3e48f0d5fa54cbe","author":{"email":"e5dd8a3899598b2e85930c5ff06b11c053ef654f@databricks.com","name":"Josh Rosen"},"message":"[SPARK-12082][FLAKY-TEST] Increase timeouts in NettyBlockTransferSecuritySuite\n\nWe should try increasing a timeout in NettyBlockTransferSecuritySuite in order to reduce that suite's flakiness in Jenkins.\n\nAuthor: Josh Rosen <joshrosen@databricks.com>\n\nCloses #10113 from JoshRosen/SPARK-12082.","distinct":true,"url":"https://api.github.com/repos/zzcclp/spark/commits/ae402533738be06ac802914ed3e48f0d5fa54cbe"},{"sha":"ec2b6c26c9b6bd59d29b5d7af2742aca7e6e0b07","author":{"email":"8adc4758e0403b3bd961e4e414291eaa9ba64098@databricks.com","name":"Yin Huai"},"message":"[SPARK-12109][SQL] Expressions's simpleString should delegate to its toString.\n\nhttps://issues.apache.org/jira/browse/SPARK-12109\n\nThe change of https://issues.apache.org/jira/browse/SPARK-11596 exposed the problem.\nIn the sql plan viz, the filter shows\n\n![image](https://cloud.githubusercontent.com/assets/2072857/11547075/1a285230-9906-11e5-8481-2bb451e35ef1.png)\n\nAfter changes in this PR, the viz is back to normal.\n![image](https://cloud.githubusercontent.com/assets/2072857/11547080/2bc570f4-9906-11e5-8897-3b3bff173276.png)\n\nAuthor: Yin Huai <yhuai@databricks.com>\n\nCloses #10111 from yhuai/SPARK-12109.","distinct":true,"url":"https://api.github.com/repos/zzcclp/spark/commits/ec2b6c26c9b6bd59d29b5d7af2742aca7e6e0b07"},{"sha":"5349851f368a1b5dab8a99c0d51c9638ce7aec56","author":{"email":"b1011540267ee7fe5a02243ad09c007ca1860809@oc0558782468.ibm.com","name":"Huaxin Gao"},"message":"[SPARK-12088][SQL] check connection.isClosed before calling connection…\n\nIn Java Spec java.sql.Connection, it has\nboolean getAutoCommit() throws SQLException\nThrows:\nSQLException - if a database access error occurs or this method is called on a closed connection\n\nSo if conn.getAutoCommit is called on a closed connection, a SQLException will be thrown. Even though the code catch the SQLException and program can continue, I think we should check conn.isClosed before calling conn.getAutoCommit to avoid the unnecessary SQLException.\n\nAuthor: Huaxin Gao <huaxing@oc0558782468.ibm.com>\n\nCloses #10095 from huaxingao/spark-12088.","distinct":true,"url":"https://api.github.com/repos/zzcclp/spark/commits/5349851f368a1b5dab8a99c0d51c9638ce7aec56"}]}