Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16068#discussion_r90752814
--- Diff:
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveUDFSuite.scala
---
@@ -487,6 +488,29 @@ class HiveUDFSuite extends QueryTest
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16128
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69609/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16128
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/16128
**[Test build #69609 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69609/consoleFull)**
for PR 16128 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15795
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/15795
**[Test build #69613 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69613/consoleFull)**
for PR 15795 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15795
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69613/
Test PASSed.
---
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16068
We have a rule
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15795
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69612/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16098
**[Test build #69614 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69614/consoleFull)**
for PR 16098 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15795
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/15795
**[Test build #69612 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69612/consoleFull)**
for PR 15795 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16098
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15795
**[Test build #69613 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69613/consoleFull)**
for PR 15795 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15795
**[Test build #69612 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69612/consoleFull)**
for PR 15795 at commit
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/16030
Looks great! Thanks so much @maropu . @tdas or @liancheng would you mind
taking a last look and possibly merging to 2.1?
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16030
**[Test build #69611 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69611/consoleFull)**
for PR 16030 at commit
Github user eyalfa commented on the issue:
https://github.com/apache/spark/pull/16043
Will do.
I'm currently focusing on a functional issue with simplifying operations on
createMap, I'll take care of these while on it.
On Dec 2, 2016 11:09 PM, "Xiao Li"
Github user maropu commented on a diff in the pull request:
https://github.com/apache/spark/pull/16030#discussion_r90752283
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala
---
@@ -189,7 +189,15 @@ case class DataSource(
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16128#discussion_r90752217
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/streaming/OffsetSeqLogSuite.scala
---
@@ -60,4 +60,39 @@ class OffsetSeqLogSuite extends
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16125
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69607/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16125
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/16125
**[Test build #69607 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69607/consoleFull)**
for PR 16125 at commit
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/16030
@brkyvz yea, I think so, but the issue of column ordering seems to be out
of scope in this original ticket. So, why don't we open a new jira and discuss
there?
---
If your project is set up for
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/16030
That is something I tried to standardize. I think we should standardize it,
otherwise it is very confusing. I think it's the right thing to do. I just
don't want people's production jobs
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16120
**[Test build #69610 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69610/consoleFull)**
for PR 16120 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16120
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69608/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16120
**[Test build #69608 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69608/consoleFull)**
for PR 16120 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16120
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 jkbradley commented on the issue:
https://github.com/apache/spark/pull/15795
I found myself wanting to make a number of tiny comments, so I thought it'd
be easier to send a PR. Could you please take a look at this one?
Thanks!
---
If your project is set up for it,
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16113#discussion_r90751494
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/OffsetSeq.scala
---
@@ -54,6 +61,26 @@ object OffsetSeq {
* `nulls` in the
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/15813#discussion_r90751405
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/CSVFileFormat.scala
---
@@ -173,51 +179,37 @@ class CSVFileFormat extends
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16128
**[Test build #69609 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69609/consoleFull)**
for PR 16128 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16098
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69606/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16098
**[Test build #69606 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69606/consoleFull)**
for PR 16098 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16098
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 rxin commented on the issue:
https://github.com/apache/spark/pull/15923
cc @zsxwing @JoshRosen does this look good?
---
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/15813
---
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 dongjoon-hyun closed the pull request at:
https://github.com/apache/spark/pull/16021
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16021
Thank you all so much for giving your attentions and opinions here.
I asked the one which is not allowed here. Please refer #16127 for more
details, too.
I'm closing this
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15813
Merging in master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16127
I will close this 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
Github user dongjoon-hyun closed the pull request at:
https://github.com/apache/spark/pull/16127
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16127
I see. If then, it's my fault.
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16127
I didn't actually look at the content. I thought they were bug fixes and as
a result said we should backport them. The title and description of the
original pr implied they were bug fixes.
---
If
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16126
---
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 rxin commented on the issue:
https://github.com/apache/spark/pull/16126
Merging in master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16126
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69599/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16126
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/16126
**[Test build #69599 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69599/consoleFull)**
for PR 16126 at commit
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/16090
Seems like the caching broke a bunch of tests. I'll take a look at this
again tomorrow.
On Fri, Dec 2, 2016, 7:49 PM UCB AMPLab wrote:
> Test FAILed.
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16092
**[Test build #3465 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3465/consoleFull)**
for PR 16092 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16120
**[Test build #69608 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69608/consoleFull)**
for PR 16120 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/15620
LGTM and cc @cloud-fan for another check.
---
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/16125
**[Test build #69607 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69607/consoleFull)**
for PR 16125 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16090
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/16090
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69600/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16090
**[Test build #69600 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69600/consoleFull)**
for PR 16090 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16109
**[Test build #3462 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3462/consoleFull)**
for PR 16109 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16109
**[Test build #3464 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3464/consoleFull)**
for PR 16109 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16109
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/16109
**[Test build #3463 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3463/consoleFull)**
for PR 16109 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16109
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69598/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16109
**[Test build #69598 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69598/consoleFull)**
for PR 16109 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16127
Oh, 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 feature
enabled and wishes so,
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16127
Just let me know if this is not what you expect. I will close this and
#16021 immediately as I mentioned before.
We just make a mistake one commit hopefully.
---
If your project is set
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16127
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/16127
**[Test build #69604 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69604/consoleFull)**
for PR 16127 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16127
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69604/
Test FAILed.
---
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16127
The my comment was
> Hi, @rxin , @gatorsmile , @hvanhovell , @srowen .
> Could you give some opinion? What I hoped here is having these 6 commits
in branch-1.6.
> But, if backports
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16094
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69602/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16094
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16127
The solution of the bug fix was the feature of predicate pushdown to
PostgreSQL in latest branch.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16094
**[Test build #69602 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69602/consoleFull)**
for PR 16094 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16127
Ur, @rxin . We talked on #16021 about these 6 commits.
You delegated this review work to @gatorsmile , didn't you?
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16098
**[Test build #69606 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69606/consoleFull)**
for PR 16098 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16098
It seems the failed test is not related and passed in my local.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16098
retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16109
**[Test build #3461 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3461/consoleFull)**
for PR 16109 at commit
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/16127
Why are we adding features? I thought they were bug fixes.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16128
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69605/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16128
**[Test build #69605 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69605/consoleFull)**
for PR 16128 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16128
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/16128
**[Test build #69605 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69605/consoleFull)**
for PR 16128 at commit
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/16128
[SPARK-18671][SS] Added tests to ensure stability of that all Structured
Streaming log formats
## What changes were proposed in this pull request?
To be able to restart StreamingQueries
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16127
**[Test build #69604 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69604/consoleFull)**
for PR 16127 at commit
Github user dongjoon-hyun commented on a diff in the pull request:
https://github.com/apache/spark/pull/16127#discussion_r90749070
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/jdbc/JDBCSuite.scala
---
@@ -180,12 +181,32 @@ class JDBCSuite extends SparkFunSuite
}
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16127
This is the second commit for #16021.
cc @gatorsmile .
---
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 dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/16127
[SPARK-12409][SPARK-12387][SPARK-12391][SQL][BACKPORT-1.6] Support
AND/OR/IN/LIKE push-down filters for JDBC
This is rework from #10386 and add more tests and LIKE push-down support.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16053
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/16053
**[Test build #69603 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69603/consoleFull)**
for PR 16053 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16053
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69603/
Test FAILed.
---
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/16090
cc @rxin please merge unless wenchen gets to it first
---
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 dongjoon-hyun closed the pull request at:
https://github.com/apache/spark/pull/16124
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/16124
Thank you! I'll close this and proceed to next.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16053
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69601/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16053
**[Test build #69601 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69601/consoleFull)**
for PR 16053 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16053
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 tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/16125#discussion_r90748623
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamingQuerySuite.scala
---
@@ -103,10 +103,12 @@ class StreamingQuerySuite extends
Github user shea-parkes commented on a diff in the pull request:
https://github.com/apache/spark/pull/16094#discussion_r90748611
--- Diff: python/pyspark/sql/column.py ---
@@ -298,19 +299,34 @@ def isin(self, *cols):
isNotNull = _unary_op("isNotNull", "True if the current
1 - 100 of 500 matches
Mail list logo