Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3691#issuecomment-66905844
LGTM; 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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/3691
---
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/3691#issuecomment-66905888
Merged into master and all of the maintenance branches.
---
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 tigerquoll commented on the pull request:
https://github.com/apache/spark/pull/2516#issuecomment-66909268
No probs, it was actually a nice way of starting to poke through the code
to figure out how things are put together. I'll stick to smaller jobs from now
on in.
Github user aniketbhatnagar closed the pull request at:
https://github.com/apache/spark/pull/3092
---
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
Github user aniketbhatnagar commented on the pull request:
https://github.com/apache/spark/pull/3092#issuecomment-66912820
Tested and Chris's suggestion to use EC2 profiles works.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3395#issuecomment-66915681
LGTM, 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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/3672#issuecomment-66916125
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3672#issuecomment-66916267
[Test build #24440 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24440/consoleFull)
for PR 3672 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3672#issuecomment-66919317
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/3672#issuecomment-66919314
[Test build #24440 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24440/consoleFull)
for PR 3672 at commit
Github user petervandenabeele commented on the pull request:
https://github.com/apache/spark/pull/3517#issuecomment-66922392
Bump ...
I suggest we revert to something close to my original proposal:
* no change in filenames (too complex for now)
* add a small(er) note
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/3517#issuecomment-66924151
Sure, I'm happy with clarifications to the documentation.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/3688#issuecomment-66925510
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3688#issuecomment-66925608
[Test build #24441 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24441/consoleFull)
for PR 3688 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/3660#issuecomment-66926121
This is a good catch, but perhaps the real bug here is that we are
overriding the `sqlContext` in `InMemoryTableScan`. Instead, what do you think
about just removing
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3688#issuecomment-66928132
[Test build #24441 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24441/consoleFull)
for PR 3688 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3688#issuecomment-66928133
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/3690#issuecomment-66928843
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 have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3690#issuecomment-66928921
[Test build #24442 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24442/consoleFull)
for PR 3690 at commit
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/3692
SPARK-4814 [CORE] Enable assertions in SBT, Maven tests / AssertionError
from Hive's LazyBinaryInteger
This enables assertions for the Maven and SBT build, but overrides the Hive
module to not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3692#issuecomment-66930746
[Test build #24443 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24443/consoleFull)
for PR 3692 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3690#issuecomment-66931556
[Test build #24442 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24442/consoleFull)
for PR 3690 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3690#issuecomment-66931560
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/3672#issuecomment-66933007
[Test build #2 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/2/consoleFull)
for PR 3672 at commit
GitHub user ganonp opened a pull request:
https://github.com/apache/spark/pull/3693
Added setMinCount to Word2Vec.scala
Wanted to customize the private minCount variable in the Word2Vec class.
Added
a method to do so.
You can merge this pull request into a Git repository by
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3693#issuecomment-66934430
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/3692#issuecomment-66934745
[Test build #24443 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24443/consoleFull)
for PR 3692 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3692#issuecomment-66934748
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/3672#issuecomment-66936450
[Test build #2 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/2/consoleFull)
for PR 3672 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3672#issuecomment-66936452
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/3686#issuecomment-66937888
@tgravescs In all other places we've managed to avoid referring to the
yarn-client AM as the driver and I think blurring this distinction would be
pretty confusing.
GitHub user scwf opened a pull request:
https://github.com/apache/spark/pull/3694
[Core] Adding a parallelismRatio to control the partitions num of
shuffledRDD
Adding parallelismRatio to control the partitions num of shuffledRDD, the
rule is:
Math.max(1,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3694#issuecomment-66940757
[Test build #24445 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24445/consoleFull)
for PR 3694 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/3660#issuecomment-66941524
I heard from @liancheng about some plan of using two SchemaRDDs from
different sqlContext. Is the override sqlContext designed to support it?
@liancheng since you added
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3694#issuecomment-66943835
[Test build #24445 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24445/consoleFull)
for PR 3694 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3694#issuecomment-66943841
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3672#issuecomment-66944216
The most recent test failures should be caused by other components. Let's
wait for a moment. This PR now LGTM.
---
If your project is set up for it, you can reply to
GitHub user harishreedharan opened a pull request:
https://github.com/apache/spark/pull/3695
[SPARK-4826][Streaming] - Create unique file names for each test in WALS...
...uite to avoid conflicts.
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/3695#issuecomment-66946543
[Test build #24446 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24446/consoleFull)
for PR 3695 at commit
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/3695#issuecomment-66946690
@tdas @JoshRosen Since the directories are created atomically each time the
suite is run, conflicts reported in SPARK-4826 was likely caused by multiple
tests
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3695#issuecomment-66946766
[Test build #24447 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24447/consoleFull)
for PR 3695 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3695#issuecomment-66946801
[Test build #24447 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24447/consoleFull)
for PR 3695 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3695#issuecomment-66946803
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/3695#issuecomment-66947024
[Test build #24448 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24448/consoleFull)
for PR 3695 at commit
GitHub user ksakellis opened a pull request:
https://github.com/apache/spark/pull/3696
SPARK-4843 [YARN] Squash ExecutorRunnableUtil and ExecutorRunnable
ExecutorRunnableUtil is a parent of ExecutorRunnable because of the
yarn-alpha and yarn-stable split. Now that yarn-alpha is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3696#issuecomment-66949811
[Test build #24449 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24449/consoleFull)
for PR 3696 at commit
Github user judynash commented on the pull request:
https://github.com/apache/spark/pull/3672#issuecomment-66950036
Thank you Cheng for the update.
From: Cheng Lian [mailto:notificati...@github.com]
Sent: Sunday, December 14, 2014 6:57 PM
To: apache/spark
Cc: Judy
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3695#issuecomment-66950408
[Test build #24446 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24446/consoleFull)
for PR 3695 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3695#issuecomment-66950410
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/3695#issuecomment-66950933
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/3695#issuecomment-66950931
[Test build #24448 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24448/consoleFull)
for PR 3695 at commit
GitHub user jinntrance opened a pull request:
https://github.com/apache/spark/pull/3697
[MLLIB]SPARK-4846: When the vocabulary size is large, Word2Vec may yield OOM
make variables syn0Global and syn1Global lazy, in order that the high-order
function passed to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3697#issuecomment-66952147
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 scwf commented on the pull request:
https://github.com/apache/spark/pull/3694#issuecomment-66952763
Jekins, 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3696#issuecomment-66952800
[Test build #24449 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24449/consoleFull)
for PR 3696 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3696#issuecomment-66952805
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/3694#issuecomment-66952871
[Test build #24450 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24450/consoleFull)
for PR 3694 at commit
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3660#issuecomment-66954133
@zsxwing I guess what you mentioned is the plan to support multiple data
sources via the newly introduced external data source API? The commit you
mentioned is
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/3660#issuecomment-66954374
I guess what you mentioned is the plan to support multiple data sources
via the newly introduced external data source API?
Yes.
In that commit I just
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3660#issuecomment-66955023
Ah I see you point, so here we referenced a field overriden by subclass in
the constructor of the parent class. Then I think it's generally not safe to
allow
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/3660#issuecomment-66955060
Yes, we should remove 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 project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3660#issuecomment-66955512
[Test build #24451 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24451/consoleFull)
for PR 3660 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/3660#issuecomment-66955549
Done. Also updated the description of this PR and JIRA.
---
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 jerryshao opened a pull request:
https://github.com/apache/spark/pull/3698
[SPARK-4847][SQL]Fix extraStrategies cannot take effect in SQLContext
issue
You can merge this pull request into a Git repository by running:
$ git pull
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/3694#issuecomment-66956061
Hmm, seems there are some problems with
```org.apache.spark.streaming.rdd.WriteAheadLogBackedBlockRDDSuite```, and i
noticed that other PRs also failed there.
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3694#issuecomment-66956286
[Test build #24450 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24450/consoleFull)
for PR 3694 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3694#issuecomment-66956294
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/3698#issuecomment-66956337
[Test build #24452 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24452/consoleFull)
for PR 3698 at commit
GitHub user nkronenfeld opened a pull request:
https://github.com/apache/spark/pull/3699
[SPARK-4848] Stand-alone cluster: Allow differences between workers with
multiple instances
I've changed the stand-alone cluster run scripts to allow different workers
to have different
Github user nkronenfeld commented on the pull request:
https://github.com/apache/spark/pull/3699#issuecomment-66957137
I'm not sure how mesos and yarn clusters are started/stopped (nor do I have
such clusters on which to test), so I'm not sure how this will affect them. I
think the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/3699#issuecomment-66957276
[Test build #24453 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24453/consoleFull)
for PR 3699 at commit
Github user ksakellis commented on the pull request:
https://github.com/apache/spark/pull/3696#issuecomment-66958311
Hmm.. tests failed but I'm not sure they are related to this change. Am I
missing something?
---
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/3660#issuecomment-66959907
[Test build #24451 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24451/consoleFull)
for PR 3660 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/3660#issuecomment-66959913
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
75 matches
Mail list logo
