Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16196
**[Test build #69795 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69795/consoleFull)**
for PR 16196 at commit
GitHub user a-roberts opened a pull request:
https://github.com/apache/spark/pull/16196
[SPARK-18231] Optimise SizeEstimator implementation
## What changes were proposed in this pull request?
Several improvements to the SizeEstimator for performance, most of the
benefit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16191
Could you pleade close this @zhuangxue ?
---
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 issue:
https://github.com/apache/spark/pull/16193
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69787/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16193
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16187
**[Test build #3473 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3473/consoleFull)**
for PR 16187 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16193
**[Test build #69787 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69787/consoleFull)**
for PR 16193 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16192
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16192
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69783/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16192
**[Test build #69783 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69783/consoleFull)**
for PR 16192 at commit
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/16189#discussion_r91259169
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -432,6 +435,57 @@ private[spark] class Executor(
}
/**
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/16189#discussion_r91259805
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -432,6 +435,57 @@ private[spark] class Executor(
}
/**
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/16189#discussion_r91258960
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -432,6 +435,57 @@ private[spark] class Executor(
}
/**
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/16189#discussion_r91257339
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -432,6 +435,57 @@ private[spark] class Executor(
}
/**
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16194
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16194
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69789/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16194
**[Test build #69789 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69789/consoleFull)**
for PR 16194 at commit
GitHub user daisukebe opened a pull request:
https://github.com/apache/spark/pull/16195
[Spark-18765] [CORE] Make values for
spark.yarn.{am|driver|executor}.memoryOverhead have configurable units
## What changes were proposed in this pull request?
Make values for
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16195
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 project does not have this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16056
**[Test build #69794 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69794/consoleFull)**
for PR 16056 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16129
Merged to master/2.1
---
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,
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16129
---
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 issue:
https://github.com/apache/spark/pull/15722
**[Test build #69793 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69793/consoleFull)**
for PR 15722 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/15722
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 feature
enabled and wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16171
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69791/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16171
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16171
**[Test build #69791 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69791/consoleFull)**
for PR 16171 at commit
Github user windpiger commented on the issue:
https://github.com/apache/spark/pull/16173
when HttpBroadCastFactory & TorrentBroadcastFactory both exists, it is use
spark.broadcast.factory to change the implement.
it is better to modify the comment of BroadcastFactory than
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16177
good catch! LGTM, cc @hvanhovell to take another 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 does not
Github user sarutak commented on the issue:
https://github.com/apache/spark/pull/16190
Also, Spark Shell says as follows.
```
Spark context Web UI available at http://192.168.1.1:4040
```
---
If your project is set up for it, you can reply to this email and have your
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16193
Would it be easier if we create a logical node for python evaluator? We do
have one in Spark 1.6 but get removed in 2.0, not sure why
---
If your project is set up for it, you can reply to this
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16193#discussion_r91250161
--- Diff: python/pyspark/sql/tests.py ---
@@ -360,6 +360,15 @@ def test_broadcast_in_udf(self):
[res] = self.spark.sql("SELECT
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16122
**[Test build #69792 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69792/consoleFull)**
for PR 16122 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16171
**[Test build #69791 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69791/consoleFull)**
for PR 16171 at commit
Github user sarutak commented on the issue:
https://github.com/apache/spark/pull/16190
Of course, HistoryServer works with SSL enabled.
---
If your project is set
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16068#discussion_r91248703
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveUDFSuite.scala
---
@@ -487,6 +489,28 @@ class HiveUDFSuite extends QueryTest
Github user sarutak commented on the issue:
https://github.com/apache/spark/pull/16190
cc: @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
enabled and wishes so, or if
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16129
I changed the title. The PR does add a correctness test, at least one that
addresses the case being fixed here.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16187
**[Test build #3473 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3473/consoleFull)**
for PR 16187 at commit
Github user sarutak commented on the issue:
https://github.com/apache/spark/pull/16190
I've confirmed I can access MasterPage and WorkerPage with SSL enabled.
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16149
What you have is fine (though I might name it `ylogy` or something). I
don't see other places in the code that compute x ln x or something similar, so
it's OK to make this a private function. You
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16190
**[Test build #69790 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69790/consoleFull)**
for PR 16190 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16194
**[Test build #69789 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69789/consoleFull)**
for PR 16194 at commit
Github user actuaryzhang commented on the issue:
https://github.com/apache/spark/pull/16149
@srowen @sethah
Thanks for the comments. Yes, the major use case is to be able to handle
multiple trials (integer weight, real-valued response). Indeed, a better way to
do this is through
GitHub user zhengruifeng opened a pull request:
https://github.com/apache/spark/pull/16194
[SPARK-18767][ML] Unify Models' toString methods
## What changes were proposed in this pull request?
override models' toString methods to output some key info
## How was this
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16150#discussion_r91247257
--- Diff: R/pkg/R/mllib.R ---
@@ -1852,9 +1867,9 @@ summary.treeEnsemble <- function(model) {
# Get the summary of a Random Forest Regression
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16161
option 1 is better, but this PR only adds the support for
`scala.collection.immutable.Map`, with a very specific way: we can't extend it
to support `scala.collection.mutable.Map` or `List`.
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/16150#discussion_r91247076
--- Diff: R/pkg/R/mllib.R ---
@@ -661,7 +665,10 @@ setMethod("fitted", signature(object = "KMeansModel"),
# Get the summary of a k-means model
Github user actuaryzhang commented on a diff in the pull request:
https://github.com/apache/spark/pull/16149#discussion_r91246870
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/regression/GeneralizedLinearRegression.scala
---
@@ -479,7 +479,12 @@ object
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16131
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16187
LGTM pending test.
---
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
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16131
Merged to master, and to 2.1 to match SPARK-18166
---
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 issue:
https://github.com/apache/spark/pull/16182
**[Test build #3472 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3472/consoleFull)**
for PR 16182 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16187#discussion_r91246228
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetFileFormat.scala
---
@@ -61,7 +61,7 @@ class
Github user ChorPangChan commented on the issue:
https://github.com/apache/spark/pull/16000
I understand its possible,
and actually I agree having a hooking mechanism is a better approach as
well in turns of programing and if we really need streaming to support history
server.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16117
---
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 issue:
https://github.com/apache/spark/pull/16173
Hm, that's a good point. I don't recall ever hearing much about someone
actually plugging in an implementation. It's a modest change you're proposing
and not unreasonable, I just don't know how much
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/16117
Since this will involve breaking change if we merge it after 2.1 release,
and actually I think it belongs to the scope of QA, so I'll merge it into
master and branch-2.1, thanks for all your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16043
**[Test build #69788 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69788/consoleFull)**
for PR 16043 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16193
cc @cloud-fan @davies @liancheng
---
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 gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16193#discussion_r91244968
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/python/ExtractPythonUDFs.scala
---
@@ -166,3 +174,40 @@ object ExtractPythonUDFs
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16193#discussion_r91244760
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/python/BatchEvalPythonExecSuite.scala
---
@@ -0,0 +1,99 @@
+/*
+ * Licensed to
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16193
**[Test build #69787 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69787/consoleFull)**
for PR 16193 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/16193
[SPARK-18766] [SQL] Push Down Filter Through BatchEvalPython
### What changes were proposed in this pull request?
Currently, when users use Python UDF in Filter, BatchEvalPython is always
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/14365
As we replace schema inferring with metastore schema completely by #14690
for converted Hive tables, we may not have the chance to detect the mismatch
between Orc file's physical schema and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16109
**[Test build #69784 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69784/consoleFull)**
for PR 16109 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16109
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69784/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16109
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16192
**[Test build #69785 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69785/consoleFull)**
for PR 16192 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16109
**[Test build #69786 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69786/consoleFull)**
for PR 16109 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16109
**[Test build #69784 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69784/consoleFull)**
for PR 16109 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16192
**[Test build #69783 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69783/consoleFull)**
for PR 16192 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16192
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 feature
enabled and wishes so,
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/16109#discussion_r91242517
--- Diff:
external/kafka-0-10-sql/src/main/scala/org/apache/spark/sql/kafka010/KafkaSource.scala
---
@@ -102,7 +102,7 @@ private[kafka010] case class
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/16109#discussion_r91242485
--- Diff:
external/kafka-0-10-sql/src/test/scala/org/apache/spark/sql/kafka010/KafkaTestUtils.scala
---
@@ -286,36 +286,56 @@ class KafkaTestUtils extends
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/16109#discussion_r91242466
--- Diff:
external/kafka-0-10-sql/src/test/scala/org/apache/spark/sql/kafka010/KafkaSourceSuite.scala
---
@@ -811,6 +812,12 @@ class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16192
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69782/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16189
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69776/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16187
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69779/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16187
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16190
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16182
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69774/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16182
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16190
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69781/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16189
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16192
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16165
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16165
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69773/
Test FAILed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16188
@zhuangxue close this PR 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 feature
enabled and
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/16191
Could you please ask this question on the user list or on StackOverflow?
Opening a PR is not an avenue for questions. Also, could you please close this
PR? Thanks!
---
If your project is set up
501 - 590 of 590 matches
Mail list logo
