Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11596#issuecomment-194109656
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
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/11596#discussion_r55470961
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/SQLBuilder.scala ---
@@ -94,6 +94,12 @@ class SQLBuilder(logicalPlan: LogicalPlan,
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/11596#discussion_r55470832
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/SQLBuilder.scala ---
@@ -297,6 +303,60 @@ class SQLBuilder(logicalPlan: LogicalPlan,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11599#issuecomment-194108308
**[Test build #52721 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52721/consoleFull)**
for PR 11599 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11595#issuecomment-194108241
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/10821#issuecomment-194108311
**[Test build #52722 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52722/consoleFull)**
for PR 10821 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11595#issuecomment-194108242
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/11410#issuecomment-194108194
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/11410#issuecomment-194108195
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11576#issuecomment-194108153
Yea I think evenutally it might make sense -- but one problem is that it is
very expensive to detect this, especially when there are a very large number of
files, which
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11599#issuecomment-194108085
cc @marmbrus @cloud-fan @dilipbiswal
---
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/11595#issuecomment-194108125
**[Test build #52716 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52716/consoleFull)**
for PR 11595 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11410#issuecomment-194108071
**[Test build #52715 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52715/consoleFull)**
for PR 11410 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/11599
[SPARK-13763] [SQL] Remove Project when its projectList is Empty
What changes were proposed in this pull request?
As shown in another PR:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11597#issuecomment-194107507
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user nongli commented on the pull request:
https://github.com/apache/spark/pull/11594#issuecomment-194107548
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11597#issuecomment-194107504
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/11597#issuecomment-194107364
**[Test build #52717 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52717/consoleFull)**
for PR 11597 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11555#issuecomment-194107200
**[Test build #52720 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52720/consoleFull)**
for PR 11555 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11596#issuecomment-194106587
hi @dilipbiswal , thanks for working on this! Some high-level questions:
1. Can any `Generate` operator be converted to a LATERAL VIEW? Does the
plan tree
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/10821#issuecomment-194106215
@tgravescs , I think here this PR fix the same issue as in #11518 , the
difference here is to access from RM's web UI, the URL should keep consistent,
would you
Github user maropu commented on the pull request:
https://github.com/apache/spark/pull/11576#issuecomment-194106085
Oh, I see. However, I think it is slightly difficult for users to notice
this option in that case (the option is true by default). How about
automatically detecting the
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11538#issuecomment-194102204
LGTM cc @liancheng
---
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 pull request:
https://github.com/apache/spark/pull/11598#issuecomment-194098450
Can one of the admins verify this patch?
---
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 zuowang opened a pull request:
https://github.com/apache/spark/pull/11598
[SPARK-12697][Streaming] Allow adding new streams without stopping Spâ¦
## What changes were proposed in this pull request?
An example to add new streams on the fly.
You can merge this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11596#issuecomment-194098014
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/11596#issuecomment-194098012
**[Test build #52719 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52719/consoleFull)**
for PR 11596 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11596#issuecomment-194098015
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/11596#issuecomment-194097849
**[Test build #52719 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52719/consoleFull)**
for PR 11596 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11578#issuecomment-194097560
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/11578#issuecomment-194097557
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/11538#issuecomment-194097264
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/11538#issuecomment-194097268
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/11578#issuecomment-194097263
**[Test build #52710 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52710/consoleFull)**
for PR 11578 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/11512#issuecomment-194097212
Thanks a lot for your comment @tgravescs , I think the scenario you
mentioned though has race condition, it seldom happens, and currently we don't
have solutions to
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11596#issuecomment-194097163
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11538#issuecomment-194097066
**[Test build #52712 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52712/consoleFull)**
for PR 11538 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/11444#discussion_r55467820
--- Diff: python/pyspark/sql/types.py ---
@@ -681,6 +681,129 @@ def __eq__(self, other):
for v in [ArrayType, MapType,
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/11444#issuecomment-194096618
ah i see, thanks! JIRA created:
https://issues.apache.org/jira/browse/SPARK-13762
---
If your project is set up for it, you can reply to this email and have your
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11550#issuecomment-194095931
cc @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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11555#issuecomment-194094117
**[Test build #52718 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52718/consoleFull)**
for PR 11555 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11594#issuecomment-194093407
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/11594#issuecomment-194093404
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/11593#issuecomment-194093113
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/11594#issuecomment-194093080
**[Test build #52714 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52714/consoleFull)**
for PR 11594 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11593#issuecomment-194093109
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/11593#issuecomment-194092571
**[Test build #52708 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52708/consoleFull)**
for PR 11593 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11534#issuecomment-194092278
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/11534#issuecomment-194092280
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11541#issuecomment-194092186
The latest one is at commit `2e20843`, and all three builds (including
that) passes.
---
If your project is set up for it, you can reply to this email and have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11534#issuecomment-194092098
**[Test build #52707 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52707/consoleFull)**
for PR 11534 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11576#issuecomment-194091960
I think it is a problem when the underlying files change.
---
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 maropu commented on the pull request:
https://github.com/apache/spark/pull/11576#issuecomment-194090951
Any possible case these metadata caches causing some problems?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11541#issuecomment-194085546
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/11597#issuecomment-194085406
**[Test build #52717 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52717/consoleFull)**
for PR 11597 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11541#issuecomment-194085552
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/11541#issuecomment-194084124
**[Test build #52696 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52696/consoleFull)**
for PR 11541 at commit
GitHub user sameeragarwal opened a pull request:
https://github.com/apache/spark/pull/11597
[SPARK-13760][SQL] Fix BigDecimal constructor for FloatType
## What changes were proposed in this pull request?
A very minor change for using `BigDecimal.decimal(f: Float)` instead
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11541#issuecomment-194081760
Hi, @mengxr .
The latest commit passes the test.
Could you review this again please?
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11403#issuecomment-194077579
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/11403#issuecomment-194077587
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/11403#issuecomment-194076934
**[Test build #52709 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52709/consoleFull)**
for PR 11403 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/11585#issuecomment-194076759
After offline discussion with @sameeragarwal , we agreed that 1) the
constraints should only used in logical plan 2) we should use the `IsNotNull()`
inserted by #11372,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11534#issuecomment-194075328
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/11534#issuecomment-194075324
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 davies commented on the pull request:
https://github.com/apache/spark/pull/11444#issuecomment-194074866
@cloud-fan In Python, the list of names could be a single string, for
example:
```
>>> from collections import namedtuple
>>> row = namedtuple("row", "a b
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11534#issuecomment-194074726
**[Test build #52704 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52704/consoleFull)**
for PR 11534 at commit
Github user dilipbiswal commented on the pull request:
https://github.com/apache/spark/pull/11596#issuecomment-194074582
@rxin @cloud-fan @liancheng @gatorsmile Hi Reynold and Wenchen,
I have made change to generate LATERAL view for all generators specified in
projection list as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11596#issuecomment-194074398
Can one of the admins verify this patch?
---
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 dilipbiswal opened a pull request:
https://github.com/apache/spark/pull/11596
[SPARK-12719][SQL] [WIP] SQL generation support for generators, including
UDTF
## What changes were proposed in this pull request?
This is a alternate way to convert SQL from analyzed
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11534#issuecomment-194074040
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/11534#issuecomment-194074039
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/11534#issuecomment-194073883
**[Test build #52705 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52705/consoleFull)**
for PR 11534 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11595#issuecomment-194073722
**[Test build #52716 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52716/consoleFull)**
for PR 11595 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11541#issuecomment-194073319
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/11541#issuecomment-194073324
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/11541#issuecomment-194072517
**[Test build #52699 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52699/consoleFull)**
for PR 11541 at commit
GitHub user mwws opened a pull request:
https://github.com/apache/spark/pull/11595
[SPARK-13758][Streaming][core]enhance exception message to avoid misleading
We have a recoverable Spark streaming job with checkpoint enabled, it could
be executed correctly at first time, but throw
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11588
---
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 pull request:
https://github.com/apache/spark/pull/11410#issuecomment-194071403
**[Test build #52715 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52715/consoleFull)**
for PR 11410 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11588#issuecomment-194070928
Thanks - 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11594#issuecomment-194064172
**[Test build #52714 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52714/consoleFull)**
for PR 11594 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11592#issuecomment-194062774
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user sameeragarwal opened a pull request:
https://github.com/apache/spark/pull/11594
[SPARK-13759][SQL] Add IsNotNull constraints for expressions with an
inequality
## What changes were proposed in this pull request?
This PR adds support for adding `IsNotNull`
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11592#issuecomment-194062773
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/9#issuecomment-194062594
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/9#issuecomment-194062592
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/11592#issuecomment-194062511
**[Test build #52706 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52706/consoleFull)**
for PR 11592 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9#issuecomment-194062283
**[Test build #52711 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52711/consoleFull)**
for PR 9 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11534#issuecomment-194061785
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/11534#issuecomment-194061779
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/11541#issuecomment-194061353
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/11534#issuecomment-194061280
**[Test build #52702 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52702/consoleFull)**
for PR 11534 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11541#issuecomment-194061350
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/11541#issuecomment-194060744
**[Test build #52697 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/52697/consoleFull)**
for PR 11541 at commit
Github user falaki closed the pull request at:
https://github.com/apache/spark/pull/11589
---
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 falaki commented on the pull request:
https://github.com/apache/spark/pull/11589#issuecomment-194060579
Thanks closing it. For some reason it did not close.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/11589#issuecomment-194060349
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 this
Github user BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/11476#issuecomment-194059874
No problem, 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11590
---
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
101 - 200 of 777 matches
Mail list logo
