Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11030#issuecomment-180020843
**[Test build #50763 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50763/consoleFull)**
for PR 11030 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11080#issuecomment-180029353
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/11080#issuecomment-180029356
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/10959#issuecomment-180030313
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user drcrallen commented on the pull request:
https://github.com/apache/spark/pull/10232#issuecomment-180034849
local fork of spark at https://github.com/metamx/spark/tree/v1.5.2-mmx is
using this successfully, but since #10993 will probably be the way to go
forward, I'm not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11081#issuecomment-180035696
**[Test build #50762 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50762/consoleFull)**
for PR 11081 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11081#issuecomment-180036190
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/11081#issuecomment-180036195
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user YuvalItzchakov commented on the pull request:
https://github.com/apache/spark/pull/11081#issuecomment-180038981
Thank you guys for the quick fix. Will the updated binary be available via
the spark download page or will I need to compile from source?
---
If your project
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10959#issuecomment-180039465
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10959#issuecomment-180039515
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11081#issuecomment-180041103
> Thank you guys for the quick fix. Will the updated binary be available
via the spark download page or will I need to compile from source?
You need to compile
Github user YuvalItzchakov commented on the pull request:
https://github.com/apache/spark/pull/11081#issuecomment-180041624
Yes, that's how I've worked around it in the meanwhile. Thx @zsxwing
---
If your project is set up for it, you can reply to this email and have your
reply
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11081#issuecomment-180041252
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 not have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11081
---
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/11030#issuecomment-180042037
**[Test build #50767 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50767/consoleFull)**
for PR 11030 at commit
Github user mgummelt commented on a diff in the pull request:
https://github.com/apache/spark/pull/10993#discussion_r51934657
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/CoarseMesosSchedulerBackend.scala
---
@@ -245,99 +239,182 @@ private[spark] class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10993#issuecomment-180043255
**[Test build #50769 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50769/consoleFull)**
for PR 10993 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10959#issuecomment-180043428
**[Test build #50759 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50759/consoleFull)**
for PR 10959 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10959#issuecomment-180044262
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/10959#issuecomment-180044254
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/10993#issuecomment-180045237
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/10993#issuecomment-180045220
**[Test build #50769 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50769/consoleFull)**
for PR 10993 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10993#issuecomment-180045231
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 RaafatAkkad commented on the pull request:
https://github.com/apache/spark/pull/10959#issuecomment-180045975
Thanks for the feedback. The tests have passed. Can you please re-trigger a
CI build for the "Make waitingApps private" commit as it has failed?
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10959#issuecomment-180047054
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/11010#issuecomment-179700147
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/7334#issuecomment-179700823
**[Test build #2514 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2514/consoleFull)**
for PR 7334 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11016#issuecomment-179706183
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/11016#issuecomment-179706186
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user carsonwang opened a pull request:
https://github.com/apache/spark/pull/11071
[SPARK-13185][SQL] Improve the performance of DateTimeUtils by reusing
TimeZone and Calendar objects
It is expensive to create java TimeZone and Calendar objects in each method
of
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11072#issuecomment-179708786
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 feature
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/11072
[SPARK-13187][SQL] Add boolean/long/double options in DataFrameReader/Writer
This patch adds option function for boolean, long, and double types. This
makes it slightly easier for Spark users to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11071#issuecomment-179711566
**[Test build #50744 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50744/consoleFull)**
for PR 11071 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11071#issuecomment-179711573
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/11010#issuecomment-179700144
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/8610#issuecomment-179700546
**[Test build #50743 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50743/consoleFull)**
for PR 8610 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/7334#discussion_r51839591
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/QueryExecution.scala ---
@@ -44,7 +44,7 @@ class QueryExecution(val sqlContext: SQLContext, val
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11064#issuecomment-179700454
**[Test build #2515 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2515/consoleFull)**
for PR 11064 at commit
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/11067#issuecomment-179700506
cc @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 have this feature
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11016#issuecomment-179705864
**[Test build #50739 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50739/consoleFull)**
for PR 11016 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11071#issuecomment-179711327
**[Test build #50744 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50744/consoleFull)**
for PR 11071 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11071#issuecomment-179711574
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/11016#issuecomment-179712429
**[Test build #50741 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50741/consoleFull)**
for PR 11016 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11016#issuecomment-179712755
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/11016#issuecomment-179712757
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/11071#issuecomment-179713645
**[Test build #50746 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50746/consoleFull)**
for PR 11071 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11060#issuecomment-179714901
**[Test build #2512 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2512/consoleFull)**
for PR 11060 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11072#issuecomment-179715859
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/11072#issuecomment-179715856
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
501 - 550 of 550 matches
Mail list logo
