Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14230
**[Test build #62404 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62404/consoleFull)**
for PR 14230 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14228
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62402/
Test PASSed.
---
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/14230
[SPARK-16584][SQL] Move regexp unit tests to RegexpExpressionsSuite
## What changes were proposed in this pull request?
This patch moves regexp related unit tests from StringExpressionsSuite to
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/14179
The error in the link you provided
(https://gist.github.com/krishnakalyan3/6585a1007b731e82fede1b942ea00bec) are
odd, I have not seen them. What is the version of testthat you have installed?
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14228
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/14228
**[Test build #62402 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62402/consoleFull)**
for PR 14228 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14132
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62403/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14132
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/14132
**[Test build #62403 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62403/consoleFull)**
for PR 14132 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14132
SQL generation is fragile and hard to maintain. This is a well-known issue
in Federation server. In Spark SQL, we are converting analyzed plans instead of
optimized plans. Thus, it is much
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Oh, for the worst case, I hope to skip all. :) I'll investigate them too.
Thank you for the pointers!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14132
To help you find the JIRAs, you can see the umbrella JIRA:
https://issues.apache.org/jira/browse/SPARK-11012
---
If your project is set up for it, you can reply to this email and have your
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14132
I am afraid you might forget the case of Generators/UDTF. I am not sure the
plan might be different if we use `Hint` with Generators/UDTF. You have to
write many different queries. See the JIRA:
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Thank you. I found these your PR looks nice to me. I'll study them for a
while and update this PR properly.
[SPARK-12720][SQL] SQL Generation Support for Cube, Rollup, and Grouping
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14132
Yeah, check the change history of `SQLBuilder` and `LogicalPlanToSQLSuite`.
You can find many examples.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Let me see the example PRs.
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14132
I did a few PRs for SQL generation in the past. To do it properly, you have
to enumerate all the cases. Any missing case will be a bug. Could you post all
the analyzed plans you can create?
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14132
**[Test build #62403 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62403/consoleFull)**
for PR 14132 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14228
**[Test build #62402 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62402/consoleFull)**
for PR 14228 at commit
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/14227
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14223
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62399/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14223
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/14223
**[Test build #62399 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62399/consoleFull)**
for PR 14223 at commit
Github user sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/14225
cc @ericl
---
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 sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/14227
cc @ericl
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14229
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62401/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14229
**[Test build #62401 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62401/consoleFull)**
for PR 14229 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14229
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/14229
**[Test build #62401 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62401/consoleFull)**
for PR 14229 at commit
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/13670
Been busy the last couple days, I'll take a look at this Monday
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14201
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/14201
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62397/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14201
**[Test build #62397 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62397/consoleFull)**
for PR 14201 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14227
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/14227
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62396/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14227
**[Test build #62396 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62396/consoleFull)**
for PR 14227 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14229
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/14229
**[Test build #62400 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62400/consoleFull)**
for PR 14229 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14229
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62400/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14229
**[Test build #62400 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62400/consoleFull)**
for PR 14229 at commit
GitHub user yinxusen opened a pull request:
https://github.com/apache/spark/pull/14229
[SPARK-16447][ML][SparkR] LDA wrapper in SparkR
## What changes were proposed in this pull request?
Add LDA Wrapper in SparkR with the following interfaces:
- spark.lda(data,
Github user hbhanawat commented on a diff in the pull request:
https://github.com/apache/spark/pull/14202#discussion_r71058847
--- Diff:
core/src/main/scala/org/apache/spark/executor/CoarseGrainedExecutorBackend.scala
---
@@ -147,7 +148,10 @@ private[spark] class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14223
**[Test build #62399 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62399/consoleFull)**
for PR 14223 at commit
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/14222#discussion_r71058680
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/KeyValueGroupedDataset.scala ---
@@ -177,10 +178,33 @@ class KeyValueGroupedDataset[K, V]
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14223
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14223
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62395/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14223
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/14223
**[Test build #62395 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62395/consoleFull)**
for PR 14223 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14228
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62398/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14228
**[Test build #62398 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62398/consoleFull)**
for PR 14228 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14228
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/14228
**[Test build #62398 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62398/consoleFull)**
for PR 14228 at commit
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/14169#discussion_r71058385
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkSqlParser.scala ---
@@ -1329,7 +1329,7 @@ class SparkSqlAstBuilder(conf: SQLConf)
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/14228#discussion_r71058312
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/columnar/InMemoryTableScanExec.scala
---
@@ -148,7 +161,7 @@ private[sql] case class
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/14228
[SPARK-16583] [SQL] [WIP] Improve Partition Pruning in InMemoryTableScanExec
What changes were proposed in this pull request?
Currently, column pruning in `InMemoryTableScanExec` only
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14201
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/14201
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62392/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14201
**[Test build #62392 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62392/consoleFull)**
for PR 14201 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14201
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/14201
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62393/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14201
**[Test build #62393 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62393/consoleFull)**
for PR 14201 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14201
**[Test build #62397 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62397/consoleFull)**
for PR 14201 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14201
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62390/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14201
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 andreweduffy commented on the issue:
https://github.com/apache/spark/pull/14201
Gotcha, sorry about the force overwrites, in some projects I've worked on
that's preferred to keep clean history, though for review I can see why
separate units is easier. Thanks again for
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14201
**[Test build #62390 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62390/consoleFull)**
for PR 14201 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14227
**[Test build #62396 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62396/consoleFull)**
for PR 14227 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14167
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/14167
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62391/
Test PASSed.
---
GitHub user sameeragarwal opened a pull request:
https://github.com/apache/spark/pull/14227
[SPARK-16582][SQL] Explicitly define isNull = false for non-nullable
expressions
## What changes were proposed in this pull request?
This patch is just a slightly safer way to fix
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14167
**[Test build #62391 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62391/consoleFull)**
for PR 14167 at commit
Github user lw-lin closed the pull request at:
https://github.com/apache/spark/pull/14214
---
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 lw-lin commented on the issue:
https://github.com/apache/spark/pull/14214
Sure let's rewrite the incremental planner to solve problems more
holistically; actually this patch is not satisfying to myself either. So I'm
closing this, and -- thank you for the ideas!
---
If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14223
**[Test build #62395 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62395/consoleFull)**
for PR 14223 at commit
Github user markgrover commented on the issue:
https://github.com/apache/spark/pull/14223
The unit test failures from the previous run looked unrelated, fyi.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14132
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62394/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14132
**[Test build #62394 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62394/consoleFull)**
for PR 14132 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14132
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/14226
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62389/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14226
**[Test build #62389 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62389/consoleFull)**
for PR 14226 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14226
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/13526
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/13526
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62388/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14225
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62387/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13526
**[Test build #62388 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62388/consoleFull)**
for PR 13526 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14225
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/14225
**[Test build #62387 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62387/consoleFull)**
for PR 14225 at commit
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/14201
I think I remember now why I asked for the checks to be removed before (I
was thinking of mimicking the PB behavior, in that calling `redirectOutput`
after `redirectToLog` would disable
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14201#discussion_r71050921
--- Diff:
launcher/src/main/java/org/apache/spark/launcher/SparkLauncher.java ---
@@ -455,6 +553,29 @@ private ProcessBuilder createBuilder() {
for
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14201#discussion_r71050862
--- Diff:
launcher/src/main/java/org/apache/spark/launcher/SparkLauncher.java ---
@@ -455,6 +553,29 @@ private ProcessBuilder createBuilder() {
for
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14201#discussion_r71050405
--- Diff:
launcher/src/main/java/org/apache/spark/launcher/SparkLauncher.java ---
@@ -455,6 +553,29 @@ private ProcessBuilder createBuilder() {
for
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14201#discussion_r71050389
--- Diff:
launcher/src/main/java/org/apache/spark/launcher/SparkLauncher.java ---
@@ -455,6 +553,29 @@ private ProcessBuilder createBuilder() {
for
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Ah, it's not always possible. When `BroadcastHint` is ignored and gone away
in some cases, we can not restore that.
In this PR, I will consider only the existing `BroadcastHint` case.
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14201#discussion_r71050089
--- Diff:
launcher/src/main/java/org/apache/spark/launcher/ChildProcAppHandle.java ---
@@ -127,7 +124,7 @@ String getSecret() {
void
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14201#discussion_r71050048
--- Diff:
core/src/test/java/org/apache/spark/launcher/SparkLauncherSuite.java ---
@@ -85,14 +91,69 @@ public void testSparkArgumentHandling() throws
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14201#discussion_r71049986
--- Diff:
core/src/test/java/org/apache/spark/launcher/SparkLauncherSuite.java ---
@@ -85,14 +91,69 @@ public void testSparkArgumentHandling() throws
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14201#discussion_r71049971
--- Diff:
core/src/test/java/org/apache/spark/launcher/SparkLauncherSuite.java ---
@@ -85,14 +91,69 @@ public void testSparkArgumentHandling() throws
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14201#discussion_r71049864
--- Diff:
core/src/test/java/org/apache/spark/launcher/SparkLauncherSuite.java ---
@@ -40,10 +41,15 @@
private static final Logger LOG =
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/14132
Oh, @rxin .
Since the position of `BroadcastHint` is different from the original, we
can not figure out the exact SELECT from the multiple SELECT candidates. I'm
trying to attach to the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14132
**[Test build #62394 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62394/consoleFull)**
for PR 14132 at commit
1 - 100 of 382 matches
Mail list logo
