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 2007/09/25 13:52:50 UTC
[jira] Resolved: (TIKA-26) Use Map instead of
List
[ https://issues.apache.org/jira/browse/TIKA-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved TIKA-26.
-------------------------------
Resolution: Fixed
Fixed in revisions 579006, 579207, and 579208.
> Use Map<String, Content> instead of List<Content>
> -------------------------------------------------
>
> Key: TIKA-26
> URL: https://issues.apache.org/jira/browse/TIKA-26
> Project: Tika
> Issue Type: Improvement
> Components: general
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Fix For: 0.1-incubator
>
> Attachments: TIKA-26.patch
>
>
> The current Parser classes take a List<Content> collection from ParserConfig, and explicitly reformat that collection into an internal Map<String,Content> map keyed by the Content names. I don't see any place where using a list of Content instances is better than a Map keyed by the Content names, so I'd like to simplify things by creating the map already in ParserConfig and using it directly ever since.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.