{"push_id":918854481,"size":194,"distinct_size":0,"ref":"refs/heads/master","head":"932cf44248e067ee7cae6fef79ddf2ab9b1c36d8","before":"051c6a066f7b5fcc7472412144c15b50a5319bd5","commits":[{"sha":"7a8e587dc04c2fabc875d1754eae7f85b4fba6ba","author":{"email":"810f4eaecb829dde5e3d87bd39ae52346de8f0c9@gmail.com","name":"Andrew Ray"},"message":"[SPARK-12211][DOC][GRAPHX] Fix version number in graphx doc for migration from 1.1\n\nMigration from 1.1 section added to the GraphX doc in 1.2.0 (see https://spark.apache.org/docs/1.2.0/graphx-programming-guide.html#migrating-from-spark-11) uses \\{{site.SPARK_VERSION}} as the version where changes were introduced, it should be just 1.2.\n\nAuthor: Andrew Ray <ray.andrew@gmail.com>\n\nCloses #10206 from aray/graphx-doc-1.1-migration.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/7a8e587dc04c2fabc875d1754eae7f85b4fba6ba"},{"sha":"8770bd1213f9b1051dabde9c5424ae7b32143a44","author":{"email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@databricks.com","name":"Andrew Or"},"message":"[SPARK-12165][ADDENDUM] Fix outdated comments on unroll test\n\nJoshRosen\n\nAuthor: Andrew Or <andrew@databricks.com>\n\nCloses #10229 from andrewor14/unroll-test-comments.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/8770bd1213f9b1051dabde9c5424ae7b32143a44"},{"sha":"ac8cdf1cdc148bd21290ecf4d4f9874f8c87cc14","author":{"email":"8adc4758e0403b3bd961e4e414291eaa9ba64098@databricks.com","name":"Yin Huai"},"message":"[SPARK-11678][SQL][DOCS] Document basePath in the programming guide.\n\nThis PR adds document for `basePath`, which is a new parameter used by `HadoopFsRelation`.\n\nThe compiled doc is shown below.\n![image](https://cloud.githubusercontent.com/assets/2072857/11673132/1ba01192-9dcb-11e5-98d9-ac0b4e92e98c.png)\n\nJIRA: https://issues.apache.org/jira/browse/SPARK-11678\n\nAuthor: Yin Huai <yhuai@databricks.com>\n\nCloses #10211 from yhuai/basePathDoc.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/ac8cdf1cdc148bd21290ecf4d4f9874f8c87cc14"},{"sha":"2166c2a75083c2262e071a652dd52b1a33348b6e","author":{"email":"52e35f341ea3ac9b5350d7ef6f0bef4e74c94f03@cloudera.com","name":"Mark Grover"},"message":"[SPARK-11796] Fix httpclient and httpcore depedency issues related to docker-client\n\nThis commit fixes dependency issues which prevented the Docker-based JDBC integration tests from running in the Maven build.\n\nAuthor: Mark Grover <mgrover@cloudera.com>\n\nCloses #9876 from markgrover/master_docker.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/2166c2a75083c2262e071a652dd52b1a33348b6e"},{"sha":"bd2cd4f53d1ca10f4896bd39b0e180d4929867a2","author":{"email":"4330a85689689e23b81e88bdf5853b25c33529eb@gmail.com","name":"Tathagata Das"},"message":"[SPARK-12244][SPARK-12245][STREAMING] Rename trackStateByKey to mapWithState and change tracking function signature\n\nSPARK-12244:\n\nBased on feedback from early users and personal experience attempting to explain it, the name trackStateByKey had two problem.\n\"trackState\" is a completely new term which really does not give any intuition on what the operation is\nthe resultant data stream of objects returned by the function is called in docs as the \"emitted\" data for the lack of a better.\n\"mapWithState\" makes sense because the API is like a mapping function like (Key, Value) => T with State as an additional parameter. The resultant data stream is \"mapped data\". So both problems are solved.\n\nSPARK-12245:\n\nFrom initial experiences, not having the key in the function makes it hard to return mapped stuff, as the whole information of the records is not there. Basically the user is restricted to doing something like mapValue() instead of map(). So adding the key as a parameter.\n\nAuthor: Tathagata Das <tathagata.das1565@gmail.com>\n\nCloses #10224 from tdas/rename.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/bd2cd4f53d1ca10f4896bd39b0e180d4929867a2"},{"sha":"d8ec081c911a040f3fb523a68025928ae4afc906","author":{"email":"563f5923eae9a92c8a3f34a26b67fa348a303ed1@databricks.com","name":"Wenchen Fan"},"message":"[SPARK-12252][SPARK-12131][SQL] refactor MapObjects to make it less hacky\n\nin https://github.com/apache/spark/pull/10133 we found that, we shoud ensure the children of `TreeNode` are all accessible in the `productIterator`, or the behavior will be very confusing.\n\nIn this PR, I try to fix this problem by expsing the `loopVar`.\n\nThis also fixes SPARK-12131 which is caused by the hacky `MapObjects`.\n\nAuthor: Wenchen Fan <wenchen@databricks.com>\n\nCloses #10239 from cloud-fan/map-objects.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/d8ec081c911a040f3fb523a68025928ae4afc906"},{"sha":"e29704f90dfe67d9e276d242699ac0a00f64fb91","author":{"email":"1a1ab5abfb65135a4f49eb66e79d9e570e28807d@us.ibm.com","name":"bomeng"},"message":"[SPARK-12136][STREAMING] rddToFileName does not properly handle prefix and suffix parameters\n\nThe original code does not properly handle the cases where the prefix is null, but suffix is not null - the suffix should be used but is not.\n\nThe fix is using StringBuilder to construct the proper file name.\n\nAuthor: bomeng <bmeng@us.ibm.com>\nAuthor: Bo Meng <mengbo@bos-macbook-pro.usca.ibm.com>\n\nCloses #10185 from bomeng/SPARK-12136.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/e29704f90dfe67d9e276d242699ac0a00f64fb91"},{"sha":"21b3d2a75f679b252e293000d706741dca33624a","author":{"email":"291c18f3fb7528c712d9098b0e50a515ea0b91d5@cloudera.com","name":"Sean Owen"},"message":"[SPARK-11530][MLLIB] Return eigenvalues with PCA model\n\nAdd `computePrincipalComponentsAndVariance` to also compute PCA's explained variance.\n\nCC mengxr\n\nAuthor: Sean Owen <sowen@cloudera.com>\n\nCloses #9736 from srowen/SPARK-11530.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/21b3d2a75f679b252e293000d706741dca33624a"},{"sha":"76540b6df5370b463277d3498097b2cc2d2e97a8","author":{"email":"c9d35a384bc579d1c6c8c055f2a2b5c04e11b521@databricks.com","name":"Reynold Xin"},"message":"[SPARK-12242][SQL] Add DataFrame.transform method\n\nAuthor: Reynold Xin <rxin@databricks.com>\n\nCloses #10226 from rxin/df-transform.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/76540b6df5370b463277d3498097b2cc2d2e97a8"},{"sha":"db5165246f2888537dd0f3d4c5a515875c7358ed","author":{"email":"249f1848d407dd74af9592a86811fcca179f01b2@gmail.com","name":"Jakob Odersky"},"message":"[SPARK-11832][CORE] Process arguments in spark-shell for Scala 2.11\n\nProcess arguments passed to the spark-shell. Fixes running the spark-shell from within a build environment.\n\nAuthor: Jakob Odersky <jodersky@gmail.com>\n\nCloses #9824 from jodersky/shell-2.11.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/db5165246f2888537dd0f3d4c5a515875c7358ed"},{"sha":"eeb58722ad73441eeb5f35f864be3c5392cfd426","author":{"email":"452ae006f36be6c70342f33f64bb6f6eb552689c@gmail.com","name":"Yanbo Liang"},"message":"[SPARK-12198][SPARKR] SparkR support read.parquet and deprecate parquetFile\n\nSparkR support ```read.parquet``` and deprecate ```parquetFile```. This change is similar with #10145 for ```jsonFile```.\n\nAuthor: Yanbo Liang <ybliang8@gmail.com>\n\nCloses #10191 from yanboliang/spark-12198.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/eeb58722ad73441eeb5f35f864be3c5392cfd426"},{"sha":"9fba9c8004d2b97549e5456fa7918965bec27336","author":{"email":"66332c93c294b372ab1bdd5acb9b89a538e2d2f2@gmail.com","name":"Yuhao Yang"},"message":"[SPARK-11602][MLLIB] Refine visibility for 1.6 scala API audit\n\njira: https://issues.apache.org/jira/browse/SPARK-11602\n\nMade a pass on the API change of 1.6. Open the PR for efficient discussion.\n\nAuthor: Yuhao Yang <hhbyyh@gmail.com>\n\nCloses #9939 from hhbyyh/auditScala.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/9fba9c8004d2b97549e5456fa7918965bec27336"},{"sha":"d9d354ed40eec56b3f03d32f4e2629d367b1bf02","author":{"email":"452ae006f36be6c70342f33f64bb6f6eb552689c@gmail.com","name":"Yanbo Liang"},"message":"[SPARK-12234][SPARKR] Fix ```subset``` function error when only set ```select``` argument\n\nFix ```subset``` function error when only set ```select``` argument. Please refer to the [JIRA](https://issues.apache.org/jira/browse/SPARK-12234) about the error and how to reproduce it.\n\ncc sun-rui felixcheung shivaram\n\nAuthor: Yanbo Liang <ybliang8@gmail.com>\n\nCloses #10217 from yanboliang/spark-12234.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/d9d354ed40eec56b3f03d32f4e2629d367b1bf02"},{"sha":"bc5f56aa60a430244ffa0cacd81c0b1ecbf8d68f","author":{"email":"8adc4758e0403b3bd961e4e414291eaa9ba64098@databricks.com","name":"Yin Huai"},"message":"[SPARK-12250][SQL] Allow users to define a UDAF without providing details of its inputSchema\n\nhttps://issues.apache.org/jira/browse/SPARK-12250\n\nAuthor: Yin Huai <yhuai@databricks.com>\n\nCloses #10236 from yhuai/SPARK-12250.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/bc5f56aa60a430244ffa0cacd81c0b1ecbf8d68f"},{"sha":"ec5f9ed5de2218938dba52152475daafd4dc4786","author":{"email":"8adc4758e0403b3bd961e4e414291eaa9ba64098@databricks.com","name":"Yin Huai"},"message":"[SPARK-12228][SQL] Try to run execution hive's derby in memory.\n\nThis PR tries to make execution hive's derby run in memory since it is a fake metastore and every time we create a HiveContext, we will switch to a new one. It is possible that it can reduce the flakyness of our tests that need to create HiveContext (e.g. HiveSparkSubmitSuite). I will test it more.\n\nhttps://issues.apache.org/jira/browse/SPARK-12228\n\nAuthor: Yin Huai <yhuai@databricks.com>\n\nCloses #10204 from yhuai/derbyInMemory.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/ec5f9ed5de2218938dba52152475daafd4dc4786"},{"sha":"2ecbe02d5b28ee562d10c1735244b90a08532c9e","author":{"email":"5a279bc90c6f3ee7b2e009f7070db93eec368853@databricks.com","name":"Timothy Hunter"},"message":"[SPARK-12212][ML][DOC] Clarifies the difference between spark.ml, spark.mllib and mllib in the documentation.\n\nReplaces a number of occurences of `MLlib` in the documentation that were meant to refer to the `spark.mllib` package instead. It should clarify for new users the difference between `spark.mllib` (the package) and MLlib (the umbrella project for ML in spark).\n\nIt also removes some files that I forgot to delete with #10207\n\nAuthor: Timothy Hunter <timhunter@databricks.com>\n\nCloses #10234 from thunterdb/12212.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/2ecbe02d5b28ee562d10c1735244b90a08532c9e"},{"sha":"4a46b8859d3314b5b45a67cdc5c81fecb6e9e78c","author":{"email":"8283fd24ce58e0bb0d6bf349e9064fef42c4d84e@cloudera.com","name":"Marcelo Vanzin"},"message":"[SPARK-11563][CORE][REPL] Use RpcEnv to transfer REPL-generated classes.\n\nThis avoids bringing up yet another HTTP server on the driver, and\ninstead reuses the file server already managed by the driver's\nRpcEnv. As a bonus, the repl now inherits the security features of\nthe network library.\n\nThere's also a small change to create the directory for storing classes\nunder the root temp dir for the application (instead of directly\nunder java.io.tmpdir).\n\nAuthor: Marcelo Vanzin <vanzin@cloudera.com>\n\nCloses #9923 from vanzin/SPARK-11563.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/4a46b8859d3314b5b45a67cdc5c81fecb6e9e78c"},{"sha":"6a6c1fc5c807ba4e8aba3e260537aa527ff5d46a","author":{"email":"0510f24c259a4f603c85979def2fe3bfbef1c219@us.ibm.com","name":"Bryan Cutler"},"message":"[SPARK-11713] [PYSPARK] [STREAMING] Initial RDD updateStateByKey for PySpark\n\nAdding ability to define an initial state RDD for use with updateStateByKey PySpark.  Added unit test and changed stateful_network_wordcount example to use initial RDD.\n\nAuthor: Bryan Cutler <bjcutler@us.ibm.com>\n\nCloses #10082 from BryanCutler/initial-rdd-updateStateByKey-SPARK-11713.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/6a6c1fc5c807ba4e8aba3e260537aa527ff5d46a"},{"sha":"23a9e62bad9669e9ff5dc4bd714f58d12f9be0b5","author":{"email":"e5dd8a3899598b2e85930c5ff06b11c053ef654f@databricks.com","name":"Josh Rosen"},"message":"[SPARK-12251] Document and improve off-heap memory configurations\n\nThis patch adds documentation for Spark configurations that affect off-heap memory and makes some naming and validation improvements for those configs.\n\n- Change `spark.memory.offHeapSize` to `spark.memory.offHeap.size`. This is fine because this configuration has not shipped in any Spark release yet (it's new in Spark 1.6).\n- Deprecated `spark.unsafe.offHeap` in favor of a new `spark.memory.offHeap.enabled` configuration. The motivation behind this change is to gather all memory-related configurations under the same prefix.\n- Add a check which prevents users from setting `spark.memory.offHeap.enabled=true` when `spark.memory.offHeap.size == 0`. After SPARK-11389 (#9344), which was committed in Spark 1.6, Spark enforces a hard limit on the amount of off-heap memory that it will allocate to tasks. As a result, enabling off-heap execution memory without setting `spark.memory.offHeap.size` will lead to immediate OOMs. The new configuration validation makes this scenario easier to diagnose, helping to avoid user confusion.\n- Document these configurations on the configuration page.\n\nAuthor: Josh Rosen <joshrosen@databricks.com>\n\nCloses #10237 from JoshRosen/SPARK-12251.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/23a9e62bad9669e9ff5dc4bd714f58d12f9be0b5"},{"sha":"5030923ea8bb94ac8fa8e432de9fc7089aa93986","author":{"email":"02e0a999c50b1f88df7a8f5a04e1b76b35ea6a88@databricks.com","name":"Andrew Or"},"message":"[SPARK-12155][SPARK-12253] Fix executor OOM in unified memory management\n\n**Problem.** In unified memory management, acquiring execution memory may lead to eviction of storage memory. However, the space freed from evicting cached blocks is distributed among all active tasks. Thus, an incorrect upper bound on the execution memory per task can cause the acquisition to fail, leading to OOM's and premature spills.\n\n**Example.** Suppose total memory is 1000B, cached blocks occupy 900B, `spark.memory.storageFraction` is 0.4, and there are two active tasks. In this case, the cap on task execution memory is 100B / 2 = 50B. If task A tries to acquire 200B, it will evict 100B of storage but can only acquire 50B because of the incorrect cap. For another example, see this [regression test](https://github.com/andrewor14/spark/blob/fix-oom/core/src/test/scala/org/apache/spark/memory/UnifiedMemoryManagerSuite.scala#L233) that I stole from JoshRosen.\n\n**Solution.** Fix the cap on task execution memory. It should take into account the space that could have been freed by storage in addition to the current amount of memory available to execution. In the example above, the correct cap should have been 600B / 2 = 300B.\n\nThis patch also guards against the race condition (SPARK-12253):\n(1) Existing tasks collectively occupy all execution memory\n(2) New task comes in and blocks while existing tasks spill\n(3) After tasks finish spilling, another task jumps in and puts in a large block, stealing the freed memory\n(4) New task still cannot acquire memory and goes back to sleep\n\nAuthor: Andrew Or <andrew@databricks.com>\n\nCloses #10240 from andrewor14/fix-oom.","distinct":false,"url":"https://api.github.com/repos/holdenk/spark/commits/5030923ea8bb94ac8fa8e432de9fc7089aa93986"}]}