Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214269773
Jenkins, retest it 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 srowen commented on the pull request:
https://github.com/apache/spark/pull/11128#issuecomment-214267644
What's the resolution here -- just leave these as-is?
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/12416#issuecomment-214266854
@pravingadakh sorry this needs a rebase now
---
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/12631#issuecomment-214262421
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/12631#issuecomment-214262423
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/12646#issuecomment-214262362
**[Test build #2867 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2867/consoleFull)**
for PR 12646 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12631#issuecomment-214262228
**[Test build #56890 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56890/consoleFull)**
for PR 12631 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12590#issuecomment-214254061
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/12590#issuecomment-214254054
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/12590#issuecomment-214253156
**[Test build #56891 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56891/consoleFull)**
for PR 12590 at commit
Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/11152#issuecomment-214245234
thanks for reviewing this,
Steve
---
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/12493#issuecomment-214241525
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214241528
Test FAILed.
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/12493#issuecomment-214241002
**[Test build #56889 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56889/consoleFull)**
for PR 12493 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12590#issuecomment-214219497
**[Test build #56891 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56891/consoleFull)**
for PR 12590 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12631#issuecomment-214218617
Thank you, @srowen !
---
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 dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12590#issuecomment-214217838
Rebased.
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/12631#issuecomment-214217296
Yeah that looks good to 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 your project does not
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12631#issuecomment-214216304
Hi, @srowen .
Now, it's ready for review again.
I think I've addressed all your comments. The last one was about `awk`
command that you recommended.
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/12653#issuecomment-214213790
Ok, that settles is it then. @aa8y could you close this? Thanks for
working on it though.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12631#issuecomment-214213800
**[Test build #56890 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56890/consoleFull)**
for PR 12631 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12646#issuecomment-214213556
**[Test build #2867 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2867/consoleFull)**
for PR 12646 at commit
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/11635#issuecomment-214213408
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12659#issuecomment-214211764
**[Test build #56888 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56888/consoleFull)**
for PR 12659 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12659#issuecomment-214211949
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12659#issuecomment-214211952
Test FAILed.
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/12395
---
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/12395#issuecomment-214211070
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 njwhite commented on the pull request:
https://github.com/apache/spark/pull/12620#issuecomment-214210492
@davies I'm using this to use the "dill" serializer, as it can pickle more
things (and allows more fine-grained control) than the cloud-pickle serializer.
What about
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12421#issuecomment-214207072
Hi, @hvanhovell .
Now, it's ready for review again.
Thank you so much. I couldn't fix this without your help.
---
If your project is set up for it, you
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12530
---
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/12530#issuecomment-214205590
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 sun-rui commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214201014
@shivaram, rebased 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12493#issuecomment-214200933
**[Test build #56889 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56889/consoleFull)**
for PR 12493 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12421#issuecomment-214198931
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/12421#issuecomment-214198934
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/12421#issuecomment-214198651
**[Test build #56885 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56885/consoleFull)**
for PR 12421 at commit
Github user MLnick commented on a diff in the pull request:
https://github.com/apache/spark/pull/12609#discussion_r60874354
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/clustering/KMeansSuite.scala ---
@@ -117,6 +126,24 @@ class KMeansSuite extends SparkFunSuite with
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10896#issuecomment-214186713
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/10896#issuecomment-214186715
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/10896#issuecomment-214186535
**[Test build #56884 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56884/consoleFull)**
for PR 10896 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12659#issuecomment-214185700
**[Test build #56888 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56888/consoleFull)**
for PR 12659 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12555
---
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/12659#issuecomment-214183743
**[Test build #56887 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56887/consoleFull)**
for PR 12659 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12555#issuecomment-214183674
I just ran into this issue again (pull requests failing style test). I'm
going to merge this. Let's see how it goes ... we can always disable it if it
ends up too
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12659#issuecomment-214183751
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/12659#issuecomment-214183748
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12659#issuecomment-214183540
**[Test build #56887 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56887/consoleFull)**
for PR 12659 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12653#issuecomment-214179104
No, I know these break 2.10. That's why they haven't been zapped yet.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12659#issuecomment-214179039
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/12659#issuecomment-214179037
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12659#issuecomment-214179032
**[Test build #56886 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56886/consoleFull)**
for PR 12659 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12659#issuecomment-214178591
**[Test build #56886 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56886/consoleFull)**
for PR 12659 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12641#issuecomment-21412
**[Test build #2866 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2866/consoleFull)**
for PR 12641 at commit
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/12659
[SPARK-14888][SQL] UnresolvedFunction should use FunctionIdentifier rather
than just a string for function name
## What changes were proposed in this pull request?
This patch changes
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/12358#issuecomment-214176468
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
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/11997#issuecomment-214164387
Close this for now, and if needed, I'll reopen 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
Github user maropu closed the pull request at:
https://github.com/apache/spark/pull/11997
---
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/12421#issuecomment-214164024
**[Test build #56885 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56885/consoleFull)**
for PR 12421 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-214163999
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/12618#issuecomment-214164002
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-214163952
@markhamstra Thank you for your comment.
I thought the non-optimal state in `DAGScheduler` was a kind of bug so I
used the words "incorrect" or "illegal" but now I
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-214163860
**[Test build #56880 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56880/consoleFull)**
for PR 12618 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12421#issuecomment-214163478
The failures are `MemorySinkSuite`. It seems to be irrelevant to this PR.
I'll rebase to retrigger Jenkins.
```
[info] *** 2 TESTS FAILED ***
[error]
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12204#issuecomment-214160150
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/12204#issuecomment-214160145
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/12204#issuecomment-214159730
**[Test build #56879 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56879/consoleFull)**
for PR 12204 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12202#issuecomment-214159433
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12421#issuecomment-214156284
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 rishabhbhardwaj reopened a pull request:
https://github.com/apache/spark/pull/12202
[SPARK-14412][ML][WIP]spark.ml ALS prefered storage level Params
## What changes were proposed in this pull request?
Added storage level params in ALSParams.
## How was this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12421#issuecomment-214156288
Test FAILed.
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/12421#issuecomment-214156199
**[Test build #56881 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56881/consoleFull)**
for PR 12421 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10896#issuecomment-214155733
**[Test build #56884 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56884/consoleFull)**
for PR 10896 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12652#issuecomment-214155439
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/12652#issuecomment-214155437
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/12652#issuecomment-214155262
**[Test build #56877 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56877/consoleFull)**
for PR 12652 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12081#discussion_r60866200
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
---
@@ -650,7 +655,12 @@ class SessionCatalog(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10896#issuecomment-214152854
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/10896#issuecomment-214152849
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10896#issuecomment-214152843
**[Test build #56883 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56883/consoleFull)**
for PR 10896 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-214152067
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/10896#issuecomment-214152193
**[Test build #56883 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56883/consoleFull)**
for PR 10896 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-214152071
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user sun-rui closed the pull request at:
https://github.com/apache/spark/pull/12090
---
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 boy-uber commented on the pull request:
https://github.com/apache/spark/pull/2633#issuecomment-214151289
Now Spark has improved a lot in fault-tolerance, robustness, and stability.
Could we revisit this PR?
There is a lot of value supporting event timestamp, since
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-214151363
**[Test build #56873 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56873/consoleFull)**
for PR 12655 at commit
701 - 786 of 786 matches
Mail list logo
