spark git commit: [Minor] [Core] Don't NPE on closeQuietly(null)

2014-11-08 Thread rxin
Repository: spark Updated Branches: refs/heads/master 7afc8564f - 4af5c7e24 [Minor] [Core] Don't NPE on closeQuietly(null) Author: Aaron Davidson aa...@databricks.com Closes #3166 from aarondav/closeQuietlyer and squashes the following commits: 78096b5 [Aaron Davidson] Don't NPE on

spark git commit: [Minor] [Core] Don't NPE on closeQuietly(null)

2014-11-08 Thread rxin
Repository: spark Updated Branches: refs/heads/branch-1.2 fc51de339 - 05bffcc02 [Minor] [Core] Don't NPE on closeQuietly(null) Author: Aaron Davidson aa...@databricks.com Closes #3166 from aarondav/closeQuietlyer and squashes the following commits: 78096b5 [Aaron Davidson] Don't NPE on

spark git commit: [SPARK-4301] StreamingContext should not allow start() to be called after calling stop()

2014-11-08 Thread tdas
Repository: spark Updated Branches: refs/heads/master 4af5c7e24 - 7b41b17f3 [SPARK-4301] StreamingContext should not allow start() to be called after calling stop() In Spark 1.0.0+, calling `stop()` on a StreamingContext that has not been started is a no-op which has no side-effects. This

spark git commit: [SPARK-4301] StreamingContext should not allow start() to be called after calling stop()

2014-11-08 Thread tdas
Repository: spark Updated Branches: refs/heads/branch-1.2 05bffcc02 - 21b9ac062 [SPARK-4301] StreamingContext should not allow start() to be called after calling stop() In Spark 1.0.0+, calling `stop()` on a StreamingContext that has not been started is a no-op which has no side-effects.

spark git commit: [SPARK-4301] StreamingContext should not allow start() to be called after calling stop()

2014-11-08 Thread tdas
Repository: spark Updated Branches: refs/heads/branch-1.1 4895f6544 - 78cd3ab88 [SPARK-4301] StreamingContext should not allow start() to be called after calling stop() In Spark 1.0.0+, calling `stop()` on a StreamingContext that has not been started is a no-op which has no side-effects.

spark git commit: [SPARK-4301] StreamingContext should not allow start() to be called after calling stop()

2014-11-08 Thread tdas
Repository: spark Updated Branches: refs/heads/branch-1.0 d4aed266d - 395656c8e [SPARK-4301] StreamingContext should not allow start() to be called after calling stop() In Spark 1.0.0+, calling `stop()` on a StreamingContext that has not been started is a no-op which has no side-effects.