[
https://issues.apache.org/jira/browse/TIKA-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034983#comment-13034983
]
Jukka Zitting commented on TIKA-645:
------------------------------------
In revision 1104472 I made TikaInputStream extend TaggedInputStream which
allows us to avoid one of these levels of wrapping (and also makes it possible
to separate exceptions from the original stream from those caused by temporary
file handling, etc.).
I'll look at what we can do about the CountingInputStream wrapper.
> Parsers can't get at an underlying TikaInputStream to get the file if they
> wanted one
> -------------------------------------------------------------------------------------
>
> Key: TIKA-645
> URL: https://issues.apache.org/jira/browse/TIKA-645
> Project: Tika
> Issue Type: Bug
> Components: parser
> Affects Versions: 0.9
> Reporter: Nick Burch
>
> Spotted this with the office parser, but it should be general. The user
> creates a TikaInputStream, and passes that off to the parser framework. The
> Parser that is called may wish to spot that the input is a File backed
> TikaInputStream, and take a shortcut to use the file instead of the
> InputStream.
> However, what the parser gets is a TaggedInputStream wrapping a
> CountingInputStream wrapping the original TikaInputStream. As such, it can't
> get at the file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
