Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/15910
Merged into master and branch-2.1. 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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16086
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
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16086
**[Test build #69443 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69443/consoleFull)**
for PR 16086 at commit
Github user NathanHowell commented on a diff in the pull request:
https://github.com/apache/spark/pull/16089#discussion_r90380594
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/text/TextFileFormat.scala
---
@@ -132,39 +128,17 @@ class
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16089#discussion_r90380316
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/text/TextFileFormat.scala
---
@@ -132,39 +128,17 @@ class
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/16089#discussion_r90380266
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/json/JacksonGenerator.scala
---
@@ -194,4 +194,8 @@ private[sql] class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16093
**[Test build #69451 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69451/consoleFull)**
for PR 16093 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16084
Yes, I noticed it before when I made a last change (avoiding the type
dispatch for each record) but I just made a safe choice.
It looks good to me as targeted because `JacksonParser`
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/15275
It seems we can cherry-pick into `branch-2.0` without conflicts, but can't
into `branch-1.6`.
Please let me know if we need to backport to `branch-1.6`.
---
If your project is set up for it,
GitHub user shea-parkes opened a pull request:
https://github.com/apache/spark/pull/16094
[SPARK-18541][Python]Add metadata parameter to pyspark.sql.Column.alias()
## What changes were proposed in this pull request?
Add a `metadata` keyword parameter to
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16094
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16093
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69447/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16093
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/16093
**[Test build #69447 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69447/consoleFull)**
for PR 16093 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16092
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69448/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16092
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/16092
**[Test build #69448 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69448/consoleFull)**
for PR 16092 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16084
**[Test build #69450 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69450/consoleFull)**
for PR 16084 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16092
**[Test build #69448 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69448/consoleFull)**
for PR 16092 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16089
**[Test build #69449 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69449/consoleFull)**
for PR 16089 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16084
Jenkins, this is ok to 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
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16089
Jenkins, this is ok to 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
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16092
Jenkins, this is ok to 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16093
**[Test build #69447 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69447/consoleFull)**
for PR 16093 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16092
There's a few other places that will need updating, including the
`source_file_regexes` in the test runner configuration (`modules.py`):
Github user ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13147#discussion_r90375148
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/planning/QueryPlanner.scala
---
@@ -27,6 +27,14 @@ import
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16093
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/16093
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69445/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16093
**[Test build #69445 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69445/consoleFull)**
for PR 16093 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15275
One important reason to prepare a backport for this is, as we deprecate the
settings to turn off unsafe and codegen since 1.6, we can't turn them off to
avoid JVM size limitation issue if users
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15958
If needed, we should not break the consistency. For example, `SHOW TABLE`
and `SHOW TABLES` are different.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16083#discussion_r90373452
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -189,14 +189,18 @@ case class DropTableCommand(
if
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16086
**[Test build #69446 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69446/consoleFull)**
for PR 16086 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16093
**[Test build #69445 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69445/consoleFull)**
for PR 16093 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16093
cc @wzhfy @hvanhovell
---
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 rxin opened a pull request:
https://github.com/apache/spark/pull/16093
[SPARK-18663][SQL] Simplify CountMinSketch aggregate implementation
## What changes were proposed in this pull request?
SPARK-18429 introduced count-min sketch aggregate function for SQL, but the
Github user jayadevanmurali commented on a diff in the pull request:
https://github.com/apache/spark/pull/16083#discussion_r90372901
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -189,14 +189,18 @@ case class DropTableCommand(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15975
**[Test build #69444 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69444/consoleFull)**
for PR 15975 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16080
I see. Will be careful in the future to not break the forward compatibility.
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15975
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 dreamworks007 commented on the issue:
https://github.com/apache/spark/pull/15616
ping ..
---
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
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16030
This is not a bug in `VectorizedParquetReader ` as @liancheng said, and
the root cause is that wrongly inferred types are passed into the reader in
`VectorizedParquetReader#initBatch`
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15275
This affects many places in code generation. I think this should be a
common issue for the users of previous versions. Should we make a backport to
branch-2.0 and branch-1.6? cc @rxin @ueshin @kiszk
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/15958
@gatorsmile Could you explicitly point out which part should be modified?
IMO we don't follow the HIVE syntax unconditionally. Thanks!
---
If your project is set up for it, you can reply to
Github user jiexiong commented on the issue:
https://github.com/apache/spark/pull/15722
Please retest!
---
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
Github user nsyca commented on the issue:
https://github.com/apache/spark/pull/16046
@hvanhovell On the placement of `LeftSemi`, have you got a chance to read
my response? Please share your thought. How are we going to implement the
support of deep correlation like the examples you
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/15780
Of course. I overlooked this comment.
---
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 sitalkedia commented on the issue:
https://github.com/apache/spark/pull/15722
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 this feature
enabled and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16086
**[Test build #69443 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69443/consoleFull)**
for PR 16086 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16090
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69437/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16091
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69439/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16091
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/16090
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/16091
**[Test build #69439 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69439/consoleFull)**
for PR 16091 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16090
**[Test build #69437 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69437/consoleFull)**
for PR 16090 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16091
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16091
Merging in master/branch-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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16068
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/16091
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/16091
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69438/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16068
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69436/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16091
**[Test build #69438 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69438/consoleFull)**
for PR 16091 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16068
**[Test build #69436 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69436/consoleFull)**
for PR 16068 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15994
**[Test build #69442 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69442/consoleFull)**
for PR 15994 at commit
Github user ChorPangChan commented on the issue:
https://github.com/apache/spark/pull/16000
`[error] * method
onStreamingStarted(org.apache.spark.streaming.scheduler.StreamingListenerStreamingStarted)Unit
in trait org.apache.spark.streaming.scheduler.StreamingListener is present
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15662
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69434/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15662
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/15662
**[Test build #69434 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69434/consoleFull)**
for PR 15662 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/15780
hi @kiszk can you address this comment?
https://github.com/apache/spark/pull/15780#discussion_r90199899 thanks!
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16000
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/16000
**[Test build #69441 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69441/consoleFull)**
for PR 16000 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16000
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69441/
Test FAILed.
---
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16088#discussion_r90366269
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -847,9 +847,11 @@ private[spark] class
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16088#discussion_r90366079
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
---
@@ -687,13 +687,14 @@ class SessionCatalog(
Github user mccheah commented on a diff in the pull request:
https://github.com/apache/spark/pull/16061#discussion_r90365964
--- Diff:
kubernetes/src/main/scala/org/apache/spark/scheduler/cluster/kubernetes/KubernetesClusterSchedulerBackend.scala
---
@@ -0,0 +1,222 @@
+/*
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16090#discussion_r90365422
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/createDataSourceTables.scala
---
@@ -58,13 +58,20 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16000
**[Test build #69441 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69441/consoleFull)**
for PR 16000 at commit
Github user ChorPangChan commented on the issue:
https://github.com/apache/spark/pull/16000
@vanzin
sorry, I think I remove some empty line accidently
the Scala style problem should be fixed now.
---
If your project is set up for it, you can reply to this email and have your
Github user foxish commented on the issue:
https://github.com/apache/spark/pull/16092
/cc @tnachen
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16092
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 foxish opened a pull request:
https://github.com/apache/spark/pull/16092
[SPARK-18662] Move resource managers to separate directory
## What changes were proposed in this pull request?
* Moves yarn and mesos scheduler backends to resource-managers/
sub-directory
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14079
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69433/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14079
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/14079
**[Test build #69433 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69433/consoleFull)**
for PR 14079 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16000
**[Test build #69440 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69440/consoleFull)**
for PR 16000 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16000
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69440/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16000
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16089
Yea then this is definitely fine.
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16080
We can have a test to check the table properties don't contain the entry,
can't we?
---
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 NathanHowell commented on the issue:
https://github.com/apache/spark/pull/16089
Yep. It uses the Hadoop `FileSystem` class to open files, just like
`TextOutputFormat` does.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16000
**[Test build #69440 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69440/consoleFull)**
for PR 16000 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16000
Sean can definitely take a look, but others like @tdas have more background
in streaming.
I want to take a look at the API hook up since it relates to other things
I'm working on, but I'm
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16000
ok to 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 so, or if the
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16080
@rxin I'm afraid it's hard to write forward compatibility tests using unit
test, we may need an external test infrastructure(python scripts) to do this.
---
If your project is set up for it, you
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16080#discussion_r90362091
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -232,17 +233,26 @@ private[spark] class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16088
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69432/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16088
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/16088
**[Test build #69432 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69432/consoleFull)**
for PR 16088 at commit
Github user ChorPangChan commented on the issue:
https://github.com/apache/spark/pull/16000
@ajbozarth
sorry, just in case you didn't noticed
I had make the change to handle the startTime
how do you think?
@srowen
hello,
I also think we need someone with
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16091
**[Test build #69439 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69439/consoleFull)**
for PR 16091 at commit
101 - 200 of 601 matches
Mail list logo
