Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18709
**[Test build #80445 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80445/testReport)**
for PR 18709 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18880
**[Test build #80444 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80444/testReport)**
for PR 18880 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18890
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/18890
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80436/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18790
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80434/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18790
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/18890
**[Test build #80436 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80436/testReport)**
for PR 18890 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18790
**[Test build #80434 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80434/testReport)**
for PR 18790 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18866
Hash function is not the only issue, one important difference is: hive will
shuffle before write, and make sure one bucket has only one file. Spark doesn't
shuffle and each write task may write a
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/16774
@BryanCutler You are right. Once `Future` complete the model can be cleaned
by GC. So the memory cost of the code has been optimized already. I didn't look
at the code carefully a few days
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18790
It sounds like we need to revisit all the optimizer rules for
`EventTimeWatermark`? We can do it in the separate PRs.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18846
**[Test build #80443 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80443/testReport)**
for PR 18846 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18846
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/18707
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/18790#discussion_r132095065
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -410,6 +413,14 @@ object
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18707
I was just asking about different fixes, I'm ok with the current fix.
thanks, merging to master/2.2!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user lvdongr commented on the issue:
https://github.com/apache/spark/pull/18756
The target of this pr is support to insert into specified columnsï¼ all
columns is no need ï¼ like insert into t(a, c) values (1, 0.8) .
---
If your project is set up for it, you can
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18790#discussion_r132094610
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -410,6 +413,14 @@ object
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18709
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 and wishes so, or if the
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18709#discussion_r132094303
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/interface.scala
---
@@ -205,6 +205,9 @@ case class BucketSpec(
*
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18756
I think this pr should be fixed in that way, maybe.
---
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 maropu commented on the issue:
https://github.com/apache/spark/pull/18756
I'm still not looking into this pr though, IMHO it would be good for users
to select parts of columns like other databases;
```
postgres=# create table t(a int, b text, c float8, d int);
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18648
**[Test build #80442 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80442/testReport)**
for PR 18648 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18648#discussion_r132093341
--- Diff:
sql/hive-thriftserver/src/test/scala/org/apache/spark/sql/hive/thriftserver/HiveCliSessionStateSuite.scala
---
@@ -0,0 +1,56 @@
+/*
+
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/18790#discussion_r132093307
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -872,6 +886,25 @@ object PushDownPredicate extends
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18648
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
Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/17894
I am also interested in implementation by level-3 BLAS. Can you post a
design doc first?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18855
since this PR only focus on `DiskStore`, shall we remove the new tests in
`BlockManagerSuite`? Seems the OOM only happens in `BlockManagerSuite`
---
If your project is set up for it, you can
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/18814
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18814
thanks, merging to master!
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18756
I see. This PR still requires users to provide all the columns, right?
---
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 issue:
https://github.com/apache/spark/pull/15435
**[Test build #80441 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80441/testReport)**
for PR 15435 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18869
**[Test build #80440 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80440/testReport)**
for PR 18869 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18869
**[Test build #80439 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80439/testReport)**
for PR 18869 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18869#discussion_r132088990
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -564,8 +611,27 @@ case class EqualNullSafe(left:
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18849#discussion_r132088495
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveExternalCatalog.scala ---
@@ -1175,6 +1205,27 @@ private[spark] class
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/18869#discussion_r132088507
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -564,8 +611,27 @@ case class
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18630
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/18630
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80433/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18630
**[Test build #80433 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80433/testReport)**
for PR 18630 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/18875#discussion_r132088249
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/jsonExpressions.scala
---
@@ -659,13 +660,19 @@ case class
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18849#discussion_r132087575
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala
---
@@ -908,7 +909,13 @@ private[hive] object HiveClientImpl {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18887
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80431/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18887
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/18887
**[Test build #80431 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80431/testReport)**
for PR 18887 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18474
Thanks for reproduction @kiszk. @wangjiaochun, I think the cause should be
explained here. I remember I reviewed similar PRs before where the cause was
`Utils.getOrCreateLocalRootDirs` is being
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18787
**[Test build #80438 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80438/testReport)**
for PR 18787 at commit
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/18890
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 and wishes so, or if the
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/18787
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18884#discussion_r132086218
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/FileFormatWriter.scala
---
@@ -269,50 +278,57 @@ object FileFormatWriter
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18849
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80432/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18849
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18884#discussion_r132085558
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/FileFormatWriter.scala
---
@@ -269,50 +278,57 @@ object FileFormatWriter
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18867
**[Test build #80437 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80437/testReport)**
for PR 18867 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18849
**[Test build #80432 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80432/testReport)**
for PR 18849 at commit
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/18799
Never mind @zsxwing I already opened a PR #18890
---
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/18890
**[Test build #80436 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80436/testReport)**
for PR 18890 at commit
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/18890
[SPARK-21596][SS] Ensure places calling HDFSMetadataLog.get check the
return value
When I was investigating a flaky test, I realized that many places don't
check the return value of
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18869
**[Test build #80435 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80435/testReport)**
for PR 18869 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18869
@gatorsmile I've checked the binary predicates in this change. Related test
cases are added.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18869#discussion_r132084124
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -484,7 +501,20 @@ object Equality {
}
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/18799
Merged to master. But there were conflicts with 2.2. Can you make another
PR for 2.2.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15435
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/18799
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15435
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80428/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18790
**[Test build #80434 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80434/testReport)**
for PR 18790 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15435
**[Test build #80428 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80428/testReport)**
for PR 15435 at commit
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/18790
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, or
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18869#discussion_r132081911
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -484,7 +501,20 @@ object Equality {
}
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18799
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80429/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18799
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/18799
**[Test build #80429 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80429/testReport)**
for PR 18799 at commit
Github user jiangxb1987 commented on a diff in the pull request:
https://github.com/apache/spark/pull/18867#discussion_r132081417
--- Diff: core/src/test/scala/org/apache/spark/MapOutputTrackerSuite.scala
---
@@ -176,7 +176,7 @@ class MapOutputTrackerSuite extends SparkFunSuite {
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/18790
Ok to test
On Aug 8, 2017 7:48 PM, "UCB AMPLab" wrote:
> Can one of the admins verify this patch?
>
> â
> You are receiving this because you
Github user tdas commented on the issue:
https://github.com/apache/spark/pull/18790
Ok to test
On Aug 8, 2017 7:48 PM, "UCB AMPLab" wrote:
> Can one of the admins verify this patch?
>
> â
> You are receiving this because
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18787
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80430/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18787
**[Test build #80430 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80430/testReport)**
for PR 18787 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18787
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 yaooqinn commented on a diff in the pull request:
https://github.com/apache/spark/pull/18648#discussion_r132080912
--- Diff:
sql/hive-thriftserver/src/test/scala/org/apache/spark/sql/hive/thriftserver/HiveCliSessionStateSuite.scala
---
@@ -0,0 +1,56 @@
+/*
+ *
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18887
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80422/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18887
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/18887
**[Test build #80422 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80422/testReport)**
for PR 18887 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18790
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 joseph-torres reopened a pull request:
https://github.com/apache/spark/pull/18790
[SPARK-21587][SS] Added pushdown through watermarks.
## What changes were proposed in this pull request?
* Filter predicates can be pushed through EventTimeWatermark if they're
Github user joseph-torres commented on the issue:
https://github.com/apache/spark/pull/18790
I'm told I can reopen this instead of making a new PR for the same branch.
Reopening with fixed commit history.
---
If your project is set up for it, you can reply to this email and have
Github user joseph-torres closed the pull request at:
https://github.com/apache/spark/pull/18889
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18790
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80424/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18790
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/18790
**[Test build #80424 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80424/testReport)**
for PR 18790 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18849
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/18849
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80423/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18849
**[Test build #80423 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80423/testReport)**
for PR 18849 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18889
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 joseph-torres commented on the issue:
https://github.com/apache/spark/pull/18790
Created https://github.com/apache/spark/pull/18889 with everything
cherrypicked into the right place.
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user joseph-torres opened a pull request:
https://github.com/apache/spark/pull/18889
[SPARK-21587][SS] Added pushdown through watermarks.
## What changes were proposed in this pull request?
Filter predicates can be pushed through EventTimeWatermark if they're
Github user joseph-torres closed the pull request at:
https://github.com/apache/spark/pull/18790
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18878
Thanks for confirmation.
---
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 brandonJY closed the pull request at:
https://github.com/apache/spark/pull/18878
---
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 brandonJY commented on the issue:
https://github.com/apache/spark/pull/18878
Never mind. I found it is actually something in my config. Silly mistake.
Sorry for the trouble. Closing this PR now.
---
If your project is set up for it, you can reply to this email and have
Github user wangjiaochun commented on the issue:
https://github.com/apache/spark/pull/18474
Thanks,I will resolve all problems. @kiszk
---
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
1 - 100 of 534 matches
Mail list logo