[
https://issues.apache.org/jira/browse/TIKA-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884594#comment-17884594
]
Tim Allison commented on TIKA-4314:
-----------------------------------
That makes sense. Thank you for opening this issue and your thoughtful response.
Let me see what I can do with our current configurability. Please ping if I
don't respond by early next week.
bq. I also recall that this feature worked fine in 2019 when I first started
using Tika.
I _think_ we "fixed" the sorting of the parsers between then and now.
> 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: 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)
