Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208175823
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208175822
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208175816
**[Test build #55508 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55508/consoleFull)**
for PR 12067 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208175668
**[Test build #55508 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55508/consoleFull)**
for PR 12067 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12267#issuecomment-208173217
**[Test build #55507 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55507/consoleFull)**
for PR 12267 at commit
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59156009
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/NonNullableBinaryComparisonSimplificationSuite.scala
---
@@ -0,0 +1,99
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59155908
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/NonNullableBinaryComparisonSimplificationSuite.scala
---
@@ -0,0 +1,99
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208171753
**[Test build #55506 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55506/consoleFull)**
for PR 12067 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208171756
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208171754
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208171517
**[Test build #55506 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55506/consoleFull)**
for PR 12067 at commit
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59155788
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -787,6 +788,28 @@ object BooleanSimplification
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12267#issuecomment-208170041
Thank you for *deep review*, @cloud-fan . :)
I changed PR according to the one comment first.
For the others, I asked some questions to understand more
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59155584
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/NonNullableBinaryComparisonSimplificationSuite.scala
---
@@ -0,0 +1,99 @@
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12267#issuecomment-208169438
**[Test build #55505 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55505/consoleFull)**
for PR 12267 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59155488
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -787,6 +788,28 @@ object BooleanSimplification
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12138#issuecomment-208168423
Yea, and in this PR we use `NamedExpression` to avoid re-using child's
output, which should work. My proposal is that, we can use placeholders(maybe
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59155308
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/NonNullableBinaryComparisonSimplificationSuite.scala
---
@@ -0,0 +1,99
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59154875
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -787,6 +788,28 @@ object BooleanSimplification
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12292#issuecomment-208165851
**[Test build #55504 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55504/consoleFull)**
for PR 12292 at commit
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/12292
[SPARK-14520][SQL] Use correct return type in VectorizedParquetInputFormat
## What changes were proposed in this pull request?
JIRA: https://issues.apache.org/jira/browse/SPARK-14520
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12292#issuecomment-208164442
cc @nongli
---
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 dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59154150
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/NonNullableBinaryComparisonSimplificationSuite.scala
---
@@ -0,0 +1,99
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59154120
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -787,6 +788,28 @@ object BooleanSimplification
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12259#issuecomment-208160483
**[Test build #55503 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55503/consoleFull)**
for PR 12259 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12259#issuecomment-208159753
cc @marmbrus @yhuai @rxin
---
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
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12138#issuecomment-208158392
@cloud-fan Thanks for comment.
The problem is we re-use child's output as `Expand`s output. We will
create new attributes in `Expand` because `Expand` actually
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208152087
I can reproduce it 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
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/9565#issuecomment-208151820
hmm. We can't remove non code-generated version of ScalaUDF as any
InterpretedProjection with udf will fail...
---
If your project is set up for it, you can reply to
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208151740
Thank you for your investigation! Sorry, just came back. Will follow your
idea to fix the issue.
---
If your project is set up for it, you can reply to this
Github user tedyu commented on a diff in the pull request:
https://github.com/apache/spark/pull/12279#discussion_r59152083
--- Diff:
sql/core/src/main/java/org/apache/spark/sql/execution/datasources/parquet/VectorizedColumnReader.java
---
@@ -200,8 +150,26 @@ void readBatch(int
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12260#issuecomment-208151177
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12260#issuecomment-208151178
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12260#issuecomment-208151080
**[Test build #55498 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55498/consoleFull)**
for PR 12260 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208150854
For now, we can avoid of dropping `current_database` in
`SessionCatalog.reset`.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12284
---
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 yhuai commented on the pull request:
https://github.com/apache/spark/pull/12284#issuecomment-208148952
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
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208148091
You can reproduce it by calling `test-only *HiveDDLSuite *HiveQuerySuite`.
Yea, it is indeed the problem of reset.
---
If your project is set up for it, you can reply
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208147970
`current_database` is special because it is registered in HiveContext. So,
it is not tracked FunctionRegistry.builtIn. I think `HiveDDLSuite` drops this
function by
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9565#issuecomment-208147721
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9565#issuecomment-208147682
**[Test build #55502 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55502/consoleFull)**
for PR 9565 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9565#issuecomment-208147724
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-208147504
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-208147505
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-208147395
**[Test build #55497 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55497/consoleFull)**
for PR 11301 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9565#issuecomment-208147148
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9565#issuecomment-208147147
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9565#issuecomment-208147121
**[Test build #55501 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55501/consoleFull)**
for PR 9565 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11550#issuecomment-208145793
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11550#issuecomment-208145794
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11550#issuecomment-208145667
**[Test build #55496 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55496/consoleFull)**
for PR 11550 at commit
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/12207#issuecomment-208142363
ping @jkbradley @MLnick
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9565#issuecomment-208138899
**[Test build #55502 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55502/consoleFull)**
for PR 9565 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9565#issuecomment-208136271
**[Test build #55501 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55501/consoleFull)**
for PR 9565 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12284#issuecomment-208131830
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12284#issuecomment-208131833
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208131549
**[Test build #55499 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55499/consoleFull)**
for PR 12067 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12284#issuecomment-208131432
**[Test build #55495 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55495/consoleFull)**
for PR 12284 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208131587
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208131584
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
Github user oliverpierson commented on the pull request:
https://github.com/apache/spark/pull/11553#issuecomment-208130852
scalastyle check is failing because the `@see` link on [line
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11553#issuecomment-208130405
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11553#issuecomment-208130400
**[Test build #55500 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55500/consoleFull)**
for PR 11553 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11553#issuecomment-208130403
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11553#issuecomment-208129954
**[Test build #55500 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55500/consoleFull)**
for PR 11553 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12067#issuecomment-208129959
**[Test build #55499 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55499/consoleFull)**
for PR 12067 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12260#issuecomment-208122361
**[Test build #55498 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55498/consoleFull)**
for PR 12260 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12268#discussion_r59148216
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/csv/CSVParserSuite.scala
---
@@ -1,125 +0,0 @@
-/*
- * Licensed to
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59147914
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/NonNullableBinaryComparisonSimplificationSuite.scala
---
@@ -0,0 +1,99 @@
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11301#issuecomment-208119382
**[Test build #55497 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55497/consoleFull)**
for PR 11301 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11550#issuecomment-208119378
**[Test build #55496 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55496/consoleFull)**
for PR 11550 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208119322
Unable to find it. : (
Still unable to reproduce it in my local environment. Will upload a code
change to print out a message when we adding Hive UDF
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11868#issuecomment-208118258
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208118294
Is there any chance that the original current_database is not in the
function registry when we call current_database?
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11868#issuecomment-208118250
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11868#issuecomment-208117787
**[Test build #55494 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55494/consoleFull)**
for PR 11868 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12290#issuecomment-208117591
Other examples in
`http://spark.apache.org/docs/latest/sql-programming-guide.html` also shows
`long`.
By the way, as you requested, I cleanly synced,
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208116409
It should be caused by `lookupFunction` in `HiveSessionCatalog`. Based on
Hive's
[UDF](https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF), it
has
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208114035
It does not sound right. It should be related to `HiveSessionCatalog`.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12290#issuecomment-208113694
Sure, I verified on master branch.
---
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208112300
Let me remove `import org.apache.hadoop.fs.Path` and make another try.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59146548
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/NonNullableBinaryComparisonSimplificationSuite.scala
---
@@ -0,0 +1,99 @@
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208109405
I guess something is wrong in the function resolution in `Analyzer`.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12267#discussion_r59146455
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -787,6 +788,28 @@ object BooleanSimplification
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208108264
No clue... In my local environment, it is not using Hive's UDF.
```
== Parsed Logical Plan ==
'Project [unresolvedalias('current_database(), None)]
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208107091
Accidentally, deleted the previous post.
```
== Parsed Logical Plan ==
'Project [unresolvedalias('current_database(), None)]
+- OneRowRelation$
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208106887
This is great! Why are we using Hive's udf?
---
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 gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208106388
```
== Parsed Logical Plan ==
'Project [unresolvedalias('current_database(), None)]
+- OneRowRelation$
== Analyzed Logical Plan ==
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12284#issuecomment-208106314
**[Test build #55495 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55495/consoleFull)**
for PR 12284 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12289
---
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 pull request:
https://github.com/apache/spark/pull/12289#issuecomment-208105809
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12289#issuecomment-208105808
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12289#issuecomment-208105709
**[Test build #55491 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55491/consoleFull)**
for PR 12289 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208105027
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208105038
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12081#issuecomment-208104908
**[Test build #55492 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55492/consoleFull)**
for PR 12081 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/12289#discussion_r59145830
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala
---
@@ -374,8 +373,9 @@ private[execution] final class
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12289#discussion_r59145739
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala
---
@@ -374,8 +373,9 @@ private[execution] final class
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12290#issuecomment-208104221
Did you verify this is what is printed if you run the example? then that
makes sense.
---
If your project is set up for it, you can reply to this email and have your
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/11868#discussion_r59145545
--- Diff: sql/catalyst/src/main/scala/org/apache/spark/sql/Row.scala ---
@@ -402,11 +402,13 @@ trait Row extends Serializable {
return
1 - 100 of 272 matches
Mail list logo
