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] (COMPRESS-540) Random access on Tar archive
Date Thu, 03 Sep 2020 18:25:00 GMT


ASF GitHub Bot logged work on COMPRESS-540:

                Author: ASF GitHub Bot
            Created on: 03/Sep/20 18:24
            Start Date: 03/Sep/20 18:24
    Worklog Time Spent: 10m 
      Work Description: coveralls edited a comment on pull request #113:

   [![Coverage Status](](
   Coverage increased (+0.06%) to 87.282% when pulling **bdd25476847d5b347cad288114e46e3ea474fe3e
on theobisproject:random-access-tar** into **4eb3bbe8e95f5e3b6388b1e8db28b862cc712294 on apache:master**.

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: 478748)
    Time Spent: 2.5h  (was: 2h 20m)

> Random access on Tar archive
> ----------------------------
>                 Key: COMPRESS-540
>                 URL:
>             Project: Commons Compress
>          Issue Type: Improvement
>            Reporter: Robin Schimpf
>            Priority: Major
>          Time Spent: 2.5h
>  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

View raw message