Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2264#issuecomment-54703741
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2264#issuecomment-54703751
LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2164#issuecomment-54703762
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2262#issuecomment-54703774
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2247#issuecomment-54703802
Ok I'm going to close this for now given the debate.
@mridulm it would be great to hear more about the performance difference.
It is hard for me to imagine a
Github user rxin closed the pull request at:
https://github.com/apache/spark/pull/2247
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2226#issuecomment-54703827
test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54703841
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user puravaggarwal closed the pull request at:
https://github.com/apache/spark/pull/89
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2297
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user puravaggarwal commented on the pull request:
https://github.com/apache/spark/pull/89#issuecomment-54703862
As per discussions above - closing the pull request
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2285#issuecomment-54703906
Can you change an old API to make sure this is reporting correctly?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2292#issuecomment-54704106
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2259#issuecomment-54704111
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2288#issuecomment-54704149
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2294#issuecomment-54704308
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19896/consoleFull)
for PR 2294 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2264#issuecomment-54704437
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19902/consoleFull)
for PR 2264 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2164#issuecomment-54704448
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19905/consoleFull)
for PR 2164 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2262#issuecomment-54704440
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19903/consoleFull)
for PR 2262 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2259#issuecomment-54704441
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19904/consoleFull)
for PR 2259 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54704438
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19901/consoleFull)
for PR 2273 at commit
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/2298
[SPARK-938][doc] Add OpenStack Swift support
See compiled doc at
http://people.apache.org/~rxin/tmp/openstack-swift/_site/storage-openstack-swift.html
This is based on #1010.
You can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2281#issuecomment-54705097
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19898/consoleFull)
for PR 2281 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2282#issuecomment-54705275
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19897/consoleFull)
for PR 2282 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2164#issuecomment-54705322
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19905/consoleFull)
for PR 2164 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2282#issuecomment-54705320
Merging this in master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2282
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2281#issuecomment-54705341
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2264#issuecomment-54705417
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19902/consoleFull)
for PR 2264 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2259#issuecomment-54705444
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19904/consoleFull)
for PR 2259 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2281#issuecomment-54705491
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19907/consoleFull)
for PR 2281 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54705508
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19901/consoleFull)
for PR 2273 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2262#issuecomment-54706276
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19903/consoleFull)
for PR 2262 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54706606
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19908/consoleFull)
for PR 2273 at commit
Github user wardviaene commented on the pull request:
https://github.com/apache/spark/pull/2287#issuecomment-54707160
Hi @JoshRosen
The bug would only be triggered in a Class, that's why I initially wrote it
like that. My last commit removes the references to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2281#issuecomment-54707290
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19907/consoleFull)
for PR 2281 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2287#issuecomment-54707788
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19909/consoleFull)
for PR 2287 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2287#issuecomment-54707812
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19909/consoleFull)
for PR 2287 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2273#issuecomment-54707818
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19908/consoleFull)
for PR 2273 at commit
GitHub user mattf opened a pull request:
https://github.com/apache/spark/pull/2299
[SPARK-1701] Clarify slice vs partition in the programming guide
This is a partial solution to SPARK-1701, only addressing the
documentation confusion.
Additional work can be to actually
GitHub user mattf opened a pull request:
https://github.com/apache/spark/pull/2300
Provide a default PYSPARK_PYTHON for python/run_tests
Without this the version of python used in the test is not
recorded. The error is,
Testing with Python version:
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2290#issuecomment-54712456
Failed test seems unrelated.
```log
[error] Failed tests:
[error] org.apache.spark.deploy.SparkSubmitSuite
```
Jenkins, retest this please.
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2300#issuecomment-54712597
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19910/consoleFull)
for PR 2300 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2299#issuecomment-54712599
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19912/consoleFull)
for PR 2299 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2287#issuecomment-54712596
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19911/consoleFull)
for PR 2287 at commit
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2290#issuecomment-54712738
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user mattf opened a pull request:
https://github.com/apache/spark/pull/2302
[SPARK-1701] [PySpark] deprecated numSlices for numPartitions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattf/spark SPARK-1701-pyspark
GitHub user mattf opened a pull request:
https://github.com/apache/spark/pull/2303
[SPARK-1701] remove unnecessary use of numSlices from pyspark tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattf/spark
GitHub user mattf opened a pull request:
https://github.com/apache/spark/pull/2304
[SPARK-1701] [PySpark] remove slice terminology from python examples
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattf/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2299#issuecomment-54714137
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19912/consoleFull)
for PR 2299 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2290#issuecomment-54714148
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19917/consoleFull)
for PR 2290 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2304#issuecomment-54714149
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19915/consoleFull)
for PR 2304 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2300#issuecomment-54714156
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19910/consoleFull)
for PR 2300 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2302#issuecomment-54714150
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19913/consoleFull)
for PR 2302 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2301#issuecomment-54714152
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19916/consoleFull)
for PR 2301 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2303#issuecomment-54714147
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19914/consoleFull)
for PR 2303 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2287#issuecomment-54714249
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19911/consoleFull)
for PR 2287 at commit
Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/2299#issuecomment-54714295
This patch fails unit tests.
the failures are in the kafka tests and unrelated to this patch
---
If your project is set up for it, you can reply to this email
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2303#issuecomment-54715939
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19914/consoleFull)
for PR 2303 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2304#issuecomment-54716023
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19915/consoleFull)
for PR 2304 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2301#issuecomment-54716032
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19916/consoleFull)
for PR 2301 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2302#issuecomment-54716164
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19913/consoleFull)
for PR 2302 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2290#issuecomment-54716161
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19917/consoleFull)
for PR 2290 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2303#issuecomment-54716695
Hi @mattf,
It looks like you've opened four separate PRS (#2299, #2303, #2302, #2304)
for SPARK-1701. Since these all deal with the same JIRA, can you please
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2290#issuecomment-54716854
@JoshRosen This PR is good for review.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/2303#issuecomment-54716879
@JoshRosen only #2299 is truly for SPARK-1701, the others are tangentially
related so i tagged them along with 1701, but they can all stand alone. my hope
is that the
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2227#issuecomment-54717377
If you want to change the branch used for the pr you will need to close and
open a new one
Sent from my phone
On Sep 5, 2014, at 7:24 PM, Bill Bejeck
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2259#issuecomment-54718008
Jenkins, retest this please.
On Sat, Sep 6, 2014 at 12:40 AM, Apache Spark QA notificati...@github.com
wrote:
QA tests have finished
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2303#issuecomment-54718542
I'd still like for these to be combined into a single PR. Each additional
PR means another run of Jenkins tests, another commit message, another round of
emails /
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2303#issuecomment-54719377
Was your intent for us to merge / backport only the documentation fixes?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/1120#issuecomment-54719617
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-54720047
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19918/consoleFull)
for PR 1983 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1120#issuecomment-54720048
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19919/consoleFull)
for PR 1120 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1120#issuecomment-54721820
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19919/consoleFull)
for PR 1120 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1983#issuecomment-54722195
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19918/consoleFull)
for PR 1983 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2287#issuecomment-54722820
LGTM, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user sjbrunst commented on a diff in the pull request:
https://github.com/apache/spark/pull/1717#discussion_r17210353
--- Diff:
external/twitter/src/main/scala/org/apache/spark/streaming/twitter/TwitterInputDStream.scala
---
@@ -42,9 +44,19 @@ class TwitterInputDStream(
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2300#issuecomment-54723033
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user sjbrunst commented on a diff in the pull request:
https://github.com/apache/spark/pull/1717#discussion_r17210396
--- Diff:
external/twitter/src/main/scala/org/apache/spark/streaming/twitter/TwitterUtils.scala
---
@@ -33,15 +33,20 @@ object TwitterUtils {
*
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2247#issuecomment-54723134
Ok. I have filed a JIRA at https://issues.apache.org/jira/browse/SPARK-3426
---
If your project is set up for it, you can reply to this email and have your
reply
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/899#issuecomment-54723174
No worries. We can build on top of your patch to make this work for hadoop
versions 2.4. Thanks for digging through this code.
---
If your project is set up for it,
Github user mattf closed the pull request at:
https://github.com/apache/spark/pull/2303
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user mattf closed the pull request at:
https://github.com/apache/spark/pull/2302
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user mattf closed the pull request at:
https://github.com/apache/spark/pull/2304
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user mattf closed the pull request at:
https://github.com/apache/spark/pull/2299
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user mattf opened a pull request:
https://github.com/apache/spark/pull/2305
[SPARK-1701] Clarify slice vs partition in the programming guide
This is a partial solution to SPARK-1701, only addressing the
documentation confusion.
Additional work can be to actually
Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/2299#issuecomment-54723659
oops, i didn't realize renaming my branch would close this PR. i'll open
another.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2305#issuecomment-54724156
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19920/consoleFull)
for PR 2305 at commit
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1120#issuecomment-54724412
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1682#issuecomment-54726062
@ash211 This weekend, I'm actually working on writing a design document for
web UI improvements in Spark 1.2. SSL encryption, authentication, and ACLs are
all
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2305#issuecomment-54726088
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19920/consoleFull)
for PR 2305 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2287#discussion_r17210951
--- Diff: python/pyspark/tests.py ---
@@ -181,6 +181,18 @@ def tearDown(self):
sys.path = self._old_sys_path
+# Regression test
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/2287#discussion_r17210968
--- Diff: python/pyspark/tests.py ---
@@ -181,6 +181,18 @@ def tearDown(self):
sys.path = self._old_sys_path
+# Regression test
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2287#issuecomment-54726495
This looks fine to me, too, although I have two minor naming nits. Sorry
to be so nitpicky on the names and test code, but I'd like this code to be
really clean so
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2288#issuecomment-54726511
Jenkins, this is ok to test. Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/2241#issuecomment-54726521
test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2280#issuecomment-54726570
Jenkins, retest this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user cfregly opened a pull request:
https://github.com/apache/spark/pull/2306
[SPARK-1981][Streaming] Updated kinesis docs and added architecture diagram
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cfregly/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2306#issuecomment-54727680
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2288#issuecomment-54727745
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/19922/consoleFull)
for PR 2288 at commit
1 - 100 of 174 matches
Mail list logo
