Github user xwu0226 commented on the pull request:
https://github.com/apache/spark/pull/13088#issuecomment-219201641
@rxin I updated the code to use existing property
`spark.sql.catalogImplementation` when checking whether we should switch to use
in-memory or hive catalog. The
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13111#issuecomment-219200482
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/13111#issuecomment-219200467
**[Test build #58601 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58601/consoleFull)**
for PR 13111 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13111#issuecomment-219200483
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/13099#issuecomment-219200309
ping @mengxr
---
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/13111#issuecomment-219200094
**[Test build #58601 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58601/consoleFull)**
for PR 13111 at commit
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/13111
[SPARK-15320] [SQL] Spark-SQL Cli Ignores Parameter
hive.metastore.warehouse.dir
What changes were proposed in this pull request?
Although overriding `hive.metastore.warehouse.dir` in
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13104#issuecomment-219199027
(I think it might need a JIRA because it seems changing existing behaviour)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user smungee commented on the pull request:
https://github.com/apache/spark/pull/13108#issuecomment-219198990
@techaddict Added a 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
Github user techaddict commented on the pull request:
https://github.com/apache/spark/pull/13108#issuecomment-219198790
@smungee Can you please add tests for 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
Github user smungee commented on the pull request:
https://github.com/apache/spark/pull/13108#issuecomment-219198553
The bug is quite easy to reproduce. In `ExpressionEncoderSuite`, if you add
the following test case:
` encodeDecodeTest(Array(Timestamp.valueOf("2016-01-29
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12767#issuecomment-219197282
**[Test build #58600 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58600/consoleFull)**
for PR 12767 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12767#issuecomment-219197287
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/12767#issuecomment-219197286
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/12767#issuecomment-219197017
**[Test build #58600 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58600/consoleFull)**
for PR 12767 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12767#issuecomment-219196442
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/12767#issuecomment-219196443
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/12767#issuecomment-219196440
**[Test build #58599 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58599/consoleFull)**
for PR 12767 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12767#issuecomment-219196409
**[Test build #58599 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58599/consoleFull)**
for PR 12767 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13103#issuecomment-219193377
For me, I would like to say this might better be closed if this PR does not
propose code changes. I think It would be nicer if the bug report is in the
JIRA.
---
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13103#issuecomment-219193053
In
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-ContributingBugReports
, It seems not suggesting to create a PR
Github user smungee commented on the pull request:
https://github.com/apache/spark/pull/13108#issuecomment-219192693
@HyukjinKwon I think the original author might have just forgotten to add
the TimestampType to the match..
---
If your project is set up for it, you can reply to this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11374#issuecomment-219192553
**[Test build #58598 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58598/consoleFull)**
for PR 11374 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11374#issuecomment-219192556
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/11374#issuecomment-219192555
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11374#issuecomment-219192289
**[Test build #58598 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58598/consoleFull)**
for PR 11374 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13086
---
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/13086#issuecomment-219191756
Merging in master/2.0. 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 pprado commented on the pull request:
https://github.com/apache/spark/pull/13103#issuecomment-219191363
Sorry, I tried to follow this document:
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-ContributingBugReports
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13108#issuecomment-219191307
(I think it might needs a JIRA because it seems changing existing behaviour)
---
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/11105#issuecomment-219191041
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/11105#issuecomment-219191037
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/11105#issuecomment-219190960
**[Test build #58595 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58595/consoleFull)**
for PR 11105 at commit
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/13107#discussion_r63267469
--- Diff:
core/src/main/java/org/apache/spark/util/collection/unsafe/sort/UnsafeExternalSorter.java
---
@@ -143,6 +151,8 @@ private
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13103#issuecomment-219188872
Because I guess this is a contribution to Spark and there is a guide for
this. It seems there are a lot of things wrong with this PR (e.g. no JIRA).
---
If your
Github user HyukjinKwon commented on a diff in the pull request:
https://github.com/apache/spark/pull/13107#discussion_r6329
--- Diff:
core/src/main/java/org/apache/spark/util/collection/unsafe/sort/UnsafeExternalSorter.java
---
@@ -24,6 +24,8 @@
import java.util.Queue;
Github user pprado commented on the pull request:
https://github.com/apache/spark/pull/13103#issuecomment-219187681
Why?
Em 13 de mai de 2016 9:08 PM, "Hyukjin Kwon"
escreveu:
> I think it would be good if you follow
>
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8559#issuecomment-219186967
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 HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/13103#issuecomment-219187010
I think it would be good if you follow
https://cwiki.apache.org/confluence/display/SPARK/Spark+Code+Style+Guide.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8559#issuecomment-219186969
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/8559#issuecomment-219186887
**[Test build #58593 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58593/consoleFull)**
for PR 8559 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13110#issuecomment-219183105
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/13110#issuecomment-219183104
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/13110#issuecomment-219183057
**[Test build #58597 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58597/consoleFull)**
for PR 13110 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13109#issuecomment-219182766
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/13109#issuecomment-219182765
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/13109#issuecomment-219182730
**[Test build #58596 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58596/consoleFull)**
for PR 13109 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13110#issuecomment-219182172
**[Test build #58597 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58597/consoleFull)**
for PR 13110 at commit
GitHub user wangmiao1981 opened a pull request:
https://github.com/apache/spark/pull/13110
[SPARK-15318][ML][Example]:spark.ml Collaborative Filtering example does
not work in spark-shell
## What changes were proposed in this pull request?
(Please fill in changes proposed
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/13109#issuecomment-219181759
LGTM. Thanks @felixcheung
---
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/13109#issuecomment-219180940
**[Test build #58596 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58596/consoleFull)**
for PR 13109 at commit
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/13109#issuecomment-219180908
@shivaram @sun-rui
---
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 felixcheung opened a pull request:
https://github.com/apache/spark/pull/13109
[SPARK-15319][SPARKR][DOCS] Fix SparkR doc layout for corr and other
DataFrame stats functions
## What changes were proposed in this pull request?
Doc only changes. Please see
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11105#issuecomment-219180295
**[Test build #58595 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58595/consoleFull)**
for PR 11105 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12889#issuecomment-219179609
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/12889#issuecomment-219179607
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/12889#issuecomment-219179550
**[Test build #58594 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58594/consoleFull)**
for PR 12889 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12889#issuecomment-219177910
**[Test build #58594 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58594/consoleFull)**
for PR 12889 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13108#issuecomment-219177160
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 smungee opened a pull request:
https://github.com/apache/spark/pull/13108
Fix MapObjects.itemAccessorMethod to handle TimestampType
## What changes were proposed in this pull request?
Fix `MapObjects.itemAccessorMethod` to handle `TimestampType`. Without this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8559#issuecomment-219172799
**[Test build #58593 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58593/consoleFull)**
for PR 8559 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12947#issuecomment-219168440
@clockfly It seems that this does not work with temporary tables, could you
send an PR to fix that?
---
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/13104#issuecomment-219165088
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/13104#issuecomment-219165082
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/13104#issuecomment-219164866
**[Test build #58591 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58591/consoleFull)**
for PR 13104 at commit
Github user kevinyu98 commented on the pull request:
https://github.com/apache/spark/pull/12646#issuecomment-219164845
retest it.
---
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 satlal commented on the pull request:
https://github.com/apache/spark/pull/9246#issuecomment-219163186
@XuTingjun revisiting this thread. Since this patch seems to be abandoned,
were you able to work around the large log files issue for long running
streaming jobs?
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8559#issuecomment-219158034
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/8559#issuecomment-219158033
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/8559#issuecomment-219157811
**[Test build #58590 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58590/consoleFull)**
for PR 8559 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/13093#issuecomment-219153156
@cloud-fan @yhuai @liancheng Could you please review this PR? Thanks!
---
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/13106#issuecomment-219152856
**[Test build #58592 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58592/consoleFull)**
for PR 13106 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13106#issuecomment-219152958
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/13106#issuecomment-219152957
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 sitalkedia commented on the pull request:
https://github.com/apache/spark/pull/13107#issuecomment-219152163
cc- @srowen, @JoshRosen
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13107#issuecomment-219151861
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 sitalkedia opened a pull request:
https://github.com/apache/spark/pull/13107
[SPARK-13850] Force the sorter to Spill when number of elements in thâ¦
## What changes were proposed in this pull request?
Force the sorter to Spill when number of elements in the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13106#issuecomment-219150836
**[Test build #58592 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58592/consoleFull)**
for PR 13106 at commit
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/12725#discussion_r63246142
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamSuite.scala ---
@@ -137,20 +137,88 @@ class StreamSuite extends StreamTest with
GitHub user holdenk opened a pull request:
https://github.com/apache/spark/pull/13106
[SPARK-15316][PySpark][ML] Add linkPredictionCol to
GeneralizedLinearRegression
## What changes were proposed in this pull request?
Add linkPredictionCol to GeneralizedLinearRegression
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13104#issuecomment-219147522
**[Test build #58591 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58591/consoleFull)**
for PR 13104 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/13104#issuecomment-219146749
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13102#issuecomment-219143546
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/13102#issuecomment-219143551
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/13102#issuecomment-219143332
**[Test build #58589 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58589/consoleFull)**
for PR 13102 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10125#issuecomment-219141188
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/10125#issuecomment-219141172
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/10125#issuecomment-219140939
**[Test build #58588 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58588/consoleFull)**
for PR 10125 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13105#issuecomment-219139730
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 sureshthalamati opened a pull request:
https://github.com/apache/spark/pull/13105
[SPARK-15315][SQL] Adding error check to the CSV datasource writer for
unsupported complex data types.
## What changes were proposed in this pull request?
Adds error handling to
Github user kevinyu98 commented on the pull request:
https://github.com/apache/spark/pull/10125#issuecomment-219136788
I just run the ./dev/mima locally, it works,
[info] Done packaging.
[info] spark-examples: previous-artifact not set, not analyzing binary
compatibility
Github user kevinyu98 commented on the pull request:
https://github.com/apache/spark/pull/10125#issuecomment-219136812
retest it 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
Github user buckhx commented on the pull request:
https://github.com/apache/spark/pull/12398#issuecomment-219136325
changed addRequirementsFile to addPyRequirements which takes a list of
requirement strings
---
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/8559#issuecomment-219134254
**[Test build #58590 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58590/consoleFull)**
for PR 8559 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13104#issuecomment-219130685
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13103#issuecomment-219130690
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 jurriaan opened a pull request:
https://github.com/apache/spark/pull/13104
Fix reading of partitioned format=text datasets
I was using this in Spark 1.6.1 but it broke in Spark 2.0.0.
It would be logical if you could also write those,
but not entirely sure
GitHub user pprado opened a pull request:
https://github.com/apache/spark/pull/13103
Problem select empty ORC table
## Error when I selected empty ORC table
> [pprado@hadoop-m ~]$ beeline -u jdbc:hive2://
WARNING: Use "yarn jar" to launch YARN applications.
Github user tejasapatil commented on the pull request:
https://github.com/apache/spark/pull/13042#issuecomment-219128637
There are no outstanding review comments left to address here. If
everything looks good, can someone merge this PR ? Thanks !!
---
If your project is set up for
Github user tejasapatil commented on the pull request:
https://github.com/apache/spark/pull/13042#issuecomment-219128249
@vanzin : I haven't gathered numbers with `Files.walkFileTree`. Based on
its source code, it will have the same quirks wrt race conditions and speed. I
believe
1 - 100 of 386 matches
Mail list logo