[
https://issues.apache.org/jira/browse/TIKA-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17893842#comment-17893842
]
Tim Allison commented on TIKA-4314:
-----------------------------------
Sorry for dropping the ball on this. The SupplementingParser is definitely the
way to go with this. I looked at it this morning and we haven't wired up the
serialization/configuration so that you can easily specify which component
parsers go into that Parser.
If we did that, then we would be able to configure
{{o.a.t.p.external2.ExternalParser}}s for each commandline you wanted.
If you don't need to configure this via xml, e.g. you're running Tika
programmatically, this should be not too hard.
> CompositeParser returns only one parser per content type
> --------------------------------------------------------
>
> Key: TIKA-4314
> URL: https://issues.apache.org/jira/browse/TIKA-4314
> Project: Tika
> Issue Type: Bug
> Components: core
> Affects Versions: 2.9.2
> Reporter: Leszek Sliwko
> Priority: Major
> Attachments: duration-test-2.avi, geolocation-test-1.jpg,
> geolocation-test-2.jpg
>
>
> External parsers can have many supported content types, but information is
> lost in CompositeParser:
>
> public Map<MediaType, Parser> getParsers(ParseContext context) {
> Map<MediaType, Parser> map = new HashMap<>();
> for (Parser parser : parsers) {
> for (MediaType type : parser.getSupportedTypes(context))
> { map.put(registry.normalize(type), parser); }
> }
> return map;
> }
>
> To recreate - parse any avi file (content type: video/x-msvideo), Only the
> exiftool will by picked up and the ffmpeg parser won't be executed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
