[jira] [Commented] (TIKA-694) On extraction, get properties AND / OR content extraction

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (TIKA-694) On extraction, get properties AND / OR content extraction

Chris Mattmann (Jira)

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

Radu Gheorghe commented on TIKA-694:
------------------------------------

Thanks for following up, Tim! It makes perfect sense.

In my particular use-case, I don't mind the performance penalty of parsing the whole file to get metadata (though I think it's not needed in the very particular use-case of Emails). But I do run into trouble if the (potentially massive) body ends up in memory, because I can run out of heap. Using 0 bytes isn't too bad of a workaround, isn't it? :D

> On extraction, get properties AND / OR content extraction
> ---------------------------------------------------------
>
>                 Key: TIKA-694
>                 URL: https://issues.apache.org/jira/browse/TIKA-694
>             Project: Tika
>          Issue Type: Wish
>          Components: parser
>    Affects Versions: 1.0
>         Environment: All OS
>            Reporter: Etienne Jouvin
>            Priority: Minor
>         Attachments: Tika-1.0.zip
>
>
> I use TIKA to extract properties, and only, on Office files.
> The parser goes throw the document content and this is not necessary and slow down the process.
> It would be nice to have choice to extract only properties or not.
> What I did was the following:
> Extension of AutoDetectParser to override the parse method.
> Then in the ParseContext instance, I put a flag with boolean true to say only extract the properties.
> And for example, on office file, I extended OfficeParser class. During parse method, I check the flag, and if equals to true, I removed all the extraction from the content.



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