You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Keith R. Bennett (JIRA)" <ji...@apache.org> on 2007/10/19 16:55:51 UTC

[jira] Closed: (TIKA-59) Include parser class name in Metadata object.

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

Keith R. Bennett closed TIKA-59.
--------------------------------

    Resolution: Won't Fix

Jukka pointed out that a document could be handled by multiple parsers.  We'd need to have a list, and parsers that wrap other parsers would need to add both to the list.  So the cost of implementing this feature is higher than I originally thought.


> Include parser class name in Metadata object.
> ---------------------------------------------
>
>                 Key: TIKA-59
>                 URL: https://issues.apache.org/jira/browse/TIKA-59
>             Project: Tika
>          Issue Type: Wish
>          Components: general
>    Affects Versions: 0.1-incubator
>            Reporter: Keith R. Bennett
>            Priority: Minor
>             Fix For: 0.1-incubator
>
>
> It would be helpful to know which parser was used to parse a given document.  Some convenience methods eliminate the need for the user to make that determination, so in that case there would be no way to know which parser was used.
> This feature could be helpful in testing and debugging, both for ourselves and for users.
> The class name could either be an entry in the Map (a property), or an instance variable.
> If the Parser ever becomes an abstract class, the act of setting this value could be done in the abstract class constructor, eliminating the need for parser implementations to deal with this.

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