[
https://issues.apache.org/jira/browse/TIKA-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534533
]
Keith R. Bennett commented on TIKA-59:
--------------------------------------
I hadn't thought about multiple parsers. I suppose there could be a list, and
the parser could add itself to the list.
But I'm not certain that the benefit exceeds the cost either.
OTOH, one of our previous discussions mentioned the possibility of Tika not
doing any logging at all. If that is the case, then maybe the Metadata object
is where we would put this information, and the user could access it or not
access it, as they like. Or is this diagnostic information not that important?
> 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.
