Skip to content
Snippets Groups Projects
  1. Jun 08, 2017
    • Mark Grover's avatar
      [SPARK-19185][DSTREAM] Make Kafka consumer cache configurable · 55b8cfe6
      Mark Grover authored
      ## What changes were proposed in this pull request?
      
      Add a new property `spark.streaming.kafka.consumer.cache.enabled` that allows users to enable or disable the cache for Kafka consumers. This property can be especially handy in cases where issues like SPARK-19185 get hit, for which there isn't a solution committed yet. By default, the cache is still on, so this change doesn't change any out-of-box behavior.
      
      ## How was this patch tested?
      Running unit tests
      
      Author: Mark Grover <mark@apache.org>
      Author: Mark Grover <grover.markgrover@gmail.com>
      
      Closes #18234 from markgrover/spark-19185.
      55b8cfe6
    • hyukjinkwon's avatar
      [INFRA] Close stale PRs · b771fed7
      hyukjinkwon authored
      # What changes were proposed in this pull request?
      
      This PR proposes to close stale PRs, mostly the same instances with https://github.com/apache/spark/pull/18017
      
      Closes #11459
      Closes #13833
      Closes #13720
      Closes #12506
      Closes #12456
      Closes #12252
      Closes #17689
      Closes #17791
      Closes #18163
      Closes #17640
      Closes #17926
      Closes #18163
      Closes #12506
      Closes #18044
      Closes #14036
      Closes #15831
      Closes #14461
      Closes #17638
      Closes #18222
      
      Added:
      Closes #18045
      Closes #18061
      Closes #18010
      Closes #18041
      Closes #18124
      Closes #18130
      Closes #12217
      
      Added:
      Closes #16291
      Closes #17480
      Closes #14995
      
      Added:
      Closes #12835
      Closes #17141
      
      ## How was this patch tested?
      
      N/A
      
      Author: hyukjinkwon <gurwls223@gmail.com>
      
      Closes #18223 from HyukjinKwon/close-stale-prs.
      b771fed7
    • 10087686's avatar
      [SPARK-21006][TESTS] Create rpcEnv and run later needs shutdown and awaitTermination · 9be79458
      10087686 authored
      Signed-off-by: 10087686 <wang.jiaochunzte.com.cn>
      
      ## What changes were proposed in this pull request?
      When  run test("port conflict") case, we need run anotherEnv.shutdown() and anotherEnv.awaitTermination() for free resource.
      (Please fill in changes proposed in this fix)
      
      ## How was this patch tested?
      run RpcEnvSuit.scala Utest
      (Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
      (If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
      
      Please review http://spark.apache.org/contributing.html before opening a pull request.
      
      Author: 10087686 <wang.jiaochun@zte.com.cn>
      
      Closes #18226 from wangjiaochun/master.
      9be79458
    • Sean Owen's avatar
      [SPARK-20914][DOCS] Javadoc contains code that is invalid · 847efe12
      Sean Owen authored
      ## What changes were proposed in this pull request?
      
      Fix Java, Scala Dataset examples in scaladoc, which didn't compile.
      
      ## How was this patch tested?
      
      Existing compilation/test
      
      Author: Sean Owen <sowen@cloudera.com>
      
      Closes #18215 from srowen/SPARK-20914.
      847efe12
  2. Jun 07, 2017
  3. Jun 06, 2017
    • Marcelo Vanzin's avatar
      [SPARK-20641][CORE] Add key-value store abstraction and LevelDB implementation. · 0cba4951
      Marcelo Vanzin authored
      This change adds an abstraction and LevelDB implementation for a key-value
      store that will be used to store UI and SHS data.
      
      The interface is described in KVStore.java (see javadoc). Specifics
      of the LevelDB implementation are discussed in the javadocs of both
      LevelDB.java and LevelDBTypeInfo.java.
      
      Included also are a few small benchmarks just to get some idea of
      latency. Because they're too slow for regular unit test runs, they're
      disabled by default.
      
      Tested with the included unit tests, and also as part of the overall feature
      implementation (including running SHS with hundreds of apps).
      
      Author: Marcelo Vanzin <vanzin@cloudera.com>
      
      Closes #17902 from vanzin/shs-ng/M1.
      0cba4951
    • Reza Safi's avatar
      [SPARK-20926][SQL] Removing exposures to guava library caused by directly... · b61a401d
      Reza Safi authored
      [SPARK-20926][SQL] Removing exposures to guava library caused by directly accessing  SessionCatalog's tableRelationCache
      
      There could be test failures because DataStorageStrategy, HiveMetastoreCatalog and also HiveSchemaInferenceSuite were exposed to guava library by directly accessing SessionCatalog's tableRelationCacheg. These failures occur when guava shading is in place.
      
      ## What changes were proposed in this pull request?
      This change removes those guava exposures by introducing new methods in SessionCatalog and also changing DataStorageStrategy, HiveMetastoreCatalog and HiveSchemaInferenceSuite so that they use those proxy methods.
      
      ## How was this patch tested?
      
      Unit tests passed after applying these changes.
      
      Author: Reza Safi <rezasafi@cloudera.com>
      
      Closes #18148 from rezasafi/branch-2.2.
      
      (cherry picked from commit 1388fdd7)
      b61a401d
    • jinxing's avatar
      [SPARK-20985] Stop SparkContext using LocalSparkContext.withSpark · 44de108d
      jinxing authored
      ## What changes were proposed in this pull request?
      SparkContext should always be stopped after using, thus other tests won't complain that there's only one `SparkContext` can exist.
      
      Author: jinxing <jinxing6042@126.com>
      
      Closes #18204 from jinxing64/SPARK-20985.
      44de108d
  4. Jun 05, 2017
    • Feng Liu's avatar
      [SPARK-20991][SQL] BROADCAST_TIMEOUT conf should be a TimeoutConf · 88a23d3d
      Feng Liu authored
      ## What changes were proposed in this pull request?
      
      The construction of BROADCAST_TIMEOUT conf should take the TimeUnit argument as a TimeoutConf.
      
      Author: Feng Liu <fengliu@databricks.com>
      
      Closes #18208 from liufengdb/fix_timeout.
      88a23d3d
    • Shixiong Zhu's avatar
      [SPARK-20957][SS][TESTS] Fix o.a.s.sql.streaming.StreamingQueryManagerSuite listing · bc537e40
      Shixiong Zhu authored
      ## What changes were proposed in this pull request?
      
      When stopping StreamingQuery, StreamExecution will set `streamDeathCause` then notify StreamingQueryManager to remove this query. So it's possible that when `q2.exception.isDefined` returns `true`, StreamingQueryManager's active list still has `q2`.
      
      This PR just puts the checks into `eventually` to fix the flaky test.
      
      ## How was this patch tested?
      
      Jenkins
      
      Author: Shixiong Zhu <shixiong@databricks.com>
      
      Closes #18180 from zsxwing/SPARK-20957.
      bc537e40
    • jerryshao's avatar
      [SPARK-20981][SPARKSUBMIT] Add new configuration spark.jars.repositories as... · 06c05441
      jerryshao authored
      [SPARK-20981][SPARKSUBMIT] Add new configuration spark.jars.repositories as equivalence of --repositories
      
      ## What changes were proposed in this pull request?
      
      In our use case of launching Spark applications via REST APIs (Livy), there's no way for user to specify command line arguments, all Spark configurations are set through configurations map. For "--repositories" because there's no equivalent Spark configuration, so we cannot specify the custom repository through configuration.
      
      So here propose to add "--repositories" equivalent configuration in Spark.
      
      ## How was this patch tested?
      
      New UT added.
      
      Author: jerryshao <sshao@hortonworks.com>
      
      Closes #18201 from jerryshao/SPARK-20981.
      06c05441
    • sethah's avatar
      [SPARK-19762][ML] Hierarchy for consolidating ML aggregator/loss code · 1665b5f7
      sethah authored
      ## What changes were proposed in this pull request?
      
      JIRA: [SPARK-19762](https://issues.apache.org/jira/browse/SPARK-19762)
      
      The larger changes in this patch are:
      
      * Adds a `DifferentiableLossAggregator` trait which is intended to be used as a common parent trait to all Spark ML aggregator classes. It factors out the common methods: `merge, gradient, loss, weight` from the aggregator subclasses.
      * Adds a `RDDLossFunction` which is intended to be the only implementation of Breeze's `DiffFunction` necessary in Spark ML, and can be used by all other algorithms. It takes the aggregator type as a type parameter, and maps the aggregator over an RDD. It additionally takes in a optional regularization loss function for applying the differentiable part of regularization.
      * Factors out the regularization from the data part of the cost function, and treats regularization as a separate independent cost function which can be evaluated and added to the data cost function.
      * Changes `LinearRegression` to use this new hierarchy as a proof of concept.
      * Adds the following new namespaces `o.a.s.ml.optim.loss` and `o.a.s.ml.optim.aggregator`
      
      Also note that none of these are public-facing changes. All of these classes are internal to Spark ML and remain that way.
      
      **NOTE: The large majority of the "lines added" and "lines deleted" are simply code moving around or unit tests.**
      
      BTW, I also converted LinearSVC to this framework as a way to prove that this new hierarchy is flexible enough for the other algorithms, but I backed those changes out because the PR is large enough as is.
      
      ## How was this patch tested?
      Test suites are added for the new components, and some test suites are also added to provide coverage where there wasn't any before.
      
      * DifferentiablLossAggregatorSuite
      * LeastSquaresAggregatorSuite
      * RDDLossFunctionSuite
      * DifferentiableRegularizationSuite
      
      Below are some performance testing numbers. Run on a 6 node virtual cluster with 44 cores and ~110G RAM, the dataset size is about 37G. These are not "large-scale" tests, but we really want to just make sure the iteration times don't increase with this patch. Notably we are doing the regularization a bit differently than before, but that should cost very little. I think there's very little risk otherwise, and these numbers don't show a difference. Of course I'm happy to add more tests as we think it's necessary, but I think the patch is ready for review now.
      
      **Note:** timings are best of 3 runs.
      
      |    |   numFeatures |   numPoints |   maxIter |   regParam |   elasticNetParam |   SPARK-19762 (sec) |   master (sec) |
      |----|---------------|-------------|-----------|------------|-------------------|---------------------|----------------|
      |  0 |          5000 |       1e+06 |        30 |       0    |               0   |             129.594 |        131.153 |
      |  1 |          5000 |       1e+06 |        30 |       0.1  |               0   |             135.54  |        136.327 |
      |  2 |          5000 |       1e+06 |        30 |       0.01 |               0.5 |             135.148 |        129.771 |
      |  3 |         50000 |  100000     |        30 |       0    |               0   |             145.764 |        144.096 |
      
      ## Follow ups
      
      If this design is accepted, we will convert the other ML algorithms that use this aggregator pattern to this new hierarchy in follow up PRs.
      
      Author: sethah <seth.hendrickson16@gmail.com>
      Author: sethah <shendrickson@cloudera.com>
      
      Closes #17094 from sethah/ml_aggregators.
      1665b5f7
    • Zheng RuiFeng's avatar
      [SPARK-20930][ML] Destroy broadcasted centers after computing cost in KMeans · 98b5ccd3
      Zheng RuiFeng authored
      ## What changes were proposed in this pull request?
       Destroy broadcasted centers after computing cost
      ## How was this patch tested?
      existing tests
      
      Author: Zheng RuiFeng <ruifengz@foxmail.com>
      
      Closes #18152 from zhengruifeng/destroy_kmeans_model.
      98b5ccd3
    • liupengcheng's avatar
      [SPARK-20945] Fix TID key not found in TaskSchedulerImpl · 2d39711b
      liupengcheng authored
      ## What changes were proposed in this pull request?
      
      This pull request fix the TaskScheulerImpl bug in some condition.
      Detail see:
      https://issues.apache.org/jira/browse/SPARK-20945
      
      (Please fill in changes proposed in this fix)
      
      ## How was this patch tested?
      manual tests
      (Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
      (If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
      
      Please review http://spark.apache.org/contributing.html before opening a pull request.
      
      Author: liupengcheng <liupengcheng@xiaomi.com>
      Author: PengchengLiu <pengchengliu_bupt@163.com>
      
      Closes #18171 from liupc/Fix-tid-key-not-found-in-TaskSchedulerImpl.
      2d39711b
  5. Jun 04, 2017
  6. Jun 03, 2017
    • Wieland Hoffmann's avatar
      [DOCS] Fix a typo in Encoder.clsTag · c70c38eb
      Wieland Hoffmann authored
      ## What changes were proposed in this pull request?
      
      Fixes a typo: `and` -> `an`
      
      ## How was this patch tested?
      
      Not at all.
      
      Author: Wieland Hoffmann <mineo@users.noreply.github.com>
      
      Closes #17759 from mineo/patch-1.
      c70c38eb
    • zuotingbing's avatar
      [SPARK-20936][CORE] Lack of an important case about the test of resolveURI in... · 887cf0ec
      zuotingbing authored
      [SPARK-20936][CORE] Lack of an important case about the test of resolveURI in UtilsSuite, and add it as needed.
      
      ## What changes were proposed in this pull request?
      1.  add `assert(resolve(before) === after)` to check before and after in test of resolveURI.
      the function `assertResolves(before: String, after: String)` have two params, it means we should check the before value whether equals the after value which we want.
      e.g. the after value of Utils.resolveURI("hdfs:///root/spark.jar#app.jar").toString should be "hdfs:///root/spark.jar#app.jar" rather than "hdfs:/root/spark.jar#app.jar". we need `assert(resolve(before) === after)` to make it more safe.
      2. identify the cases between resolveURI and resolveURIs.
      3. delete duplicate cases and some small fix make this suit more clear.
      
      ## How was this patch tested?
      
      unit tests
      
      Author: zuotingbing <zuo.tingbing9@zte.com.cn>
      
      Closes #18158 from zuotingbing/spark-UtilsSuite.
      887cf0ec
    • David Eis's avatar
      [SPARK-20790][MLLIB] Remove extraneous logging in test · 96e6ba6c
      David Eis authored
      ## What changes were proposed in this pull request?
      
      Remove extraneous logging.
      
      ## How was this patch tested?
      
      Unit tests pass.
      
      Author: David Eis <deis@bloomberg.net>
      
      Closes #18188 from davideis/fix-test.
      96e6ba6c
    • Ruben Berenguel Montoro's avatar
      [SPARK-19732][SQL][PYSPARK] Add fill functions for nulls in bool fields of datasets · 6cbc61d1
      Ruben Berenguel Montoro authored
      ## What changes were proposed in this pull request?
      
      Allow fill/replace of NAs with booleans, both in Python and Scala
      
      ## How was this patch tested?
      
      Unit tests, doctests
      
      This PR is original work from me and I license this work to the Spark project
      
      Author: Ruben Berenguel Montoro <ruben@mostlymaths.net>
      Author: Ruben Berenguel <ruben@mostlymaths.net>
      
      Closes #18164 from rberenguel/SPARK-19732-fillna-bools.
      6cbc61d1
  7. Jun 02, 2017
  8. Jun 01, 2017
    • Bogdan Raducanu's avatar
      [SPARK-20854][SQL] Extend hint syntax to support expressions · 2134196a
      Bogdan Raducanu authored
      ## What changes were proposed in this pull request?
      
      SQL hint syntax:
      * support expressions such as strings, numbers, etc. instead of only identifiers as it is currently.
      * support multiple hints, which was missing compared to the DataFrame syntax.
      
      DataFrame API:
      * support any parameters in DataFrame.hint instead of just strings
      
      ## How was this patch tested?
      Existing tests. New tests in PlanParserSuite. New suite DataFrameHintSuite.
      
      Author: Bogdan Raducanu <bogdan@databricks.com>
      
      Closes #18086 from bogdanrdc/SPARK-20854.
      2134196a
    • Marcelo Vanzin's avatar
      [SPARK-20922][CORE] Add whitelist of classes that can be deserialized by the launcher. · 8efc6e98
      Marcelo Vanzin authored
      Blindly deserializing classes using Java serialization opens the code up to
      issues in other libraries, since just deserializing data from a stream may
      end up execution code (think readObject()).
      
      Since the launcher protocol is pretty self-contained, there's just a handful
      of classes it legitimately needs to deserialize, and they're in just two
      packages, so add a filter that throws errors if classes from any other
      package show up in the stream.
      
      This also maintains backwards compatibility (the updated launcher code can
      still communicate with the backend code in older Spark releases).
      
      Tested with new and existing unit tests.
      
      Author: Marcelo Vanzin <vanzin@cloudera.com>
      
      Closes #18166 from vanzin/SPARK-20922.
      8efc6e98
    • Li Yichao's avatar
      [SPARK-20365][YARN] Remove local scheme when add path to ClassPath. · 640afa49
      Li Yichao authored
      In Spark on YARN, when configuring "spark.yarn.jars" with local jars (jars started with "local" scheme), we will get inaccurate classpath for AM and containers. This is because we don't remove "local" scheme when concatenating classpath. It is OK to run because classpath is separated with ":" and java treat "local" as a separate jar. But we could improve it to remove the scheme.
      
      Updated `ClientSuite` to check "local" is not in the classpath.
      
      cc jerryshao
      
      Author: Li Yichao <lyc@zhihu.com>
      Author: Li Yichao <liyichao.good@gmail.com>
      
      Closes #18129 from liyichao/SPARK-20365.
      640afa49
    • Xiao Li's avatar
      [SPARK-20941][SQL] Fix SubqueryExec Reuse · f7cf2096
      Xiao Li authored
      ### What changes were proposed in this pull request?
      Before this PR, Subquery reuse does not work. Below are three issues:
      - Subquery reuse does not work.
      - It is sharing the same `SQLConf` (`spark.sql.exchange.reuse`) with the one for Exchange Reuse.
      - No test case covers the rule Subquery reuse.
      
      This PR is to fix the above three issues.
      - Ignored the physical operator `SubqueryExec` when comparing two plans.
      - Added a dedicated conf `spark.sql.subqueries.reuse` for controlling Subquery Reuse
      - Added a test case for verifying the behavior
      
      ### How was this patch tested?
      N/A
      
      Author: Xiao Li <gatorsmile@gmail.com>
      
      Closes #18169 from gatorsmile/subqueryReuse.
      f7cf2096
    • John Compitello's avatar
      [SPARK-20109][MLLIB] Rewrote toBlockMatrix method on IndexedRowMatrix · 0975019c
      John Compitello authored
      ## What changes were proposed in this pull request?
      
      - ~~I added the method `toBlockMatrixDense` to the IndexedRowMatrix class. The current implementation of `toBlockMatrix` is insufficient for users with relatively dense IndexedRowMatrix objects, since it assumes sparsity.~~
      
      EDIT: Ended up deciding that there should be just a single `toBlockMatrix` method, which creates a BlockMatrix whose blocks may be dense or sparse depending on the sparsity of the rows. This method will work better on any current use case of `toBlockMatrix` and doesn't go through `CoordinateMatrix` like the old method.
      
      ## How was this patch tested?
      
      ~~I used the same tests already written for `toBlockMatrix()` to test this method. I also added a new additional unit test for an edge case that was not adequately tested by current test suite.~~
      
      I ran the original `IndexedRowMatrix` tests, plus wrote more to better handle edge cases ignored by original tests.
      
      Author: John Compitello <johnc@broadinstitute.org>
      
      Closes #17459 from johnc1231/johnc-fix-ir-to-block.
      0975019c
    • Yuming Wang's avatar
      [SPARK-20910][SQL] Add build-in SQL function - UUID · 6d05c1c1
      Yuming Wang authored
      ## What changes were proposed in this pull request?
      
      Add build-int SQL function - UUID.
      
      ## How was this patch tested?
      
      unit tests
      
      Author: Yuming Wang <wgyumg@gmail.com>
      
      Closes #18136 from wangyum/SPARK-20910.
      6d05c1c1
    • Yuming Wang's avatar
      [MINOR][SQL] Fix a few function description error. · c8045f8b
      Yuming Wang authored
      ## What changes were proposed in this pull request?
      
      Fix a few function description error.
      
      ## How was this patch tested?
      
      manual tests
      
      ![descissues](https://cloud.githubusercontent.com/assets/5399861/26619392/d547736c-4610-11e7-85d7-aeeb09c02cc8.gif)
      
      Author: Yuming Wang <wgyumg@gmail.com>
      
      Closes #18157 from wangyum/DescIssues.
      c8045f8b
    • Dongjoon Hyun's avatar
      [SPARK-20708][CORE] Make `addExclusionRules` up-to-date · 34661d8a
      Dongjoon Hyun authored
      ## What changes were proposed in this pull request?
      
      Since [SPARK-9263](https://issues.apache.org/jira/browse/SPARK-9263), `resolveMavenCoordinates` ignores Spark and Spark's dependencies by using `addExclusionRules`. This PR aims to make [addExclusionRules](https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala#L956-L974) up-to-date to neglect correctly because it fails to neglect some components like the following.
      
      **mllib (correct)**
      ```
      $ bin/spark-shell --packages org.apache.spark:spark-mllib_2.11:2.1.1
      ...
      ---------------------------------------------------------------------
      |                  |            modules            ||   artifacts   |
      |       conf       | number| search|dwnlded|evicted|| number|dwnlded|
      ---------------------------------------------------------------------
      |      default     |   0   |   0   |   0   |   0   ||   0   |   0   |
      ---------------------------------------------------------------------
      ```
      
      **mllib-local (wrong)**
      ```
      $ bin/spark-shell --packages org.apache.spark:spark-mllib-local_2.11:2.1.1
      ...
      ---------------------------------------------------------------------
      |                  |            modules            ||   artifacts   |
      |       conf       | number| search|dwnlded|evicted|| number|dwnlded|
      ---------------------------------------------------------------------
      |      default     |   15  |   2   |   2   |   0   ||   15  |   2   |
      ---------------------------------------------------------------------
      ```
      
      ## How was this patch tested?
      
      Pass the Jenkins with a updated test case.
      
      Author: Dongjoon Hyun <dongjoon@apache.org>
      
      Closes #17947 from dongjoon-hyun/SPARK-20708.
      34661d8a
    • jerryshao's avatar
      [SPARK-20244][CORE] Handle incorrect bytesRead metrics when using PySpark · 5854f77c
      jerryshao authored
      ## What changes were proposed in this pull request?
      
      Hadoop FileSystem's statistics in based on thread local variables, this is ok if the RDD computation chain is running in the same thread. But if child RDD creates another thread to consume the iterator got from Hadoop RDDs, the bytesRead computation will be error, because now the iterator's `next()` and `close()` may run in different threads. This could be happened when using PySpark with PythonRDD.
      
      So here building a map to track the `bytesRead` for different thread and add them together. This method will be used in three RDDs, `HadoopRDD`, `NewHadoopRDD` and `FileScanRDD`. I assume `FileScanRDD` cannot be called directly, so I only fixed `HadoopRDD` and `NewHadoopRDD`.
      
      ## How was this patch tested?
      
      Unit test and local cluster verification.
      
      Author: jerryshao <sshao@hortonworks.com>
      
      Closes #17617 from jerryshao/SPARK-20244.
      5854f77c
Loading