[ 
https://issues.apache.org/jira/browse/COMPRESS-540?focusedWorklogId=491944&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-491944
 ]

ASF GitHub Bot logged work on COMPRESS-540:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Sep/20 11:59
            Start Date: 28/Sep/20 11:59
    Worklog Time Spent: 10m 
      Work Description: PeterAlfredLee commented on pull request #113:
URL: https://github.com/apache/commons-compress/pull/113#issuecomment-699962152


   IMO, it's OK to have a random access for Tar - even through it would be 
slower as we read the `tar archive` to get the positions of entries. But I 
think we should hear more voice from others about this idea, cause this is a 
big change and `tar archives` are not designed to have a random access.
   
    @theobisproject And as you said, there are still some work(e.g. the 
refactor of the duplication) to do.


----------------------------------------------------------------
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 491944)
    Time Spent: 2h 40m  (was: 2.5h)

> Random access on Tar archive
> ----------------------------
>
>                 Key: COMPRESS-540
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-540
>             Project: Commons Compress
>          Issue Type: Improvement
>            Reporter: Robin Schimpf
>            Priority: Major
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> The TarArchiveInputStream only provides sequential access. If only a small 
> amount of files from the archive is needed large amount of data in the input 
> stream needs to be skipped.
> Therefore I was working on a implementation to provide random access to 
> TarFiles equal to the ZipFile api. The basic idea behind the implementation 
> is the following
>  * Random access is backed by a SeekableByteChannel
>  * Read all headers of the tar file and save the place to the data of every 
> header
>  * User can request an input stream for any entry in the archive multiple 
> times



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to