Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/14712
@gatorsmial, do you mean `COLUMN_STATS_ACCURATE` exists in any table's
properties?
---
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 cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14746#discussion_r76511709
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkSqlParser.scala ---
@@ -1294,20 +1296,29 @@ class SparkSqlAstBuilder(conf: SQLConf) e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14842
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64514/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14842
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14842
**[Test build #64514 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64514/consoleFull)**
for PR 14842 at commit
[`760e890`](https://github.com/apache/spark/commit/
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14788#discussion_r76511635
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeExpressions.scala
---
@@ -916,21 +953,26 @@ case class ToDate(chil
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14746
**[Test build #64526 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64526/consoleFull)**
for PR 14746 at commit
[`d84db62`](https://github.com/apache/spark/commit/d
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14788#discussion_r76511621
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/datetimeExpressions.scala
---
@@ -583,20 +602,25 @@ case class FromUnixTim
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14788#discussion_r76511591
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala
---
@@ -748,6 +764,14 @@ object DateTimeUtils {
}
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14823
**[Test build #64525 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64525/consoleFull)**
for PR 14823 at commit
[`0e9b3d2`](https://github.com/apache/spark/commit/0
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14788
**[Test build #64524 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64524/consoleFull)**
for PR 14788 at commit
[`eee40b8`](https://github.com/apache/spark/commit/e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14788
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64523/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14788
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14836
**[Test build #64522 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64522/consoleFull)**
for PR 14836 at commit
[`217ff7a`](https://github.com/apache/spark/commit/2
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/14788#discussion_r76511384
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala
---
@@ -845,6 +922,10 @@ object DateTimeUtils {
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14848
**[Test build #64521 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64521/consoleFull)**
for PR 14848 at commit
[`247e852`](https://github.com/apache/spark/commit/2
GitHub user keypointt opened a pull request:
https://github.com/apache/spark/pull/14848
[SPARK-17276][Core][Test] Stop env params output on Jenkins job page
https://issues.apache.org/jira/browse/SPARK-17276
## What changes were proposed in this pull request?
When tr
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14847
**[Test build #64520 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64520/consoleFull)**
for PR 14847 at commit
[`ccac04f`](https://github.com/apache/spark/commit/c
GitHub user viirya opened a pull request:
https://github.com/apache/spark/pull/14847
[SPARK-17254][SQL] Filter can stop when the condition is false if the child
output is sorted
## What changes were proposed in this pull request?
From
https://issues.apache.org/ji
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14846
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 feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14846
**[Test build #64519 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64519/consoleFull)**
for PR 14846 at commit
[`1e08294`](https://github.com/apache/spark/commit/1
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14846
Hopefully this one can be merged in 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 featu
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/14846
[SPARK-17274][SQL] Move join optimizer rules into a separate file
## What changes were proposed in this pull request?
As part of breaking Optimizer.scala apart, this patch moves various join
rules
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14845
**[Test build #64518 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64518/consoleFull)**
for PR 14845 at commit
[`de2e35b`](https://github.com/apache/spark/commit/d
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14845
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 feature
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14844
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 feature
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/14845
[SPARK-17273][SQL] Move expression optimizer rules into a separate file
## What changes were proposed in this pull request?
As part of breaking Optimizer.scala apart, this patch moves various
subq
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/14746#discussion_r76510475
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/views.scala ---
@@ -105,7 +105,13 @@ case class CreateViewCommand(
}
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/14841
cc'ing @rxin and @hvanhovell for review
---
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/14844
**[Test build #64517 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64517/consoleFull)**
for PR 14844 at commit
[`c18dbad`](https://github.com/apache/spark/commit/c
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/14844
[SPARK-17272][SQL] Move subquery optimizer rules into its own file
## What changes were proposed in this pull request?
As part of breaking Optimizer.scala apart, this patch moves various
subquery
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14836
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14836
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64513/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14836
**[Test build #64513 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64513/consoleFull)**
for PR 14836 at commit
[`a5e1db3`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14843
**[Test build #64516 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64516/consoleFull)**
for PR 14843 at commit
[`d2c2474`](https://github.com/apache/spark/commit/d
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/14843
[SPARK-17270][SQL] Move object optimization rules into its own file
(branch-2.0)
## What changes were proposed in this pull request?
As part of breaking Optimizer.scala apart, this patch moves var
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14841
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64512/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14841
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14841
**[Test build #64512 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64512/consoleFull)**
for PR 14841 at commit
[`7192418`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14838
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64515/
Test FAILed.
---
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14838
---
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 ena
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14838
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14840
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64511/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14840
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14840
**[Test build #64511 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64511/consoleFull)**
for PR 14840 at commit
[`d79d801`](https://github.com/apache/spark/commit/
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14839
OK I will submit a separate one.
---
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/14839
Seems the conflicts are caused by
https://github.com/apache/spark/commit/d063898bebaaf4ec2aad24c3ac70aabdbf97a190#diff-a636a87d8843eeccca90140be91d4faf.
---
If your project is set up for it, you can
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14839
hmm. There are conflicts in 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
enabl
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14839
---
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 ena
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14838
LGTM. 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
enabl
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14839
LGTM. 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
enabl
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14842
**[Test build #64514 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64514/consoleFull)**
for PR 14842 at commit
[`760e890`](https://github.com/apache/spark/commit/7
Github user xwu0226 commented on the issue:
https://github.com/apache/spark/pull/14842
@hvanhovell It turns out that this involves the whole new feature that
supports NULLS FIRST|LAST in ORDER BY clause. Please help to see if the
implementation is in the right direction. Thanks!
---
GitHub user xwu0226 opened a pull request:
https://github.com/apache/spark/pull/14842
[SPARK-10747][SQL] Support NULS FIRST|LAST clause in ORDER BY
## What changes were proposed in this pull request?
Currently, ORDER BY clause returns nulls value according to sorting order
(ASC|
Github user JustinPihony commented on the issue:
https://github.com/apache/spark/pull/12601
@rxin I am sure you are busy, so if there is anybody else I can ping to
have this reviewed please let me know.
---
If your project is set up for it, you can reply to this email and have your
r
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14836
**[Test build #64513 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64513/consoleFull)**
for PR 14836 at commit
[`a5e1db3`](https://github.com/apache/spark/commit/a
Github user keypointt commented on the issue:
https://github.com/apache/spark/pull/14836
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 wi
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14841
**[Test build #64512 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64512/consoleFull)**
for PR 14841 at commit
[`7192418`](https://github.com/apache/spark/commit/7
Github user tejasapatil commented on the issue:
https://github.com/apache/spark/pull/14841
ok to test
---
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
GitHub user tejasapatil opened a pull request:
https://github.com/apache/spark/pull/14841
[SPARK-17271] [SQL] Planner adds un-necessary Sort even if child ordering
is semantically same as required ordering
## What changes were proposed in this pull request?
Jira : https://i
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14839
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64510/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14839
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14839
**[Test build #64510 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64510/consoleFull)**
for PR 14839 at commit
[`39d8a9e`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14838
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64509/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14838
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
e
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14840
I will cc you @hvanhovell . This is the backport of #14829.
---
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 n
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14838
**[Test build #64509 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64509/consoleFull)**
for PR 14838 at commit
[`063ddfb`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14840
**[Test build #64511 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64511/consoleFull)**
for PR 14840 at commit
[`d79d801`](https://github.com/apache/spark/commit/d
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/14840
[SPARK-16216][SQL][FOLLOWUP][BRANCH-2.0] Bacoport enabling timestamp type
tests for JSON and verify all unsupported types in CSV
## What changes were proposed in this pull request?
Thi
Github user QQshu1 commented on the issue:
https://github.com/apache/spark/pull/14835
I may have a question ,if I just have a application,and it is very large
.It also can't load it by this way. How to solve this kind of scene?
---
If your project is set up for it, you can reply to
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/14837
---
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 ena
Github user yhuai commented on the issue:
https://github.com/apache/spark/pull/14837
Thanks. I will merge this and watch the 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 does not have this featur
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14835
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14835
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64508/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14835
**[Test build #64508 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64508/consoleFull)**
for PR 14835 at commit
[`172dc56`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14832
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14832
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64507/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14832
**[Test build #64507 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64507/consoleFull)**
for PR 14832 at commit
[`4f2b272`](https://github.com/apache/spark/commit/
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/14746#discussion_r76508097
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/views.scala ---
@@ -105,7 +105,13 @@ case class CreateViewCommand(
}
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14836
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64504/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14836
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14836
**[Test build #64504 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64504/consoleFull)**
for PR 14836 at commit
[`70a751c`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14836
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14836
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64506/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14836
**[Test build #64506 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64506/consoleFull)**
for PR 14836 at commit
[`a5e1db3`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14837
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14837
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64505/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14837
**[Test build #64505 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64505/consoleFull)**
for PR 14837 at commit
[`6add905`](https://github.com/apache/spark/commit/
Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/14712
@cloud-fan did you see the
[comment](https://github.com/apache/spark/pull/14712#discussion_r75540560) by
@gatorsmile ?
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14839
**[Test build #64510 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64510/consoleFull)**
for PR 14839 at commit
[`39d8a9e`](https://github.com/apache/spark/commit/3
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/14839
[SPARK-17270][SQL] Move object optimization rules into its own file
## What changes were proposed in this pull request?
As part of breaking Optimizer.scala apart, this patch moves various Dataset
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14838
**[Test build #64509 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/64509/consoleFull)**
for PR 14838 at commit
[`063ddfb`](https://github.com/apache/spark/commit/0
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14839
cc @cloud-fan
---
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 th
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/14838#discussion_r76506795
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/finishAnalysis.scala
---
@@ -0,0 +1,65 @@
+/*
+ * Licensed to the Apache
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14838
cc @srinathshankar
---
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 rxin opened a pull request:
https://github.com/apache/spark/pull/14838
[SPARK-17269][SQL] Move finish analysis optimization stage into its own file
## What changes were proposed in this pull request?
As part of breaking Optimizer.scala apart, this patch moves various
Github user holdenk commented on a diff in the pull request:
https://github.com/apache/spark/pull/14691#discussion_r76505266
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/DataStreamWriter.scala
---
@@ -123,12 +124,30 @@ final class DataStreamWriter[T] private[sq
Github user frreiss commented on a diff in the pull request:
https://github.com/apache/spark/pull/14691#discussion_r76505064
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/DataStreamWriter.scala
---
@@ -123,12 +124,30 @@ final class DataStreamWriter[T] private[sq
Github user frreiss commented on a diff in the pull request:
https://github.com/apache/spark/pull/14691#discussion_r76504239
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/streaming/DataStreamWriter.scala
---
@@ -123,12 +124,30 @@ final class DataStreamWriter[T] private[sq
Github user keypointt commented on the issue:
https://github.com/apache/spark/pull/14836
I just noticed that there are many other places where 'PropSpec' style is
used `with Matchers`, while I guess spark project is mainly using `FunSuite`
sylte
---
If your project is set up for it,
1 - 100 of 477 matches
Mail list logo
