Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63540 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63540/consoleFull)**
for PR 14568 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63540/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
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/14568
**[Test build #63540 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63540/consoleFull)**
for PR 14568 at commit
Github user avulanov commented on the issue:
https://github.com/apache/spark/pull/13868
@srowen Could you give me a link to the log of the failed 2.0 build?
---
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/14581
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63538/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14581
**[Test build #63538 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63538/consoleFull)**
for PR 14581 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14581
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/14568
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/14568
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63539/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63539 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63539/consoleFull)**
for PR 14568 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12896
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63535/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63539 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63539/consoleFull)**
for PR 14568 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/12896
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/12896
**[Test build #63535 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63535/consoleFull)**
for PR 12896 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14567
**[Test build #63536 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63536/consoleFull)**
for PR 14567 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14581
OK
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14581
**[Test build #63538 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63538/consoleFull)**
for PR 14581 at commit
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13868
This didn't work in branch-2.0. I'm going to investigate briefly and almost
certainly revert.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user ash211 commented on the issue:
https://github.com/apache/spark/pull/14563
Agreed that it's better to avoid tiny PRs for typos where possible, though
when I'm doing something in the moment and encounter a typo I'd rather submit
at least _some_ PR rather than break my
Github user ash211 commented on the issue:
https://github.com/apache/spark/pull/14566
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 feature
enabled and wishes so, or if the
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63537/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14568
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/14568
**[Test build #63537 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63537/consoleFull)**
for PR 14568 at commit
GitHub user ash211 opened a pull request:
https://github.com/apache/spark/pull/14581
Correct example value for spark.ssl.YYY.XXX settings
Docs adjustment to:
- link to other relevant section of docs
- correct statement about the only value when actually other values are
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14159
**[Test build #3211 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3211/consoleFull)**
for PR 14159 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14568
**[Test build #63537 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63537/consoleFull)**
for PR 14568 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14397
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63529/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14397
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/14397
**[Test build #63529 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63529/consoleFull)**
for PR 14397 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/14452
Originally I use the analyzed logical plans to compare subqueries when
finding the subqueries with the same results. But I think that optimized plan
might be better because it should have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/12896
**[Test build #63535 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63535/consoleFull)**
for PR 12896 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/14452
@hvanhovell Got it. Thanks for the cue.
I think the thought is the same, to reuse the results of the plans wit same
results.
The performance gain of this PR is from the reuse of the
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14573#discussion_r74239358
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkPlan.scala ---
@@ -333,15 +333,14 @@ abstract class SparkPlan extends
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14546
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63528/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14546
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/14567
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63534/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14567
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/14567
**[Test build #63534 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63534/consoleFull)**
for PR 14567 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14546
**[Test build #63528 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63528/consoleFull)**
for PR 14546 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14534
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/14534
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63531/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14534
**[Test build #63531 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63531/consoleFull)**
for PR 14534 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14567
**[Test build #63534 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63534/consoleFull)**
for PR 14567 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14452
We reuse all exchanges (including shuffled ones), see this rule:
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/exchange/Exchange.scala#L69-L94
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14577
Hm, I also don't quite like this change, as it's kind of hackily rewriting
dates in Javascript. I am not sure this is correct, even. What does the Spark
job page do to format dates? Seems like it
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14567
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/14567
**[Test build #63533 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63533/consoleFull)**
for PR 14567 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14567
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63533/
Test FAILed.
---
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14564
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14567
**[Test build #63533 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63533/consoleFull)**
for PR 14567 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/13701
@davies Due to the accumulators for vectorized setting "true" and "false"
are with the same names "numRowGroups", the API looking for the accumulator
will return one among them. So the test becomes
Github user andreweduffy commented on the issue:
https://github.com/apache/spark/pull/14159
Yep, closing now
---
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 andreweduffy closed the pull request at:
https://github.com/apache/spark/pull/14159
---
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 srowen commented on the issue:
https://github.com/apache/spark/pull/14567
Jenkins add to whitelist
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14567
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 and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13701
**[Test build #63532 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63532/consoleFull)**
for PR 13701 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/14452
@hvanhovell Thanks for looking at this.
The first attempt of this PR is to address all `SubqueryAlias`. But looks
like we use `SubqueryAlias` plan in many places. To de-duplicating all of
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14546
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 srowen commented on the issue:
https://github.com/apache/spark/pull/13868
Merged to master, and to 2.0 after a weird conflict and then merge problem
(Github API isn't matching the status shown here?). I'll keep an eye on the
builds to make sure I did it right.
---
If
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14546
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63527/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14546
**[Test build #63527 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63527/consoleFull)**
for PR 14546 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14534
**[Test build #63531 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63531/consoleFull)**
for PR 14534 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14452
@viirya I have taken a look. It looks pretty cool what you are doing. One
question: why are you focussing on CTE's only? Shouldn't we look at any part of
the query tree?
The other thing
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14397
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/14555
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63530/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14555
**[Test build #63530 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63530/consoleFull)**
for PR 14555 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14555
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/14397
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63526/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14397
**[Test build #63526 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63526/consoleFull)**
for PR 14397 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14159
Ok :)... Could you close then?
---
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 Stibbons commented on the issue:
https://github.com/apache/spark/pull/14180
Rebased, without import reorg and editorconfig files. Still not fully
validated.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14102
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63525/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14102
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/14102
**[Test build #63525 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63525/consoleFull)**
for PR 14102 at commit
Github user andreweduffy commented on the issue:
https://github.com/apache/spark/pull/14159
Actually it appears that since this was opened, later PR #14450 fixes this.
Should be safe to close now.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14397
LGTM pending Jenkins.
---
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 hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14548
@davies this looks pretty good. I am very excited about the SparkPlan
clean-up!
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/14555
**[Test build #63530 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63530/consoleFull)**
for PR 14555 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14159
**[Test build #3211 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3211/consoleFull)**
for PR 14159 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14159
Could you open a JIRA or add the existing JIRA to the PR?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14159
@andreweduffy not much. I'll trigger a test.
@liancheng could you take a look at this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14548#discussion_r74228578
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/subquery.scala ---
@@ -17,42 +17,77 @@
package org.apache.spark.sql.execution
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14548#discussion_r74228609
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/subquery.scala ---
@@ -17,42 +17,77 @@
package org.apache.spark.sql.execution
Github user MLnick commented on the issue:
https://github.com/apache/spark/pull/14579
cc @nchammas @holdenk @rxin
**Note:**
This is implemented by adding the `__enter__` and `__exit__` methods to
RDD/DataFrame directly. This allows some potentially weird stuff, such as
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14102
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/14102
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63522/
Test PASSed.
---
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14548#discussion_r74228083
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkPlan.scala ---
@@ -165,21 +161,10 @@ abstract class SparkPlan extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14102
**[Test build #63522 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63522/consoleFull)**
for PR 14102 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14397
**[Test build #63529 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63529/consoleFull)**
for PR 14397 at commit
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/14397#discussion_r74227100
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -125,21 +125,23 @@ class Analyzer(
object
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14548#discussion_r74226982
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkPlan.scala ---
@@ -142,21 +142,17 @@ abstract class SparkPlan extends
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14397#discussion_r74226825
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -125,21 +125,23 @@ class Analyzer(
object
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/14397#discussion_r74226355
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -125,21 +125,23 @@ class Analyzer(
object
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14546
**[Test build #63528 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/63528/consoleFull)**
for PR 14546 at commit
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14548#discussion_r74226191
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/ui/SparkPlanGraph.scala
---
@@ -99,7 +99,11 @@ private[sql] object SparkPlanGraph {
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14548#discussion_r74226144
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/subquery.scala ---
@@ -68,14 +103,90 @@ case class ScalarSubquery(
}
/**
Github user Stibbons commented on the issue:
https://github.com/apache/spark/pull/14567
Done
---
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 hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14397#discussion_r74225867
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -125,22 +125,20 @@ class Analyzer(
object
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/14397#discussion_r74225717
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -125,21 +125,23 @@ class Analyzer(
object
401 - 500 of 724 matches
Mail list logo
