You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/04/15 10:54:49 UTC
[jira] Resolved: (TIKA-243) Fire event at start- and end of archive
parsing
[ https://issues.apache.org/jira/browse/TIKA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved TIKA-243.
--------------------------------
Assignee: Jukka Zitting
Resolution: Won't Fix
Resolving as Won't Fix, since nowadays it's possible to pass a custom parser instance through the parse context that'll be called for each component document within an archive. This is the recommended way to implement custom handling of nested documents.
> Fire event at start- and end of archive parsing
> -----------------------------------------------
>
> Key: TIKA-243
> URL: https://issues.apache.org/jira/browse/TIKA-243
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Affects Versions: 0.3
> Reporter: Jan Goyvaerts
> Assignee: Jukka Zitting
> Priority: Minor
>
> Archive parsers fire a start- and stop document event. Although this is event is suppressed. Probably because only one start- and stop document events are allowed.
> Getting these events - or equivalents - in one way or another would be needed to index the files the archive contains separately. Because when Lucene has a hit on a file that is inside an archive the choice must be given to the users to download just that file and not the entire archive. And let the user figure out how to decompress the archive - assuming the user has a suitable decompressor installed - and locate the required file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira