Github user yanboliang commented on the pull request:
https://github.com/apache/spark/pull/11258#issuecomment-186973326
@dbtsai I have copied tests from ML.
---
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/11262#issuecomment-186971819
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/11262#issuecomment-186971820
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/11262#issuecomment-186971303
**[Test build #51648 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51648/consoleFull)**
for PR 11262 at commit
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/10947#issuecomment-186970941
@NarineK, yes it is assumed that R has been installed in each worker node.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11262#issuecomment-186969215
**[Test build #51651 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51651/consoleFull)**
for PR 11262 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11262#issuecomment-186967397
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11229#issuecomment-186967084
**[Test build #51650 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51650/consoleFull)**
for PR 11229 at commit
Github user zhonghaihua commented on a diff in the pull request:
https://github.com/apache/spark/pull/10794#discussion_r53579600
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -169,6 +172,24 @@ private[yarn] class YarnAllocator(
}
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/11229#issuecomment-186961739
Thanks @andrewor14 for your comments, I've updated the codes accordingly,
please review.
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11262#issuecomment-186960032
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/11262#issuecomment-186960034
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11290
---
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/11262#issuecomment-186957557
**[Test build #2563 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2563/consoleFull)**
for PR 11262 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11290#issuecomment-186957610
I'm going to merge this in 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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11290#issuecomment-186957539
This is great timing given the next version is 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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11262#issuecomment-186957384
LGTM pending tests.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/11279
---
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 HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/11262#issuecomment-186956637
Sure.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11279#issuecomment-186955852
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 does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11279#issuecomment-186955298
**[Test build #2562 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2562/consoleFull)**
for PR 11279 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11262#issuecomment-186954558
**[Test build #51648 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51648/consoleFull)**
for PR 11262 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11262#issuecomment-186954500
Can you also update the pr description?
---
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11262#discussion_r53578002
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameReader.scala ---
@@ -345,6 +346,46 @@ class DataFrameReader private[sql](sqlContext:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11279#issuecomment-186954337
**[Test build #2561 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2561/consoleFull)**
for PR 11279 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11279#issuecomment-186953780
**[Test build #2560 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2560/consoleFull)**
for PR 11279 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/11262#discussion_r53577852
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/DataFrameReader.scala ---
@@ -345,6 +346,46 @@ class DataFrameReader private[sql](sqlContext:
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11295#issuecomment-186953261
@dongjoon-hyun if you are doing a few of these, can you merge them into a
single bigger patch?
---
If your project is set up for it, you can reply to this email and have
Github user jegonzal commented on the pull request:
https://github.com/apache/spark/pull/11290#issuecomment-186951853
This looks good to me. @insidedctm thanks for reviving the PR and @srowen
thanks for taking a look at this! My only minor concern is that it will change
the results
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11294#issuecomment-186947742
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/11294#issuecomment-186947741
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/11294#issuecomment-186947661
**[Test build #51645 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51645/consoleFull)**
for PR 11294 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11295#issuecomment-186945280
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 dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/11295
[MINOR][DOCS] Fix typos in ML doc
## What changes were proposed in this pull request?
This PR fixes some typos in ML and MLLib markdown document files.
## How was the this
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11293#issuecomment-186944373
> because we might have many "tables".
Yeah that's why I renamed it in the first place. As of this patch though
there are no more classes that are called
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11279#issuecomment-186944315
I will merge it once tests pass 3 times in a row.
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/11154
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/11275
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11154#issuecomment-186944104
LGTM. Merging in 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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11275#issuecomment-186943998
LGTM. 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 does
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11289#issuecomment-186943912
Thank you for merging, @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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11269#issuecomment-186943609
@maropu mind closing this for 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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11289
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11289#issuecomment-186943514
Thanks - I've merged 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
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11289#issuecomment-186943382
Thank you, @rxin. I remove the change on NOTICE file and rebased it now.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11279#issuecomment-186943312
**[Test build #2562 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2562/consoleFull)**
for PR 11279 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11289#issuecomment-186942883
Yes only notice. 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 dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/11289#issuecomment-186942753
Oh, sure. No problem. Only for `NOTICE`, right?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11279#issuecomment-186942409
**[Test build #2561 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2561/consoleFull)**
for PR 11279 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11279#issuecomment-186941497
**[Test build #2560 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2560/consoleFull)**
for PR 11279 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11289#issuecomment-186941205
I don't think we should change the NOTICE file. Can you reset the change
for that?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11293#issuecomment-186940230
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/11293#issuecomment-186940231
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/11293#issuecomment-186940162
**[Test build #51644 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51644/consoleFull)**
for PR 11293 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11293
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11293#issuecomment-186939416
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 does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11286#issuecomment-186939363
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/11293#issuecomment-186939374
Alright let's discuss the renaming. I initially just used Table, but I
think both could work (Table or CatalogTable), because we might have many
"tables".
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11286#issuecomment-186939366
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/11286#issuecomment-186939000
**[Test build #51643 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51643/consoleFull)**
for PR 11286 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11293#issuecomment-186938837
**[Test build #2559 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2559/consoleFull)**
for PR 11293 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11128#issuecomment-186938240
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/11128#issuecomment-186938239
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/11128#issuecomment-186938138
**[Test build #51647 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51647/consoleFull)**
for PR 11128 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11128#issuecomment-186935322
**[Test build #51647 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51647/consoleFull)**
for PR 11128 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11108#issuecomment-186935010
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/11108#issuecomment-186935006
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/11108#issuecomment-186934904
**[Test build #51646 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51646/consoleFull)**
for PR 11108 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11294#issuecomment-186934695
**[Test build #51645 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51645/consoleFull)**
for PR 11294 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/11260#discussion_r53574661
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicOperators.scala
---
@@ -260,6 +260,20 @@ case class Join(
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11108#issuecomment-186930988
**[Test build #51646 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51646/consoleFull)**
for PR 11108 at commit
Github user andrewor14 closed the pull request at:
https://github.com/apache/spark/pull/11189
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11189#issuecomment-186930674
Closing in favor of #11293.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11293#issuecomment-186930661
Thanks, @davies also suggested offline to rename all `CatalogTable` and
related classes to just `Table`. We can do that separately after this patch
gets merged.
GitHub user hvanhovell opened a pull request:
https://github.com/apache/spark/pull/11294
[SPARK-13424][SQL] Improve test coverage of EnsureRequirements [WIP]
### What changes were proposed in this pull request?
Improve the testing of the `EnsureRequirements` planner rule. This
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11023
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11023#issuecomment-186921039
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 xguo27 commented on the pull request:
https://github.com/apache/spark/pull/11291#issuecomment-186923232
@hvanhovell I just rebased with your new PR, do you mind reviewing again?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/11220#discussion_r53573498
--- Diff: R/pkg/R/DataFrame.R ---
@@ -303,8 +303,28 @@ setMethod("colnames",
#' @rdname columns
#' @name colnames<-
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11293#issuecomment-186918335
**[Test build #51644 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51644/consoleFull)**
for PR 11293 at commit
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/11267#discussion_r53573356
--- Diff: R/pkg/R/functions.R ---
@@ -536,15 +536,27 @@ setMethod("factorial",
#'
#' Aggregate function: returns the first value in a group.
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/11293#issuecomment-186915642
LGTM pending tests
---
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/11293#issuecomment-186914838
**[Test build #2559 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2559/consoleFull)**
for PR 11293 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11293#issuecomment-186914774
I simply brought https://github.com/apache/spark/pull/11189 up to date and
resolved some code review issues so we can merge this quickly and unblock some
other work.
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11189#issuecomment-186914590
FYI I took most of Herman and Davies' comments and created a rebased pr
here: https://github.com/apache/spark/pull/11293
---
If your project is set up for it, you
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/11293
[SPARK-13080] [SQL] Implement new Catalog API using Hive
## What changes were proposed in this pull request?
This is a step towards merging `SQLContext` and `HiveContext`. A new
internal
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/11291#issuecomment-186909702
@xguo27 you'll need rebase this. We just merged a PR that changes broadcast
joins.
---
If your project is set up for it, you can reply to this email and have your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11286#issuecomment-186909589
**[Test build #51643 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/51643/consoleFull)**
for PR 11286 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11083
---
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/11291#issuecomment-186909052
**[Test build #2558 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2558/consoleFull)**
for PR 11291 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11083#issuecomment-186908861
Thanks. 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
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/11189#issuecomment-186908709
@andrewor14 This is pretty solid, couldn't find anything except for some
trivial stuff.
LGTM pending an update to the latest master and a succesfull test
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11285
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/11285#issuecomment-186907761
Merging 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 does not have
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/11189#discussion_r53572493
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/HiveClientImpl.scala
---
@@ -18,24 +18,26 @@
package
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/11189#discussion_r53572447
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveMetastoreCatalog.scala ---
@@ -765,9 +771,14 @@ private[hive] case class
Github user holdenk closed the pull request at:
https://github.com/apache/spark/pull/11287
---
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/11287#issuecomment-186900836
I did some digging into why its 32 in jenkins and 4 on my machine - digging
into the Scala internals it seems that the (private) FutureTasks doesn't
actually look at
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/11189#discussion_r53572202
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/interface.scala
---
@@ -174,40 +207,65 @@ case class TablePartition(
*
Github user hvanhovell commented on the pull request:
https://github.com/apache/spark/pull/11291#issuecomment-186896296
@xguo27 how expensive is the no-op? I'd rather avoid a pointless iteration
in a hot code section.
---
If your project is set up for it, you can reply to this email
101 - 200 of 429 matches
Mail list logo
