You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2014/06/20 18:30:25 UTC

[jira] [Updated] (TIKA-1351) Parser implementations should accept null content handlers

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

Sergey Beryozkin updated TIKA-1351:
-----------------------------------

    Description: 
Applications which want to let users search documents based only on their metadata do not need to get the content parsed. 
The only workaround I've found so far is to pass a no op content handler which can ignore the content events but it does not stop the parser such as PDFParser from parsing the content.

Proposal: update parser API docs to let implementers know ContentHandler can be null and update the shipped implementations to parse the metadata only if ContentHandler is null

  was:
Applications which want to let users search documents based only on their metadata do not need to get the content parsed. 
The only workaround I've found so far is to pass a no op content handler which can ignore the content events but it does not stop the parser such as PDFParser from parsing the content.

Proposal: update parser API docs to let implementers know ContentHandler can be empty and update the shipped implementations to parse the metadata only if ContentHandler is null


> Parser implementations should accept null content handlers
> ----------------------------------------------------------
>
>                 Key: TIKA-1351
>                 URL: https://issues.apache.org/jira/browse/TIKA-1351
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>            Reporter: Sergey Beryozkin
>            Priority: Minor
>
> Applications which want to let users search documents based only on their metadata do not need to get the content parsed. 
> The only workaround I've found so far is to pass a no op content handler which can ignore the content events but it does not stop the parser such as PDFParser from parsing the content.
> Proposal: update parser API docs to let implementers know ContentHandler can be null and update the shipped implementations to parse the metadata only if ContentHandler is null



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