commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (IO-170) Scalable Iterator for files, better than FileUtils.iterateFiles
Date Tue, 08 Oct 2019 01:50:00 GMT


ASF GitHub Bot logged work on IO-170:

                Author: ASF GitHub Bot
            Created on: 08/Oct/19 01:49
            Start Date: 08/Oct/19 01:49
    Worklog Time Spent: 10m 
      Work Description: detinho commented on issue #67: IO-170: Scalable Iterator for files,
better than FileUtils.iterateFiles
   @garydgregory in that case it would be Files.walkTree, as Files.walk was introduced on
Java 1.8.
   Regarding Files.walkTree, it would be possible to use it instead FileUtils.iterateFiles,
but not with an Iterator pattern.
   I think it would be nice to update the documentation too, so users can be aware of Files.walk
in case they are using Java 1.8 already and use the Stream pattern, what do you think?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

            Worklog Id:     (was: 324801)
    Remaining Estimate: 4.5h  (was: 4h 40m)
            Time Spent: 0.5h  (was: 20m)

> Scalable Iterator for files, better than FileUtils.iterateFiles
> ---------------------------------------------------------------
>                 Key: IO-170
>                 URL:
>             Project: Commons IO
>          Issue Type: Improvement
>          Components: Utilities
>    Affects Versions: 1.4
>         Environment: generic file systems
>            Reporter: Damian Noseda
>            Priority: Minor
>             Fix For: 3.x
>         Attachments: real_iterators.patch
>   Original Estimate: 5h
>          Time Spent: 0.5h
>  Remaining Estimate: 4.5h
> Improve the way that iterateFiles generate an iterator. The current way it not scale.
It's try to add all files in a list and then return the iterator of that list. A better way
it would be create an customize Iterator<File> with a stack of arrays of File to go
up and down in the directory tree.

This message was sent by Atlassian Jira

View raw message