Github user reactormonk commented on the pull request:
https://github.com/apache/spark/pull/8240#issuecomment-132560703
I haven't found any documentation on how to write UDFs with R.
https://issues.apache.org/jira/browse/SPARK-6817 tells me it's not going to
happen anytime soon.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5516#issuecomment-132571806
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/8310#issuecomment-132592882
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/8311#issuecomment-132601493
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/8311#issuecomment-132601446
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/8264#issuecomment-132604042
[Test build #41243 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41243/consoleFull)
for PR 8264 at commit
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/8273#issuecomment-132549915
/CC @rxin
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8308#issuecomment-132559067
I think the additional changes I mentioned are worth fixing here since
they're very much of the same form. If you have time to scan for similar
problems in nearby
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8102#issuecomment-132560134
**[Test build #41230 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41230/console)**
for PR 8102 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8102#issuecomment-132560183
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 project does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8102#issuecomment-132560185
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/7874#issuecomment-132563477
**[Test build #41231 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41231/console)**
for PR 7874 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7874#issuecomment-132563638
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/7874
---
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/8309#issuecomment-132571063
[Test build #41236 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41236/console)
for PR 8309 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8311#issuecomment-132602862
[Test build #41241 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41241/consoleFull)
for PR 8311 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8268#issuecomment-132605286
[Test build #41242 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41242/consoleFull)
for PR 8268 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8308#issuecomment-132607672
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 yu-iskw commented on a diff in the pull request:
https://github.com/apache/spark/pull/8256#discussion_r37416961
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/GaussianMixtureModel.scala
---
@@ -53,32 +54,48 @@ class GaussianMixtureModel(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7602#issuecomment-132560076
[Test build #1666 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1666/console)
for PR 7602 at commit
Github user sabhyankar commented on a diff in the pull request:
https://github.com/apache/spark/pull/8241#discussion_r37410650
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/classification/NaiveBayes.scala ---
@@ -83,9 +86,13 @@ class NaiveBayesModel private[spark] (
Github user eshilts commented on the pull request:
https://github.com/apache/spark/pull/5516#issuecomment-132584944
AFAICT, the build fails on files I haven't touched. I get assorted failures
unrelated to this patch when running all tests locally, too. I'm not sure why
that is.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8264#issuecomment-132590726
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/8264#issuecomment-132590724
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 Lewuathe opened a pull request:
https://github.com/apache/spark/pull/8311
[SPARK-10111][PySpark] StringIndexerModel lacks of method labels
PySpark `StringIndexerModel` implements `labels` property.
You can merge this pull request into a Git repository by running:
$
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8264#issuecomment-132602958
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/8300#discussion_r37415899
--- Diff: python/pyspark/sql/dataframe.py ---
@@ -1223,10 +1226,8 @@ def withColumnRenamed(self, existing, new):
df.withColumnRenamed('age',
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8279#issuecomment-132554181
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
GitHub user MechCoder opened a pull request:
https://github.com/apache/spark/pull/8309
[SPARK-10108] Add since tags to mllib.feature
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MechCoder/spark tags_feature
Alternatively you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8279#issuecomment-132554178
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 project does
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8267#issuecomment-132557394
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/8267#issuecomment-132557389
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/7874#issuecomment-132561008
[Test build #1667 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1667/console)
for PR 7874 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/8276#issuecomment-132571243
@shivaram, I tried to support ArrayType. By adding code like:
// Convert Seq[Any] to Array[Any]
val value =
if
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5516#issuecomment-132577837
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/5516#issuecomment-132577801
[Test build #41238 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41238/console)
for PR 5516 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5516#issuecomment-132577839
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/8310#issuecomment-132592884
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yu-iskw commented on a diff in the pull request:
https://github.com/apache/spark/pull/8256#discussion_r37418372
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/KMeans.scala ---
@@ -430,11 +430,14 @@ class KMeans private (
/**
*
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5516#issuecomment-132571833
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/8310#issuecomment-132584034
[Test build #41239 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41239/consoleFull)
for PR 8310 at commit
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8264#issuecomment-132586765
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8264#issuecomment-132587189
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/8264#issuecomment-132587149
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/8312#issuecomment-132614509
Please look at
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark before
opening a PR
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7943#issuecomment-132614380
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/8279#issuecomment-132554106
**[Test build #41227 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41227/console)**
for PR 8279 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8296#issuecomment-132554058
[Test build #41235 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41235/consoleFull)
for PR 8296 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8033#issuecomment-132565831
[Test build #1668 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1668/consoleFull)
for PR 8033 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8310#issuecomment-132583429
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/8310#issuecomment-132583366
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/8312#issuecomment-132607361
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/8308#issuecomment-132607676
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/8308#issuecomment-132607463
[Test build #41234 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41234/console)
for PR 8308 at commit
Github user yu-iskw commented on a diff in the pull request:
https://github.com/apache/spark/pull/8256#discussion_r37418271
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/KMeans.scala ---
@@ -430,11 +430,14 @@ class KMeans private (
/**
*
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/7943#issuecomment-132614143
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7943#issuecomment-132614365
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 sarutak commented on a diff in the pull request:
https://github.com/apache/spark/pull/8273#discussion_r37403257
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JdbcUtils.scala
---
@@ -122,7 +123,15 @@ object JdbcUtils extends Logging
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/8296#issuecomment-132551589
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 ehnalis commented on the pull request:
https://github.com/apache/spark/pull/8308#issuecomment-13238
Would you like if I go through all of them?
---
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/8267#issuecomment-132555177
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 MechCoder commented on the pull request:
https://github.com/apache/spark/pull/8309#issuecomment-132555433
@mengxr
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/7602#issuecomment-132564803
There we go, tests pass. What do you think @andrewor14 ? I'm OK with it.
---
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/8264#issuecomment-132603641
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/8264#issuecomment-132603669
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 crakjie opened a pull request:
https://github.com/apache/spark/pull/8312
Add optional getters to the Row
Add a clean syntax to request nullable field
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/crakjie/spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8296#issuecomment-132552593
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/8296#issuecomment-132552618
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/8267#issuecomment-132555089
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/8309#issuecomment-132555078
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/8309#issuecomment-132555178
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/8309#issuecomment-132571221
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/8309#issuecomment-132571222
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/8264#issuecomment-132586137
[Test build #41233 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41233/console)
for PR 8264 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8264#issuecomment-132586295
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/8310#issuecomment-132592417
[Test build #41239 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41239/console)
for PR 8310 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8309#issuecomment-132556766
[Test build #41236 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41236/consoleFull)
for PR 8309 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7874#issuecomment-132563634
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/5516#issuecomment-132572432
[Test build #41238 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41238/consoleFull)
for PR 5516 at commit
GitHub user Lewuathe opened a pull request:
https://github.com/apache/spark/pull/8310
[SPARK-10110] StringIndexer lacks of parameter handleInvalid.
Pyspark StringIndexer should implement handleInvalid API
You can merge this pull request into a Git repository by running:
$ git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8268#issuecomment-132603652
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/8268#issuecomment-132603633
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/8311#issuecomment-132606367
[Test build #41241 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41241/console)
for PR 8311 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8311#issuecomment-132606569
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/8311#issuecomment-132606566
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/8268#issuecomment-132616734
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/8268#issuecomment-132616663
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/8268#issuecomment-132618969
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/8288#issuecomment-132624923
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/8288#issuecomment-132624956
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/8279#issuecomment-132635550
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/8268#issuecomment-132635590
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/5400#issuecomment-132644806
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/8279#issuecomment-132650927
[Test build #41252 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41252/console)
for PR 8279 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8268#issuecomment-132665588
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/8273#discussion_r37434622
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/jdbc/JdbcUtils.scala
---
@@ -122,7 +123,15 @@ object JdbcUtils extends Logging {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8296#issuecomment-132619920
[Test build #1669 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/1669/consoleFull)
for PR 8296 at commit
Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/8288#issuecomment-132621530
@MechCoder Alright. Thank you for letting me know.
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/8309#issuecomment-132625744
No, for existing PRs, we ask the authors to stay with `@since` tags because
most of them are first-time contributors. For new PRs, we should use `@Since`
annotation
Github user sabhyankar commented on the pull request:
https://github.com/apache/spark/pull/8241#issuecomment-132631199
Hi @holdenk I have moved the common logic to a trait and am mixin it with
the model. Let me know if you see something that needs to be corrected. I am
still getting
1 - 100 of 819 matches
Mail list logo
