Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183219842
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183219843
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/5
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183219699
**[Test build #51174 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51174/consoleFull)**
for PR 9893 at commit
[`fe79873`](https://git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11180#issuecomment-183219234
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 p
GitHub user amitdev opened a pull request:
https://github.com/apache/spark/pull/11180
Added pygments.rb dependancy
Looks like pygments.rb gem is also required for jekyll build to work. At
least on Ubuntu/RHEL I could not do build without this dependency. So added
this to steps.
Yo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183216520
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183216521
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/5
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183216221
**[Test build #51172 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51172/consoleFull)**
for PR 9893 at commit
[`e61ec6a`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11178#issuecomment-183211245
**[Test build #51176 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51176/consoleFull)**
for PR 11178 at commit
[`bef62eb`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11178#issuecomment-183211271
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11178#issuecomment-183211270
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11178#issuecomment-183206102
**[Test build #51176 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51176/consoleFull)**
for PR 11178 at commit
[`bef62eb`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11179#issuecomment-183206172
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11179#issuecomment-183206177
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11179#issuecomment-183205820
**[Test build #51173 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51173/consoleFull)**
for PR 11179 at commit
[`8d443e9`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11140#issuecomment-183201556
**[Test build #51175 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51175/consoleFull)**
for PR 11140 at commit
[`837252a`](https://gi
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10838#issuecomment-183200705
@redsanket what's your JIRA account name? I want to assign it to you.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10838
---
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 zsxwing commented on the pull request:
https://github.com/apache/spark/pull/10838#issuecomment-183200242
Merging to master. Thanks, @redsanket
---
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 do
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/11140#issuecomment-183198830
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 fe
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/8#issuecomment-183198008
Just saw this got merged. I'm probably missing some context, but can
somebody explain to me why something so conceptually simple leads to such a big
patch?
---
If your p
Github user ygcao commented on the pull request:
https://github.com/apache/spark/pull/10152#issuecomment-183197942
addressed new comments. still kept the if statement as I explained by
sample codes.
reran test and lint test. Jenkins should still be happy :fireworks:
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11179#issuecomment-183197817
**[Test build #51173 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51173/consoleFull)**
for PR 11179 at commit
[`8d443e9`](https://gi
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11153#issuecomment-183197064
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
enabl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11100#issuecomment-183195272
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183195289
**[Test build #51174 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51174/consoleFull)**
for PR 9893 at commit
[`fe79873`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11100#issuecomment-183195269
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11100#issuecomment-183194619
**[Test build #51169 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51169/consoleFull)**
for PR 11100 at commit
[`79c11de`](https://g
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11078#issuecomment-183194684
@hhbyyh Did you test it? `Iterator` is lazy. I think the new version would
consume more memory because `modified` would store all the values.
---
If your project is set
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11179#issuecomment-183194055
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 projec
Github user ygcao commented on a diff in the pull request:
https://github.com/apache/spark/pull/10152#discussion_r52708705
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/Word2Vec.scala ---
@@ -289,24 +301,20 @@ class Word2Vec extends Serializable with Logging {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11179#issuecomment-183194060
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11179#issuecomment-183193865
**[Test build #51170 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51170/consoleFull)**
for PR 11179 at commit
[`8d443e9`](https://g
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11179#issuecomment-183191566
@yanboliang Could you take a look?
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/11179#issuecomment-183191594
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
ena
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183189659
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/5
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183189658
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9893#issuecomment-183189627
**[Test build #51172 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51172/consoleFull)**
for PR 9893 at commit
[`e61ec6a`](https://gith
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/11153#discussion_r52707357
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -572,98 +572,64 @@ class Analyzer(
// Skip
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/11153#discussion_r52707329
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -572,98 +572,64 @@ class Analyzer(
// Skip
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11179#issuecomment-183185609
**[Test build #51170 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51170/consoleFull)**
for PR 11179 at commit
[`8d443e9`](https://gi
GitHub user NarineK opened a pull request:
https://github.com/apache/spark/pull/11179
[SPARK-13295] [ ML, MLlib ] AFTSurvivalRegression.AFTAggregator
improvements - Avoids creating new instances of arrays/vectors for each record
As also mentioned/marked by TODO in AFTAggregator.AFTA
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11178#issuecomment-183181035
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11178#issuecomment-183181025
**[Test build #51168 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51168/consoleFull)**
for PR 11178 at commit
[`5528c48`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11178#issuecomment-183181036
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11100#issuecomment-183180286
**[Test build #51169 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51169/consoleFull)**
for PR 11100 at commit
[`79c11de`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11178#issuecomment-183179580
**[Test build #51168 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51168/consoleFull)**
for PR 11178 at commit
[`5528c48`](https://gi
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/11100#issuecomment-183178340
Thank you! @davies @aray
Yeah, my first fix is very similar to what you proposed above. Will
remember what you said regarding `GROUPING__ID`. After the rele
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10894#issuecomment-183172788
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10894#issuecomment-183172787
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10894#issuecomment-183172697
**[Test build #51167 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51167/consoleFull)**
for PR 10894 at commit
[`7151a73`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183170957
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183170958
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183170927
**[Test build #51146 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51146/consoleFull)**
for PR 10705 at commit
[`ef7d885`](https://g
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/6935#issuecomment-183169031
ps can you close this one 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 ha
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8
---
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 squito commented on the pull request:
https://github.com/apache/spark/pull/8#issuecomment-183168840
merged to master, thanks @steveloughran!
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11125#issuecomment-183159966
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11125#issuecomment-183159907
**[Test build #51166 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51166/consoleFull)**
for PR 11125 at commit
[`7e3ea32`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11125#issuecomment-183159964
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 projec
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11169#issuecomment-183158218
@rxin Can we maybe merge this for now and then take the optimisation into
account in another PR?
This optimisation would apply to all the pruned scan as wel
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11125#issuecomment-183158035
**[Test build #51166 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51166/consoleFull)**
for PR 11125 at commit
[`7e3ea32`](https://gi
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10894#issuecomment-183154802
**[Test build #51167 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51167/consoleFull)**
for PR 10894 at commit
[`7151a73`](https://gi
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11043
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/11125#issuecomment-183153830
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
ena
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/11043#issuecomment-183153739
Merged into master and branch-1.6. 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 projec
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/10697#issuecomment-183153557
Merged into master. Thanks! @Earthson I didn't merge it into branch-1.6
because `checkColumnTypes` is not available on branch-1.6. I don't think this
is a critical bug f
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11177#discussion_r52700130
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/Expand.scala ---
@@ -71,9 +80,76 @@ case class Expand(
idx = 0
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183153291
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183153257
**[Test build #51132 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51132/consoleFull)**
for PR 10705 at commit
[`a0c5bb3`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10705#issuecomment-183153290
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 projec
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11177#discussion_r52699940
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/Expand.scala ---
@@ -71,9 +80,76 @@ case class Expand(
idx = 0
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10697
---
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 ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/10894#discussion_r52699952
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/codegen/GenerateOrdering.scala
---
@@ -138,3 +138,32 @@ object GenerateOrderi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11177#issuecomment-183152706
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11177#issuecomment-183152703
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11177#issuecomment-183152562
**[Test build #51156 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51156/consoleFull)**
for PR 11177 at commit
[`22ceda9`](https://g
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11174
---
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 pull request:
https://github.com/apache/spark/pull/11043#issuecomment-183151944
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11043#issuecomment-183151946
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11043#issuecomment-183151833
**[Test build #51161 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51161/consoleFull)**
for PR 11043 at commit
[`06e06f7`](https://g
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11174#issuecomment-183151703
Thanks - going to merge this 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 do
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/11174#issuecomment-183151336
LGTM, looks like jenkins has generated proposed warning and caught it
correctly.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10697#issuecomment-183151260
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10697#issuecomment-183151263
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10697#issuecomment-183151137
**[Test build #51163 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51163/consoleFull)**
for PR 10697 at commit
[`9cd7ced`](https://g
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11177#issuecomment-183150208
As always, can you paste the generated code? :)
---
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 pr
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11178#issuecomment-183150046
LGTM provided tests pass.
---
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11109#issuecomment-183149783
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11109#issuecomment-183149781
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11109#issuecomment-183149629
**[Test build #51148 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51148/consoleFull)**
for PR 11109 at commit
[`c086135`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11142#issuecomment-183149434
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11142#issuecomment-183149432
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11142#issuecomment-183149328
**[Test build #51164 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51164/consoleFull)**
for PR 11142 at commit
[`6c3122a`](https://g
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11170
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/11170#issuecomment-183147622
I'm going to merge this.
---
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 thi
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11170#issuecomment-183147129
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
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11169#issuecomment-183146848
This
[CSVRelation.scala#L193-L199](https://github.com/HyukjinKwon/spark/blob/SPARK-13260/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/csv/CSVRe
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11170#issuecomment-183146671
**[Test build #2537 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2537/consoleFull)**
for PR 11170 at commit
[`ec716ea`](https://
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11169#issuecomment-183146606
I think I should have described this in more details. This works identical
with the original CSV datasource.
When the parsing mode is drop-malformed, then
1 - 100 of 655 matches
Mail list logo
