Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9714#issuecomment-156690358
**[Test build #2059 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2059/consoleFull)**
for PR 9714 at commit
GitHub user RohanBhanderi opened a pull request:
https://github.com/apache/spark/pull/9714
Typo in comment: use 2 seconds instead of 1
Use 2 seconds batch size as duration specified in JavaStreamingContext
constructor is 2000 ms
You can merge this pull request into a Git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9714#issuecomment-156691120
**[Test build #2059 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2059/consoleFull)**
for PR 9714 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9714#issuecomment-156673111
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9714#issuecomment-156679953
OK. Any other comments like this that need a fix? might be worth looking at
related files.
---
If your project is set up for it, you can reply to this email and have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9714
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/9714#issuecomment-156697444
Merged to master/1.6
---
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 jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/9501#issuecomment-154572569
Thanks again @srowen! Next pull req should be from starter tag.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9501#issuecomment-154348664
Typos, maybe, or doc fixes. Some of these aren't fixes, or are just
whitespace changes. It's not worth the time, really, unless you're cleaning up
along the way to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9501#issuecomment-154349622
**[Test build #1996 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1996/consoleFull)**
for PR 9501 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9501#issuecomment-154383561
**[Test build #1996 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1996/consoleFull)**
for PR 9501 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9501#issuecomment-154518300
Merged to 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/9501
---
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 jaceklaskowski opened a pull request:
https://github.com/apache/spark/pull/9501
Typo fixes + code readability improvements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jaceklaskowski/spark typos-with-style
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9501#discussion_r44064323
--- Diff: core/src/main/scala/org/apache/spark/rdd/HadoopRDD.scala ---
@@ -195,9 +196,6 @@ class HadoopRDD[K, V](
// add the credentials here as this
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/9501#issuecomment-154199308
Thanks @srowen for reviewing the changes. They indeed are small since
they're the outcome of me going through the code and learning Spark this way.
When I run
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9501#issuecomment-154180634
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9501#issuecomment-154180340
Except one comment, all the changes look fine, but I'm not sure I think
it's a great use of time. Most of these are very marginal clarifications or
spacing fixes. I'd
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/9501#discussion_r44071949
--- Diff: core/src/main/scala/org/apache/spark/rdd/HadoopRDD.scala ---
@@ -195,9 +196,6 @@ class HadoopRDD[K, V](
// add the credentials here
GitHub user Mageswaran1989 opened a pull request:
https://github.com/apache/spark/pull/9333
Typo in mllib-evaluation-metrics.md
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mageswaran1989/spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9333#issuecomment-151861473
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
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9333#issuecomment-151888523
LGTM. Merged into master and backported to old branches. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9333
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8497#issuecomment-135657150
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
GitHub user dharmeshkakadia opened a pull request:
https://github.com/apache/spark/pull/8497
typo in comment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dharmeshkakadia/spark patch-2
Alternatively you can review and apply
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8497
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8497#issuecomment-135681438
OK too. I wouldn't mind if people took time to spell-check a whole file or
package rather than do one PR per typo, as it does cost time to process.
---
If your project
GitHub user Lewuathe opened a pull request:
https://github.com/apache/spark/pull/3412
Typo in Programming Guide markdown
Grammatical error in Programming Guide document
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3412#issuecomment-64065563
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
GitHub user jackylk opened a pull request:
https://github.com/apache/spark/pull/2809
typo in HiveFromSpark
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jackylk/spark patch-1
Alternatively you can review and apply these
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2809#issuecomment-59154436
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
GitHub user gasparms opened a pull request:
https://github.com/apache/spark/pull/2614
Typo error in KafkaWordCount example
topicpMap to topicMap
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gasparms/spark patch-1
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2614#issuecomment-57441727
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
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2614#issuecomment-57505879
Jenkins, this is ok to test.
---
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/2614#issuecomment-57505906
@gasparms Good catch!
---
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/2614#issuecomment-57506266
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/2614#issuecomment-57506597
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21135/consoleFull)
for PR 2614 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2614#issuecomment-57507258
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21137/consoleFull)
for PR 2614 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2614#issuecomment-57516882
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2614#issuecomment-57516873
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21135/consoleFull)
for PR 2614 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2614#issuecomment-57518372
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21137/consoleFull)
for PR 2614 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2614#issuecomment-57518381
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2614
---
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/1926#issuecomment-53368810
Thanks for the patch. You should open a JIRA issue on
https://issues.apache.org/jira/browse/SPARK for this and update the pull
request title to include its name, then we
Github user WangTaoTheTonic commented on the pull request:
https://github.com/apache/spark/pull/1926#issuecomment-53378027
All done. The issue is https://issues.apache.org/jira/browse/SPARK-3225.
Please check.
---
If your project is set up for it, you can reply to this email and
GitHub user WangTaoTheTonic opened a pull request:
https://github.com/apache/spark/pull/1926
Typo in script
use_conf_dir = user_conf_dir in load-spark-env.sh.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/WangTaoTheTonic/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1926#issuecomment-52075508
QA tests have started for PR 1926. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18444/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1926#issuecomment-52082467
QA results for PR 1926:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1495#issuecomment-49529878
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
GitHub user cesararevalo opened a pull request:
https://github.com/apache/spark/pull/1495
Typo fix to the programming guide in the docs
Typo fix to the programming guide in the docs. Changed the word
distibuted to distributed.
You can merge this pull request into a Git repository
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1495
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/927#issuecomment-44713343
Merged build triggered.
---
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 ash211 opened a pull request:
https://github.com/apache/spark/pull/927
Typo: and - an
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ash211/spark patch-5
Alternatively you can review and apply these changes as the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/927#issuecomment-44713349
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/927#issuecomment-44714464
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/927#issuecomment-44714465
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15310/
---
If your project
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/927#issuecomment-44718161
Thanks. Merged in master branch-1.0.
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/927
---
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 andrewor14 opened a pull request:
https://github.com/apache/spark/pull/847
[Typo] Stoped - Stopped
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewor14/spark yarn-typo
Alternatively you can review and apply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/847#issuecomment-43798932
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/847#issuecomment-43798958
Merged build started.
---
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/847#issuecomment-43799605
Thanks. I've merged this into master branch-1.0.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/847#issuecomment-43803493
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/847#issuecomment-43803495
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15123/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/680#issuecomment-42403127
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/680#issuecomment-42403117
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/680#issuecomment-42409172
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/780#issuecomment-43154166
Merged build triggered.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/680
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/780#issuecomment-43158275
Merged build finished. All automated tests passed.
---
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 andrewor14 opened a pull request:
https://github.com/apache/spark/pull/780
[Typo] propertes - properties
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewor14/spark submit-typo
Alternatively you can review and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/780#issuecomment-43154190
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/780#issuecomment-43158277
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14999/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/780
---
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/780#issuecomment-43158107
I've merged this. 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/680#issuecomment-42409177
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14768/
---
If your project
GitHub user ash211 opened a pull request:
https://github.com/apache/spark/pull/680
Typo fix: fetchting - fetching
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ash211/spark patch-3
Alternatively you can review and apply these
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/743#issuecomment-42875483
Merged build started.
---
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 ash211 opened a pull request:
https://github.com/apache/spark/pull/743
Typo: resond - respond
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ash211/spark patch-4
Alternatively you can review and apply these changes
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/743#issuecomment-42875468
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/743#issuecomment-42880113
Merged build finished. All automated tests passed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/743#issuecomment-42880115
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14903/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/743
---
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/743#issuecomment-42909069
Thanks. Merged.
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/680#issuecomment-42485074
Thanks. Merged.
---
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 andrewor14 opened a pull request:
https://github.com/apache/spark/pull/548
[Typo] In the maven docs: chd - cdh
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewor14/spark doc-typo
Alternatively you can review
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/548#issuecomment-41355909
Merged build triggered.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/548#issuecomment-41355914
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/548#issuecomment-41358104
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14475/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/548
---
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
90 matches
Mail list logo
