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 2009/10/02 13:31:23 UTC

[jira] Commented: (TIKA-288) Support override parsers in AutoDetectParser

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

Jukka Zitting commented on TIKA-288:
------------------------------------

Hmm, I see. It feels to me that something like this should rather be handled at the TikaConfig level instead of in AutoDetectParser.

> Support override parsers in AutoDetectParser
> --------------------------------------------
>
>                 Key: TIKA-288
>                 URL: https://issues.apache.org/jira/browse/TIKA-288
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 0.4
>            Reporter: Ken Krugler
>            Priority: Minor
>
> In some situations, being able to specify an alternative parser is useful even when the general parser framework/full set of parsers is desired.
> For example, when processing HTML documents the current HtmlParser doesn't pass through all of the tags that a vertical crawler might want.
> I'm proposing an alternative constructor, something like:
> public AutoDetectParser(Map<class, Parser>)
> where class would be the class of the standard Tika parser, and Parser is the override.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.