[ 
https://issues.apache.org/jira/browse/TIKA-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Allison updated TIKA-1212:
------------------------------

    Attachment: RECURSIVE_PARSER_WRAPPER_HACK.patch

This is nowhere near ready to go, but this shows the solution I mentioned.

There has to be an easier way...

SIDENOTE:
The overall design is that the parser wrapper returns a 
{code}List<Metadata>{code} and the content for each embedded file is stored 
within a Metadata.  This goes against several design principles within Tika, 
but I'd like to add something like this for TIKA-1302, and there may be 
interest for clients of server and cli.  If this looks to be useful, I'll clean 
it up, add test cases and commit.

> Recursive Extraction of Archive File
> ------------------------------------
>
>                 Key: TIKA-1212
>                 URL: https://issues.apache.org/jira/browse/TIKA-1212
>             Project: Tika
>          Issue Type: Bug
>            Reporter: Vikram
>            Priority: Critical
>         Attachments: RECURSIVE_PARSER_WRAPPER_HACK.patch, 
> RecursiveMetadataParserZukka.java, RecursiveParsingExample.java, 
> TIKA-Output.xlsx, abc.zip, abc.zip, test_recursive_embedded.docx
>
>
> Please refer the code: 
> http://wiki.apache.org/tika/RecursiveMetadata#Main_from_Jukka.27s_Example
> Requirement:
> -----------------
> abc.zip
>    ---> a.doc
>    ---> b.xls
>    ---> pqr.zip
>   -------------> m.ppt
> There are two issues with TIKA:
> 1. How to block extraction embedded doc separately optionally?
> 2. When I extract recussively, file name / or resourceKeyName is not coming 
> properly. For example
>     --> a.doc should have value  abc.zip/a.doc. Similarily for b.xls. This is 
> fine BUT m.ppt is having resource file name as pqr/m.ppt which is WRONG. This 
> should have value abc.zip/pqr.zip/m.ppt.
>     --> Even for the Embedded doc, only random name is coming.. not even with 
> proper file path.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to