Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5974#issuecomment-100114302
[Test build #32201 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32201/consoleFull)
for PR 5974 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5974#issuecomment-100114335
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/5974#issuecomment-100127815
[Test build #32212 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32212/consoleFull)
for PR 5974 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5999#issuecomment-100127748
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5999#issuecomment-100127804
[Test build #32211 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32211/consoleFull)
for PR 5999 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5974#issuecomment-100127741
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5974#issuecomment-100127754
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5999#issuecomment-100127739
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5974#issuecomment-100114332
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 scwf commented on the pull request:
https://github.com/apache/spark/pull/5838#issuecomment-100117333
@yhuai can you help review 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 project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5918#issuecomment-100121901
[Test build #32208 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32208/consoleFull)
for PR 5918 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5744#issuecomment-100127368
[Test build #32210 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32210/consoleFull)
for PR 5744 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5744#issuecomment-100127387
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/5744#issuecomment-100127383
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/5980#issuecomment-100115085
@yinxusen @jkbradley Instead of having three parameters to control the
buckets, is it simpler to let the users provide the boundaries directly? For
example, `[0, 1, 2,
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/5838#issuecomment-100117384
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5918#issuecomment-100120924
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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/5991#discussion_r29918612
--- Diff: python/pyspark/ml/feature.py ---
@@ -16,61 +16,73 @@
#
from pyspark.rdd import ignore_unicode_prefix
-from pyspark.ml.param.shared
Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/5939#issuecomment-100115666
@jkbradley , I think the Python docs for ChiSqSelector and
ChiSqSelectorModel have reached parity with Scala ones. Please correct me is I
misunderstand.
Yes, I
Github user jacek-lewandowski commented on the pull request:
https://github.com/apache/spark/pull/5977#issuecomment-100116778
@ScrapCodes do you mean should matchers ?
---
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 yinxusen commented on the pull request:
https://github.com/apache/spark/pull/5980#issuecomment-100116796
@mengxr How to represent `-inf` and `inf`? One possible solution is
```scala
val inf = Double.MaxValue
val negInf = Double.MinValue
splits =
Github user scwf commented on a diff in the pull request:
https://github.com/apache/spark/pull/5806#discussion_r29919305
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLConf.scala ---
@@ -32,6 +34,7 @@ private[spark] object SQLConf {
val CODEGEN_ENABLED =
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5742#issuecomment-100116863
[Test build #32199 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32199/consoleFull)
for PR 5742 at commit
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/5806#issuecomment-100116896
updated /cc @marmbrus , please take a look
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5742#issuecomment-100116867
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/5742#issuecomment-100116869
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/5999#issuecomment-100125452
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5744#issuecomment-100126134
[Test build #32210 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32210/consoleFull)
for PR 5744 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5999#issuecomment-100125754
[Test build #32209 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32209/consoleFull)
for PR 5999 at commit
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/5977#issuecomment-100126071
Yes.
---
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/5996#issuecomment-100112171
[Test build #32206 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32206/consoleFull)
for PR 5996 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5806#issuecomment-100116482
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/5806#issuecomment-100116475
[Test build #32198 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32198/consoleFull)
for PR 5806 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5806#issuecomment-100116484
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/5838#issuecomment-100119222
[Test build #32207 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32207/consoleFull)
for PR 5838 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5838#issuecomment-100118934
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5744#issuecomment-100125476
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5744#issuecomment-100125531
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5999#issuecomment-100125532
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5996#issuecomment-100111477
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
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/5821#issuecomment-100110996
ping @yhuai is this ok to go?
---
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/5996#issuecomment-100111443
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5821#issuecomment-100115917
[Test build #786 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/786/consoleFull)
for PR 5821 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/5989#issuecomment-100116112
@rekhajoshm , Thank you. As discussed in the JIRA issue, we can keep these
names as is. But we can improve the implementation of showDF() to print c-style
strings.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5838#issuecomment-100118893
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5918#issuecomment-100120917
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6002#issuecomment-100130010
[Test build #32214 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32214/consoleFull)
for PR 6002 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6002#issuecomment-100129926
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100132091
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
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/5927#issuecomment-100136265
But as @koeninger pointed out that it was not obvious to find out the
`TaskContext.get.partitionId()`. And may be for consistency with
mapPartitionsWithIndex, its okay to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100152398
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100152416
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5974#issuecomment-100154039
This LGTM. Will leave it a day or two for comments, but the logic seems
sound. this improves consistency, behavior vs docs, and avoids an avoidable
error
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100159709
[Test build #32220 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32220/consoleFull)
for PR 6006 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5744#issuecomment-100128735
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6002#issuecomment-100129915
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
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/6002
[SPARK-7466] DAG visualization: fix orphan nodes
Simple fix. We were comparing an option with `null`.
Before:
img
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100132082
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6004#issuecomment-100133196
[Test build #32217 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32217/consoleFull)
for PR 6004 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6000#issuecomment-100133197
[Test build #32204 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32204/consoleFull)
for PR 6000 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6000#issuecomment-100133202
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/6000#issuecomment-100133201
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/6005#issuecomment-100133068
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6005#issuecomment-100133127
[Test build #32216 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32216/consoleFull)
for PR 6005 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6004#issuecomment-100133059
@zsxwing @tdas
---
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/6004#issuecomment-100133079
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6005#issuecomment-100133053
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6004#issuecomment-100133058
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100140235
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100140283
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100140381
[Test build #32218 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32218/consoleFull)
for PR 6003 at commit
Github user tianyi commented on the pull request:
https://github.com/apache/spark/pull/5730#issuecomment-100143023
@marmbrus the test issue is fixed in #5983
---
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 tdas commented on the pull request:
https://github.com/apache/spark/pull/5927#issuecomment-100145100
Still ugly IMO.
On Fri, May 8, 2015 at 12:44 AM, Reynold Xin notificati...@github.com
wrote:
Why not just add to the javadoc of mapPartitions to
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5934
---
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/5998#issuecomment-100150482
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 the pull request:
https://github.com/apache/spark/pull/5871#issuecomment-100152788
A little test would be great, yeah. Would still love a quick look from
@tdas to make sure we're not missing something.
---
If your project is set up for it, you can
Github user MechCoder commented on the pull request:
https://github.com/apache/spark/pull/5748#issuecomment-100158192
@jkbradley can you have a look at this too? even if it won't be in this
release?
---
If your project is set up for it, you can reply to this email and have your
Github user jacek-lewandowski commented on the pull request:
https://github.com/apache/spark/pull/5977#issuecomment-100158160
I don't agree with this - you already use such notation in a few places
(for Idea search for `\d+\sseconds` except comments and string literals shows
16
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/6006#discussion_r29924867
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -1272,6 +1273,56 @@ class SQLContext(@transient val sparkContext:
SparkContext)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6006#issuecomment-100159728
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/6006#issuecomment-100159724
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/5922#issuecomment-100161796
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5967#issuecomment-100170305
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 this
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/5977#issuecomment-100170256
I am sorry, I was in an assumption we are religious about it. A quick
search across the codebase proved my wrong. Matchers are widely used in at
least recently added
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5967#issuecomment-100170292
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5830#issuecomment-100131676
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/5830#issuecomment-100131651
[Test build #32203 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32203/consoleFull)
for PR 5830 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6003#issuecomment-100132393
[Test build #32215 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32215/consoleFull)
for PR 6003 at commit
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/6004
[SPARK-7467] Dag visualization: treat checkpoint as an RDD operation
Such that a checkpoint RDD does not go into random scopes on the UI, e.g.
`take`. We've seen this in streaming.
You can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-100133880
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 project does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-100133881
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/4960#issuecomment-100133872
[Test build #32202 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32202/consoleFull)
for PR 4960 at commit
Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6003#discussion_r29921893
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonUtils.scala
---
@@ -53,4 +53,11 @@ private[spark] object PythonUtils {
def
Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/6003#discussion_r29921999
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -896,6 +900,77 @@ def fillna(self, value, subset=None):
return
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/5030#issuecomment-100145742
@rxin agree, this is probably not used so much, as it's fairly dependent on
Java serialization. To me the question here is just API consistency. If you're
thinking of it
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5996#issuecomment-100149955
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5996#issuecomment-100149932
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5974#issuecomment-100153175
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/5974#issuecomment-100153159
[Test build #32212 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32212/consoleFull)
for PR 5974 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5974#issuecomment-100153171
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
1 - 100 of 913 matches
Mail list logo
