Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12442#issuecomment-212181313
@Sunshineit
- This PR seems does not change anything but is made by mistake.
- This PR does not describe anything so committers can see what the purpose
for
Github user jodersky commented on the pull request:
https://github.com/apache/spark/pull/12442#issuecomment-213320568
it looks like this was made by mistake. @Sunshineit, @srowen (or anyone
with the commit powers), could you please close this?
---
If your project is set up for it, yo
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12442
---
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 ena
GitHub user Sunshineit opened a pull request:
https://github.com/apache/spark/pull/12442
merge
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
## How was this patch tested?
(Please explain how this patc
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12442#issuecomment-210778679
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 p
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12442#issuecomment-210780787
@Sunshineit please close this PR
---
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 loachli opened a pull request:
https://github.com/apache/spark/pull/2173
merge updates
Support building spark under http proxy environment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/loachli/spark master
Alternati
Github user loachli closed the pull request at:
https://github.com/apache/spark/pull/2173
---
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 ena
GitHub user wangmiao1981 opened a pull request:
https://github.com/apache/spark/pull/11380
merge code
## What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
## How was this patch tested?
(Please explain how th
Github user wangmiao1981 closed the pull request at:
https://github.com/apache/spark/pull/11380
---
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 wangmiao1981 commented on the pull request:
https://github.com/apache/spark/pull/11380#issuecomment-189038485
Sorry for mistakenly sending it out. I want to merge Master code to my own
branch.
---
If your project is set up for it, you can reply to this email and have your
GitHub user chuckreporting opened a pull request:
https://github.com/apache/spark/pull/4366
merge from master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chuckreporting/spark master
Alternatively you can review and apply the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4366#issuecomment-72841232
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 pro
Github user chuckreporting closed the pull request at:
https://github.com/apache/spark/pull/4366
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39239988
+1 !!! I have been asking for this multiple times on the mailing list and
finally see the light!!!
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39240088
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/286#issuecomment-39240076
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39240275
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13636/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39240273
Merged build finished.
---
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39240317
But will this work on YARN?
---
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 pwendell opened a pull request:
https://github.com/apache/spark/pull/286
Merge Hadoop Into Spark
This patch merges the Hadoop 0.20.2 source code into the Spark project.
I've thought about this a bunch and this will provide us with several benefits:
### More sour
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39240734
The best way to have more lines than some project is to merge it!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39243472
I love hadoop-0.20.2 -- It is the best Hadoop I have ever used. Thanks
@pwendell for pulling this in.
---
If your project is set up for it, you can reply to this email a
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39251945
LGTM, merged !
On Wed, Apr 2, 2014 at 12:20 AM, Shivaram Venkataraman <
notificati...@github.com> wrote:
> I love hadoop-0.20.2 -- It is the best
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39253343
LGTMT
---
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 sryza commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39253647
I'm OK with holding off on this for a separate JIRA, but for completeness
I'd like to propose merging in CDH code as well. I believe that CDH4.2.2 would
be the best choice
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39253624
Great job!
---
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
ena
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39254250
Guys, I just realized that this includes a really cool submodule called
"Map Reduce" which seems to be a generalized form of Spark! It also has around
3x the amount of co
Github user mattf commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39260062
+1, lgtm, but only today!
---
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39270210
Wait, so did it pass or fail Jenkins tests? Jenkins isn't saying what
happened, only that the build finished.
Anyway I'd be okay with this as long as you make it me
Github user pwendell closed the pull request at:
https://github.com/apache/spark/pull/286
---
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 ena
Github user CrazyJvm commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39278059
+1 amazing! I've been looking forward it for a long time! thx!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user CrazyJvm commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39278167
amazing! I've been looking forward it for a long time!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user DavyLin commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39280455
I do not know, ah, but I'm looking forward to it
---
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 pr
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39280558
This is a good start! Why not merge all transitive dependencies into Spark
altogether? In this way we can save lots of efforts on SBT/Maven, and avoid
time consuming Ivy
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39281046
Yep, I find that each time I do `sbt clean gen-idea` or `sbt update` or
even `sbt testOnly xxx`, I can do the cooking, take a shower, and have a rest.
---
If your projec
Github user pelick commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39281241
Is it true about this => â Wait, hold on, is hadoop-0.20.2 the same as
hadoop-2.2.0? I'm assuming it's the same because they both have the same number
of "2"s. â
---
Github user win2cs commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39281738
"But will this work on YARN?", I've the same question.
And does it still support specifying other Hadoop distribution like before?
---
If your project is set up for it,
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/286#issuecomment-39284253
> You know, ever since those .orbit things were added, sbt update costs
nearly 40 minutes to resolve all the dependencies in mainland China... I have
to turn it off by ski
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/738
---
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 enabl
GitHub user ArcherShao opened a pull request:
https://github.com/apache/spark/pull/738
Merge addWithoutResize and rehashIfNeeded into one function.
It will be more safety to add an element, users do not need to the
function rehashIfNeeded() after addWithoutResize().
You can merge
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/738#issuecomment-42837187
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 proj
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/738#issuecomment-42910236
Thanks for submitting this - but considering this is a low level building
block collection and not meant to be used as a general collection library, and
the method's name its
GitHub user yiheng opened a pull request:
https://github.com/apache/spark/pull/6975
Merge from latest spark code
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yiheng/spark master
Alternatively you can review and apply these ch
Github user yiheng closed the pull request at:
https://github.com/apache/spark/pull/6975
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3879
---
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 enab
GitHub user jameszhouyi opened a pull request:
https://github.com/apache/spark/pull/4035
Merge pull request #1 from apache/master
[SPARK-2140] Updating heap memory calculation for YARN stable and alpha.
You can merge this pull request into a Git repository by running:
$ git pul
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4035#issuecomment-69875249
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 pro
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/4035#issuecomment-69875321
Do you mind closing this PR? It looks like it was opened accidentally.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
GitHub user yuyongyang800 opened a pull request:
https://github.com/apache/spark/pull/4071
Merge pull request #1 from apache/master
Update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yuyongyang800/spark master
Alternatively y
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4071#issuecomment-70265345
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 pro
Github user yuyongyang800 closed the pull request at:
https://github.com/apache/spark/pull/4071
---
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/4035
---
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 enab
Github user jameszhouyi commented on the pull request:
https://github.com/apache/spark/pull/4035#issuecomment-70643624
Sorry for opened accidentally..please kindly close it. 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/2502
---
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 enab
GitHub user judynash opened a pull request:
https://github.com/apache/spark/pull/2827
Merge pull request #1 from apache/master
Merge with latest spark enlistment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dwann/spark master
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2827#issuecomment-59395697
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 pro
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/2827#issuecomment-59397923
Hi @judynash, there's nothing in this PR, do you mind closing it? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user judynash closed the pull request at:
https://github.com/apache/spark/pull/2827
---
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 en
Github user judynash commented on the pull request:
https://github.com/apache/spark/pull/2827#issuecomment-59398090
Sorry â still learning Github and sent the request out unintentionally.
From: Marcelo Vanzin [mailto:notificati...@github.com]
Sent: Thursday, October 16, 2
GitHub user ceys opened a pull request:
https://github.com/apache/spark/pull/2502
Merge pull request #1 from apache/master
Update from original
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ceys/spark master
Alternatively you c
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2502#issuecomment-56471527
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 d
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/2502#issuecomment-56484239
Hi @ceys. What is the purpose of this PR? It looks like it was perhaps a
mistake?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2502#issuecomment-56584364
close this issue.
---
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 feat
GitHub user javadba opened a pull request:
https://github.com/apache/spark/pull/1954
Merge pull request #1 from apache/master
Syncing to upstream
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/javadba/spark master
Alternatively
Github user javadba closed the pull request at:
https://github.com/apache/spark/pull/1954
---
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 ena
GitHub user javadba opened a pull request:
https://github.com/apache/spark/pull/1955
Merge pull request #1 from apache/master
Syncing to upstream
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/javadba/spark master
Alternatively
Github user javadba closed the pull request at:
https://github.com/apache/spark/pull/1955
---
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 ena
GitHub user javadba reopened a pull request:
https://github.com/apache/spark/pull/1955
Merge pull request #1 from apache/master
Syncing to upstream
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/javadba/spark master
Alternativel
Github user javadba closed the pull request at:
https://github.com/apache/spark/pull/1955
---
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 ena
GitHub user yzhou2001 opened a pull request:
https://github.com/apache/spark/pull/1957
Merge pull request #1 from apache/master
A merge of latest changes since creation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Huawei-Spark/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1957#issuecomment-52260978
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 pro
Github user yzhou2001 closed the pull request at:
https://github.com/apache/spark/pull/1957
---
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 e
GitHub user SpyderRiverA opened a pull request:
https://github.com/apache/spark/pull/2040
Merge pull request #1 from apache/master
updating my fork
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SpyderRiverA/spark master
Alterna
Github user SpyderRiverA closed the pull request at:
https://github.com/apache/spark/pull/2040
---
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 i
GitHub user pengyanhong opened a pull request:
https://github.com/apache/spark/pull/3015
Merge pull request #1 from apache/master
update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pengyanhong/spark master
Alternatively you c
Github user pengyanhong closed the pull request at:
https://github.com/apache/spark/pull/3015
---
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 pengyanhong opened a pull request:
https://github.com/apache/spark/pull/3016
Merge pull request #1 from apache/master
update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pengyanhong/spark master
Alternatively you c
Github user pengyanhong commented on the pull request:
https://github.com/apache/spark/pull/3016#issuecomment-61106373
update
---
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
enab
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3016#issuecomment-61106591
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 pro
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/3016#issuecomment-61107082
I think you opened this accidentally. Can you close it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/3016#issuecomment-61146550
Hey @pengyanhong mind closing this issue?
---
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 proje
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/3016
---
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 enab
GitHub user codeAshu opened a pull request:
https://github.com/apache/spark/pull/3384
Merge pull request #1 from apache/master
updating Fork
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/codeAshu/spark master
Alternatively you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3384#issuecomment-63815959
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 pro
Github user codeAshu closed the pull request at:
https://github.com/apache/spark/pull/3384
---
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 en
Github user codeAshu commented on the pull request:
https://github.com/apache/spark/pull/3384#issuecomment-63816089
sorry my bad
---
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
e
GitHub user hxfeng opened a pull request:
https://github.com/apache/spark/pull/3879
Merge pull request #1 from apache/master
update
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hxfeng/spark master
Alternatively you can review
Github user hxfeng commented on the pull request:
https://github.com/apache/spark/pull/3879#issuecomment-68526458
update
---
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 a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3879#issuecomment-68526639
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 pro
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/3879#issuecomment-68549708
Hi @hxfeng did you mean to send this in? I don't see any code change, just
an empty merge commit. Would you mind closing this pull request if it was sent
accidentally?
GitHub user Jianfeng-chs opened a pull request:
https://github.com/apache/spark/pull/8576
Merge pull request #1 from apache/master
Syn apache spark
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Jianfeng-chs/spark master
Alterna
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8576#issuecomment-137153154
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 pr
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/8576#issuecomment-137164005
Do you mind closing this 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. If your project doe
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8576#issuecomment-137271147
@Jianfeng-chs looks like this is opened by mistake. Please close this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8576
---
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 enab
GitHub user jiangxb1987 opened a pull request:
https://github.com/apache/spark/pull/8654
Merge pull request #1 from apache/master
merge origin pr
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jiangxb1987/spark master
Alternativ
Github user jiangxb1987 closed the pull request at:
https://github.com/apache/spark/pull/8654
---
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 jiangxb1987 reopened a pull request:
https://github.com/apache/spark/pull/8654
Merge pull request #1 from apache/master
merge origin pr
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jiangxb1987/spark master
Alternat
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8654#issuecomment-138606793
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 pr
1 - 100 of 184 matches
Mail list logo
