Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14731#discussion_r83490975
--- Diff: docs/streaming-programming-guide.md ---
@@ -644,17 +644,90 @@ methods for creating DStreams from files as input
sources.
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14731#discussion_r83491041
--- Diff: docs/streaming-programming-guide.md ---
@@ -644,17 +644,90 @@ methods for creating DStreams from files as input
sources.
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/14731#discussion_r83491136
--- Diff: docs/streaming-programming-guide.md ---
@@ -644,17 +644,90 @@ methods for creating DStreams from files as input
sources.
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15475
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/15475
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66971/
Test PASSed.
---
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/15489#discussion_r83495403
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/SQLQuerySuite.scala
---
@@ -1106,6 +1106,30 @@ class SQLQuerySuite extends QueryTest with
Github user sitalkedia commented on the issue:
https://github.com/apache/spark/pull/15408
jenkins 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
Github user falaki commented on the issue:
https://github.com/apache/spark/pull/15421
@felixcheung and @shivaram AppVeyor test that @HyukjinKwon kicked passed
and jenkins passed too. Do you think this is ready?
---
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/15475
**[Test build #66979 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66979/consoleFull)**
for PR 15475 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15493
**[Test build #66981 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66981/consoleFull)**
for PR 15493 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15492
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/15398
**[Test build #66974 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66974/consoleFull)**
for PR 15398 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15490
**[Test build #66976 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66976/consoleFull)**
for PR 15490 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15490
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66976/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15490
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/15398
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66974/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15398
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/15493
**[Test build #66982 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66982/consoleFull)**
for PR 15493 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15492
**[Test build #66983 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66983/consoleFull)**
for PR 15492 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15492
**[Test build #66983 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66983/consoleFull)**
for PR 15492 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15492
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66983/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15492
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15190
It sounds like the other merged PRs made a change and impact your code.
Please resolve it. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/15421
@felixcheung I rebuild clean image and use the test case on JIRA. Still
fails.
> df <- data.frame(Date = as.Date(c(rep("2016-01-10", 10), "NA", "NA")), id
= 1:12)
>
>
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/15490
Jenkins, 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
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15190
Yea. Looks like so. No worries. Let's get it tested again.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15490
**[Test build #66985 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66985/consoleFull)**
for PR 15490 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15492
**[Test build #66984 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66984/consoleFull)**
for PR 15492 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15492
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66984/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15492
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/15492
**[Test build #66986 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66986/consoleFull)**
for PR 15492 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15489
**[Test build #66975 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66975/consoleFull)**
for PR 15489 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15489
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66975/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15489
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 ericl commented on the issue:
https://github.com/apache/spark/pull/14690
> My main concern is that, the new FileCatalog class hierarchy is really
complex now. Can we simplify it a little? or at least let's put a class
hierarchy chart(or text explanation) in PR description
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15421
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 so, or
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/15494
[SPARK-17947] [SQL] Add Doc and Comment about spark.sql.debug
### What changes were proposed in this pull request?
Just document the impact of `spark.sql.debug`:
When enabling the
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15489
Thanks! Merging to master and branch 2.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user falaki commented on the issue:
https://github.com/apache/spark/pull/15421
@wandjenkins yes, I think there must be some non-standard issue on your
system. I tested on Mac and Linux with different version of R and passed the
test case.
---
If your project is set up for
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/14690
btw, what's the parquet log redirection issue? I don't see anything unusual
in spark shell.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15494
**[Test build #66987 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66987/consoleFull)**
for PR 15494 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15421
**[Test build #66988 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66988/consoleFull)**
for PR 15421 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15489
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15475
**[Test build #66979 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66979/consoleFull)**
for PR 15475 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15459
**[Test build #66989 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66989/consoleFull)**
for PR 15459 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15475
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66979/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15408
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/15408
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66972/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15338
**[Test build #66969 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66969/consoleFull)**
for PR 15338 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15416
**[Test build #66970 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66970/consoleFull)**
for PR 15416 at commit
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/15488
Merged into master. 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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15408
**[Test build #66978 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66978/consoleFull)**
for PR 15408 at commit
Github user sethah commented on the issue:
https://github.com/apache/spark/pull/14547
A few observations:
* Before this patch, users could not set an impurity (in fact, if you call
`getImpurity` on a gbt classifier it returns "gini", which is not true. Seems
an unrelated
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15458#discussion_r83496528
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -915,4 +915,9 @@ object StaticSQLConf {
.internal()
Github user andrewor14 commented on the issue:
https://github.com/apache/spark/pull/15410
We shouldn't display file names but we should display application names and
IDs, something the user understands. We don't have to do that as part of this
issue.
---
If your project is set up
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15190
I am reverting this patch. Sorry.
---
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 marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/14553#discussion_r82297835
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/socket.scala
---
@@ -92,21 +105,64 @@ class TextSocketSource(host: String,
GitHub user srinathshankar opened a pull request:
https://github.com/apache/spark/pull/15493
[SPARK-17946][PYSPARK] Python crossJoin API similar to Scala
## What changes were proposed in this pull request?
Add a crossJoin function to the DataFrame API similar to that in
Github user srinathshankar commented on the issue:
https://github.com/apache/spark/pull/15493
cc @sameeragarwal @hvanhovell @davies @JoshRosen
---
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/15493
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/15493
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66981/
Test FAILed.
---
Github user wangmiao1981 commented on the issue:
https://github.com/apache/spark/pull/15421
@felixcheung Yes. I think I missed `vector` in the above example. I am
building on clean checkout and test again. Thanks!
---
If your project is set up for it, you can reply to this email and
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/15488
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15190
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15190
Merging to master! 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15488
---
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 ericl commented on the issue:
https://github.com/apache/spark/pull/15475
Jenkins test this please
On Fri, Oct 14, 2016, 1:15 PM UCB AMPLab wrote:
> Test PASSed.
> Refer to this link for build results (access rights to CI
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/15492
[DO NOT MERGE][TEST] Testing flakiness of StreamingQueryListener
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdas/spark metrics-flaky-test
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/15410
@andrewor14 I plan to address that in another issue soon (see by end of the
month) as soon as I have time. Fixing how the History Server loads has been
coming up in a lot of PRs lately.
---
If
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/14690
https://github.com/VideoAmp/spark-public/pull/7
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15190
Reverted
---
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 dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/15190
@yhuai very sorry Yin.. Let me look what happened here.. Is there a way to
open this pull request ? or i need to open a new one ?
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15493
**[Test build #66981 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66981/consoleFull)**
for PR 15493 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15492
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66980/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15408
**[Test build #66972 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66972/consoleFull)**
for PR 15408 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15416
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/15416
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66970/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15475
**[Test build #66971 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66971/consoleFull)**
for PR 15475 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15338
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/15338
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66969/
Test PASSed.
---
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/15190
---
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 dilipbiswal commented on the issue:
https://github.com/apache/spark/pull/15190
Thank you @yhuai @gatorsmile @cloud-fan @viirya @dafrista
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15492
**[Test build #66980 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66980/consoleFull)**
for PR 15492 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/15399
Hi, @rxin or @liancheng .
Could you review this PR when you have some time?
---
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 yhuai commented on the issue:
https://github.com/apache/spark/pull/15489
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 yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/15489#discussion_r83500257
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/SQLQuerySuite.scala
---
@@ -1106,6 +1106,30 @@ class SQLQuerySuite extends QueryTest with
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/15190
Seems this breaks the build.
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/job/spark-master-compile-sbt-scala-2.10/2843/console
---
If your project is set up for it, you can reply
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15398
Sounds like a good idea. It doesn't need to be in this PR though ...
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15398
@jodersky Please follow @rxin 's suggestion and submit a separate PR to
support it. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15475
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 falaki commented on the issue:
https://github.com/apache/spark/pull/15471
@felixcheung that is a good suggestion. I will try to use a single constant.
I changed the label to WIP because something is still timing out the
connection in my tests. Maybe very long timeouts
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14690
We can also merge this first and then do clean-ups next week BTW.
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15434
cc @yhuai
---
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 jodersky commented on the issue:
https://github.com/apache/spark/pull/15338
You raise a good point about having to commit to support environment
variables in future versions. A command-line option would be preferable
---
If your project is set up for it, you can reply to
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15434
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/9
**[Test build #66991 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66991/consoleFull)**
for PR 9 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15434
**[Test build #66990 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66990/consoleFull)**
for PR 15434 at commit
Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/13780
Sorry for the delay. I'm going to merge this to master. I'll update the
since versions while merging. Thanks for working on this!
---
If your project is set up for it, you can reply to this
Github user mallman commented on the issue:
https://github.com/apache/spark/pull/14690
I just pushed the rebase. It was really hairy, but I tried hard to ensure I
got essentially all three branches' changes in.
---
If your project is set up for it, you can reply to this email and
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15398#discussion_r83509641
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/expressions/RegexpExpressionsSuite.scala
---
@@ -74,6 +107,31 @@ class
1 - 100 of 530 matches
Mail list logo