Github user nakul02 commented on the pull request:
https://github.com/apache/spark/pull/9756#issuecomment-159032729
@Lewuathe, could you please take a look at this?
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8610#issuecomment-159041605
The 1.6 preview is already cut. This will have to come later. Until then,
it would be good for @tnachen and @dragos to have a look.
---
If your project is set up
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9914#issuecomment-159041866
Is it easy to fix this issue in 1.5?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9914#issuecomment-159042903
**[Test build #46545 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46545/consoleFull)**
for PR 9914 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9905#issuecomment-159043800
LGTM too. Merging with master and branch-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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9913#issuecomment-159033836
**[Test build #46543 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46543/consoleFull)**
for PR 9913 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9613#issuecomment-159035448
**[Test build #46544 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46544/consoleFull)**
for PR 9613 at commit
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/8610#issuecomment-159035418
Hi, @dragos , thanks for the comments, just sync the patch with master and
addressed your comments
@andrewor14 any plan to fix this in the coming 1.6?
---
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/9816#discussion_r45647600
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -119,30 +119,31 @@ trait Logging {
val usingLog4j12 =
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/9914
[SPARK-11836] udf/cast should not create new SQLContext
They should use the existing SQLContext.
You can merge this pull request into a Git repository by running:
$ git pull
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9427#discussion_r45650551
--- Diff: core/src/main/scala/org/apache/spark/scheduler/Task.scala ---
@@ -89,9 +89,15 @@ private[spark] abstract class Task[T](
} finally {
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9914#issuecomment-159043738
@yhuai I could send another patch for 1.5
---
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 jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9338#issuecomment-159044776
@yu-iskw Could you please fix the conflicts?
@noel-smith Will you be able to review this? If not, let me know, and I'll
review it.
Thanks!
---
If
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/9895#discussion_r45651751
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveContext.scala ---
@@ -535,6 +535,14 @@ class HiveContext private[hive](
).map { case
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9905
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/9914#issuecomment-159045248
Thanks. That will be great!
---
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/9912#issuecomment-159015907
**[Test build #46540 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46540/consoleFull)**
for PR 9912 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9904#discussion_r45638276
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/objects.scala
---
@@ -531,15 +526,15 @@ case class
Github user ajbozarth commented on the pull request:
https://github.com/apache/spark/pull/9874#issuecomment-159019026
@srowen, yes it put them in reverse order for some reason.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9800#issuecomment-159023601
Merging 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9898
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/9747#issuecomment-159024652
Merging 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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9904#issuecomment-159016363
Thanks, merging to master and 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
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/8610#issuecomment-159016285
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9904
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9906#issuecomment-159016667
Thanks, merging to master and 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9906
---
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/6757#issuecomment-159018402
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9861#issuecomment-159019288
**[Test build #46538 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46538/consoleFull)**
for PR 9861 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9861#issuecomment-159019627
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9861#issuecomment-159019623
Merged build finished. Test PASSed.
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159021372
@zsxwing true. Fixed.
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159022902
LGTM pending tests.
---
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/9859#issuecomment-159023025
So, is there any code in any of the other backends to actually use those
config options?
Looking at the bug, isn't the fix actually achieved by just doing the
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9898#issuecomment-159023270
Thanks, merging to master and 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9853#issuecomment-159023678
**[Test build #46541 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46541/consoleFull)**
for PR 9853 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9800
---
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 davies opened a pull request:
https://github.com/apache/spark/pull/9915
[SPARK-11836] [SQL] use existing SQLContext for udf/cast
udf/cast should use existing SQLContext.
You can merge this pull request into a Git repository by running:
$ git pull
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/9797#issuecomment-159047468
LGTM, so I'm going to merge this into master and branch-1.6.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9797
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/8359#issuecomment-159048986
Do you mind closing this PR for now in order to de-clutter the queue?
Thanks!
---
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/9914#issuecomment-159050037
**[Test build #46545 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46545/consoleFull)**
for PR 9914 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9914#issuecomment-159050415
Merged build finished. Test PASSed.
---
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/9914#issuecomment-159050419
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user ehsanmok closed the pull request at:
https://github.com/apache/spark/pull/9817
---
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 ehsanmok reopened a pull request:
https://github.com/apache/spark/pull/9817
[SPARK-11826][MLlib] subtract method for BlockMatrix
@mengxr Could you please check this when you have time?
You can merge this pull request into a Git repository by running:
$ git pull
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9915#issuecomment-159051715
[Test build #46546 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46546/consoleFull)
for PR 9915 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/9886#issuecomment-159051811
+1 on having a fall back with a warning message as well.
---
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 ehsanmok closed the pull request at:
https://github.com/apache/spark/pull/9817
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9613#issuecomment-159051454
**[Test build #46548 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46548/consoleFull)**
for PR 9613 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9793#issuecomment-159051902
**[Test build #46547 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46547/consoleFull)**
for PR 9793 at commit
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9608#discussion_r45654941
--- Diff: core/src/main/scala/org/apache/spark/HttpFileServer.scala ---
@@ -42,10 +42,11 @@ private[spark] class HttpFileServer(
fileDir.mkdir()
Github user woj-i commented on the pull request:
https://github.com/apache/spark/pull/9859#issuecomment-159052976
No It's not enough. Please look at the code of the method
UserGroupInformation.loginUserFromKeytab(args.principal, args.keytab). There is
a check of authentication type.
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9859#issuecomment-159053620
I know that, but that's not what I'm asking about. I'm asking about all the
other code; why do you need to set `spark.yarn.keytab` for other backends?
I also
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/8610#issuecomment-159053651
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 CodingCat commented on the pull request:
https://github.com/apache/spark/pull/8610#issuecomment-159053442
OK, thx
One more question, am I supposed to have the permission to trigger Jenkins
to retest the patch, I thought I was once able to do that...or it is due
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8610#issuecomment-159054509
**[Test build #46549 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46549/consoleFull)**
for PR 8610 at commit
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/8610#issuecomment-159054566
nvm, the bot fixed the relationship with me .
---
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 tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8610#discussion_r45656480
--- Diff: core/src/main/scala/org/apache/spark/deploy/master/Master.scala
---
@@ -639,10 +640,11 @@ private[deploy] class Master(
// in the queue,
Github user woj-i commented on the pull request:
https://github.com/apache/spark/pull/9859#issuecomment-159057200
Let's see the situation when I wrap the context of SparkContext with my UGI
and even wrap the HiveContext with my UGI then most of Spark functions work
with my provided
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9613#issuecomment-159057568
Merged build finished. Test PASSed.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9613#issuecomment-159057394
**[Test build #46548 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46548/consoleFull)**
for PR 9613 at commit
GitHub user ehsanmok opened a pull request:
https://github.com/apache/spark/pull/9916
[SPARK-11826][MLlib] Reimplement add() and subtract() methods
@srowen Could you please check this when you have time?
You can merge this pull request into a Git repository by running:
$ git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9915#issuecomment-159057723
[Test build #46546 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46546/console)
for PR 9915 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9613#issuecomment-159057569
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9915#issuecomment-159057863
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9915#issuecomment-159057861
Merged build finished. Test PASSed.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-158882752
**[Test build #46516 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46516/consoleFull)**
for PR 8714 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-158882813
Merged build finished. Test FAILed.
---
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/9905#issuecomment-158882535
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9896#issuecomment-158882773
**[Test build #2097 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2097/consoleFull)**
for PR 9896 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-158882815
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9901#issuecomment-158882753
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9843#discussion_r45582811
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/feature/IDF.scala ---
@@ -218,7 +218,7 @@ private object IDFModel {
newValues(k) =
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9886#issuecomment-158883916
@toddwan what do you think about writing a separate code path to handle the
incorrect `zk://...` syntax? It could use the same "case", if it's a regex that
captures the
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/9906
[SPARK-11921][SQL] fix `nullable` of encoder schema
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloud-fan/spark nullable
Alternatively
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/9902#issuecomment-158887372
The failure results from old TRIM would trim characters whose ascii is in
[0, 20], but actually we should only trim ' '. This is to stay consistent with
Hive 1.2.1.
Github user liyezhang556520 commented on a diff in the pull request:
https://github.com/apache/spark/pull/7753#discussion_r45584487
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/EventLoggingListener.scala ---
@@ -20,8 +20,10 @@ package org.apache.spark.scheduler
Github user liyezhang556520 commented on a diff in the pull request:
https://github.com/apache/spark/pull/7753#discussion_r45584427
--- Diff:
core/src/main/scala/org/apache/spark/network/netty/NettyBlockTransferService.scala
---
@@ -47,6 +50,39 @@ class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9905#issuecomment-158889297
Merged build finished. Test PASSed.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9905#issuecomment-158889155
**[Test build #46519 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46519/consoleFull)**
for PR 9905 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-158889188
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9904#issuecomment-158889177
Merged build finished. Test PASSed.
---
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/9905#issuecomment-158889299
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/9904#issuecomment-158889348
cc @marmbrus
---
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/8714#issuecomment-158889187
Merged build finished. Test PASSed.
---
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/9904#issuecomment-158889178
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user liyezhang556520 commented on a diff in the pull request:
https://github.com/apache/spark/pull/7753#discussion_r45585344
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/EventLoggingListener.scala ---
@@ -228,6 +260,40 @@ private[spark] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9908#issuecomment-158910484
Merged build finished. Test PASSed.
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158900367
**[Test build #46518 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46518/consoleFull)**
for PR 9883 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9883#issuecomment-158900494
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9709#issuecomment-158903703
Merged build finished. Test PASSed.
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/9900#issuecomment-158903633
Looks like it is because I modified InternalRow's hashCode for string in
#9883. Close it now.
---
If your project is set up for it, you can reply to this email and have
Github user viirya closed the pull request at:
https://github.com/apache/spark/pull/9900
---
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/9709#issuecomment-158903706
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/9709#issuecomment-158903588
**[Test build #46526 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46526/consoleFull)**
for PR 9709 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9907#issuecomment-158904200
**[Test build #46525 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46525/consoleFull)**
for PR 9907 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9907#issuecomment-158904324
Merged build finished. Test PASSed.
---
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/9907#issuecomment-158904325
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/9709#issuecomment-158905191
**[Test build #46528 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46528/consoleFull)**
for PR 9709 at commit
1 - 100 of 556 matches
Mail list logo
