Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14500
We do not generate golden files anymore. Let's port those tests. 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
Github user davies commented on the issue:
https://github.com/apache/spark/pull/14500
@yhuai Just checked the repair.q, it's kind of useless, already covered by
out unit test, we could just ignore it.
---
If your project is set up for it, you can reply to this email and have your
GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/14497
[SPARK-16901] Hive settings in hive-site.xml may be overridden by Hive's
default values
## What changes were proposed in this pull request?
When we create the HiveConf for metastore client, we
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/14498
[SPARK-16904] [SQL] Removal of Hive Built-in Hash Functions and
TestHiveFunctionRegistry [WIP]
### What changes were proposed in this pull request?
Currently, the Hive built-in `hash`
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12944
---
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/14497
**[Test build #63238 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63238/consoleFull)**
for PR 14497 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12944#discussion_r73612252
--- Diff:
common/network-shuffle/src/main/java/org/apache/spark/network/shuffle/ShuffleIndexInformation.java
---
@@ -0,0 +1,63 @@
+/*
+ *
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/12944
Hotfixing in #14499 to fix the build. My bad.
---
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 eyalfa commented on the issue:
https://github.com/apache/spark/pull/1
@cloud-fan this turned out to be a bit wider than I thought it is, I had to
touch few areas:
1. ExpressionEncoder, (seems to be your craft)
2. AstBuilder, (@hvanhovell)
3. CreateStruct,
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/13152#discussion_r73615142
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManagerId.scala
---
@@ -69,24 +72,39 @@ class BlockManagerId private (
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/13152#discussion_r73615218
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMaster.scala ---
@@ -50,12 +50,20 @@ class BlockManagerMaster(
logInfo("Removal of
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14500
**[Test build #63244 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63244/consoleFull)**
for PR 14500 at commit
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/14308
attaching a quick audit of example data files and what examples reference
them, take from this branch
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14462
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9936
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/13123
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10356
---
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/14500#discussion_r73621345
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -425,6 +431,96 @@ case class AlterTableDropPartitionCommand(
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10943
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14101
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14402
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14343
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/13923
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14347
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14424
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9866
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14437
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10701
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14390
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10474
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14310
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/13248
---
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 vanzin closed the pull request at:
https://github.com/apache/spark/pull/14495
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/14423
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/10676
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/12000
---
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 shubhamchopra commented on a diff in the pull request:
https://github.com/apache/spark/pull/13152#discussion_r73593762
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -159,8 +162,27 @@ private[spark] class BlockManager(
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14428
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63236/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14428
**[Test build #63236 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63236/consoleFull)**
for PR 14428 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14483
Merged to master/2.0
---
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/14478
---
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/12790
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 JoshRosen opened a pull request:
https://github.com/apache/spark/pull/14499
[HOTFIX] Remove unnecessary imports from #12944 that broke build
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/JoshRosen/spark hotfix
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/13152#discussion_r73615313
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManagerId.scala
---
@@ -103,8 +121,11 @@ private[spark] object BlockManagerId {
* @param
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/13152#discussion_r73615629
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMessages.scala ---
@@ -111,4 +111,6 @@ private[spark] object BlockManagerMessages {
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14428
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/14470
---
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/11127
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63233/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12790
**[Test build #63239 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63239/consoleFull)**
for PR 12790 at commit
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/14396
Hi @NYcleaner,
This pull request isn't the right venue for making PySpark API feature
requests. Instead, please file a ticket at
https://issues.apache.org/jira/browse/SPARK.
---
If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14500
**[Test build #63243 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63243/consoleFull)**
for PR 14500 at commit
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/13152#discussion_r73615368
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMaster.scala ---
@@ -50,12 +50,20 @@ class BlockManagerMaster(
logInfo("Removal of
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/13152#discussion_r73615208
--- Diff:
core/src/main/scala/org/apache/spark/storage/BlockManagerMaster.scala ---
@@ -50,12 +50,20 @@ class BlockManagerMaster(
logInfo("Removal of
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14495
Alright, commit is pushed, lots of PRs are in the process of being closed.
---
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14232#discussion_r73622103
--- Diff:
common/network-shuffle/src/main/java/org/apache/spark/network/shuffle/protocol/BlockTransferMessage.java
---
@@ -35,6 +35,9 @@
* shuffle
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14500
**[Test build #63243 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63243/consoleFull)**
for PR 14500 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14500
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/14500
**[Test build #63244 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63244/consoleFull)**
for PR 14500 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14500
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63244/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14498
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63247/
Test PASSed.
---
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/13680#discussion_r73627677
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/catalyst/expressions/UnsafeArrayData.java
---
@@ -25,30 +25,36 @@
import
Github user falaki commented on the issue:
https://github.com/apache/spark/pull/14118
@lw-lin thanks a lot for the clear summary.
After seeing some use cases, I think it is better to apply nullValue to all
types, including `StringType`. `treatEmptyValuesAsNulls` seems a special
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12819
**[Test build #63250 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63250/consoleFull)**
for PR 12819 at commit
Github user NYcleaner commented on the issue:
https://github.com/apache/spark/pull/14396
Oh. sorry. I am a newer , thank you for your patience and help
---
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 vanzin commented on the issue:
https://github.com/apache/spark/pull/13428
Two suggestions, otherwise I'm not familiar enough with Ivy - I'll trust
you guys to know what you're doing. :-)
---
If your project is set up for it, you can reply to this email and have your
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14482#discussion_r73638320
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/CatalogImpl.scala ---
@@ -272,18 +259,15 @@ class CatalogImpl(sparkSession: SparkSession)
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14500
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 vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9571#discussion_r73623629
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -114,28 +123,45 @@ class HistoryServer(
* this UI with the
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/14155#discussion_r73623682
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -301,9 +298,6 @@ case class AlterTableSerDePropertiesCommand(
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9571#discussion_r73624457
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -226,6 +259,135 @@ class HistoryServer(
}
/**
+ *
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9571#discussion_r73624479
--- Diff: core/src/main/scala/org/apache/spark/metrics/MetricsSystem.scala
---
@@ -204,6 +204,8 @@ private[spark] class MetricsSystem private (
}
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14501
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63245/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14501
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/14467
**[Test build #63248 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63248/consoleFull)**
for PR 14467 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14501
**[Test build #63245 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63245/consoleFull)**
for PR 14501 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14491
Could you look through these as below? at least I found one more.
```
src/main/java/org/apache/spark/examples/ml/JavaDecisionTreeClassificationExample.java:
// Load the data
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/12694
I'm not a fan of this approach. This means that every invocation of the
launcher code will create temp files and have to deal with cleaning it up;
except the launcher cannot do it, because the jvm
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14445
---
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 zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/12819
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 this feature
enabled
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14155#discussion_r73639529
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -301,9 +298,6 @@ case class AlterTableSerDePropertiesCommand(
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13701
**[Test build #63255 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63255/consoleFull)**
for PR 13701 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9571#discussion_r73623757
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -226,6 +259,135 @@ class HistoryServer(
}
/**
+ *
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9571#discussion_r73623780
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -226,6 +259,135 @@ class HistoryServer(
}
/**
+ *
Github user mgummelt commented on the issue:
https://github.com/apache/spark/pull/11157
> How about the rest of the ports?
Unused resources in an offer are implicitly declined.
> We will have only one executor per job right?
if they specify a port, then one executor per
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9571#discussion_r73623900
--- Diff:
core/src/main/scala/org/apache/spark/deploy/history/HistoryServer.scala ---
@@ -226,6 +259,135 @@ class HistoryServer(
}
/**
+ *
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14499
**[Test build #3203 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3203/consoleFull)**
for PR 14499 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14498
**[Test build #63247 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63247/consoleFull)**
for PR 14498 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14498
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 WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/14156
@srowen OK I close the pr for now if I found better way to optimize it I
will reopen it, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user WeichenXu123 closed the pull request at:
https://github.com/apache/spark/pull/14156
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12819
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/12819
**[Test build #63251 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63251/consoleFull)**
for PR 12819 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12819
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63251/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12819
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
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12819
**[Test build #63250 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63250/consoleFull)**
for PR 12819 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12819
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63250/
Test FAILed.
---
GitHub user princejwesley opened a pull request:
https://github.com/apache/spark/pull/14502
[SPARK-16909][Spark Core] - Streaming for postgreSQL JDBC driver
As per the postgreSQL JDBC driver
Github user inouehrs commented on the issue:
https://github.com/apache/spark/pull/13459
From the participants list, it looks like @SparkQA is not checking this PR.
Is there anyway to call attention of the jenkins system?
---
If your project is set up for it, you can reply to this
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13459
I'm not sure how to trigger a test manually, will check with my colleague
later
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/1
Why? I think we only need to touch `Analyzer` and remove the execution
logic from `CreateStruct`. Wherever we create `CreateStruct`, we just keep it,
but replace(or resolve) it in Analyzer.
---
201 - 300 of 468 matches
Mail list logo
