[
https://issues.apache.org/jira/browse/TIKA-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287995#comment-14287995
]
Nick Burch commented on TIKA-1527:
----------------------------------
TikaInputStream already supports the concept of an ["Open
Container"|https://tika.apache.org/1.7/api/org/apache/tika/io/TikaInputStream.html#getOpenContainer%28%29],
which can be attached. The open container can be ignored by parsers, but it
can save work when a detector spends some time parsing/processing a file to do
detection, which the parser can then piggy-back off of. TikaInputStream will
clean/close this container where possible when the overall input stream is
closed.
Could that work here too?
> Add payload to TikaInputStream
> ------------------------------
>
> Key: TIKA-1527
> URL: https://issues.apache.org/jira/browse/TIKA-1527
> Project: Tika
> Issue Type: Improvement
> Affects Versions: 1.7
> Reporter: Tim Allison
> Assignee: Tim Allison
>
> On TIKA-1511, I found a need to pass a Java object into a an
> EmbeddedDocumentExtractor. I would have sent the object into the parser via
> ParseContext, but EmbeddedDocumentExtractor doesn't take a ParseContext, and
> it makes some sense that this object should be used instead of the actual
> TikaInputStream.
> I propose adding a payload to TikaInputStream that would only be used
> internally by parsers of container documents passing information to
> EmbeddedDocumentExtractors.
> Any problems with this or alternatives?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
