[jira] [Comment Edited] (COMPRESS-560) TarArchiveInputStream returns wrong value on canReadEntryData for sparse entries

["Peter Lee (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COMPRESS-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239003#comment-17239003 ] 

Peter Lee edited comment on COMPRESS-560 at 11/26/20, 9:12 AM:
---------------------------------------------------------------

Yes. Seems we can always read the entry now, and we do not need a canReadEntryData here any more.

-Since it's a public method and removing it may break the BC, maybe we can make it always return true and have a Deprecated annotation here. WDYT?-


was (Author: peterlee):
Yes. Seems we can always read the entry now, and we do not need a canReadEntryData here any more.

Since it's a public method and removing it may break the BC, maybe we can make it always return true and have a Deprecated annotation here. WDYT?

> TarArchiveInputStream returns wrong value on canReadEntryData for sparse entries
> --------------------------------------------------------------------------------
>
>                 Key: COMPRESS-560
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-560
>             Project: Commons Compress
>          Issue Type: Bug
>    Affects Versions: 1.20
>            Reporter: Robin Schimpf
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Since sparse tar content files are now supported the result from canReadEntryData is wrong since it still returns false if the entry is a sparse file.



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