[jira] [Comment Edited] (TIKA-3812) Parser Order: image get parsed by GDALParser instead of TesseractOCRParser

["Tim Allison (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TIKA-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612638#comment-17612638 ] 

Tim Allison edited comment on TIKA-3812 at 10/4/22 2:51 PM:
------------------------------------------------------------

Ugh [~dadoonet]...sorry.  Are you using tika-parsers-scientific-package?  Can you share the contents of the metadata object after the test -- which parsers touched the file?


was (Author: tallison@mitre.org):
Ugh [~dadoonet]...sorry.  Are you using tika-scientific-parsers?  Can you share the contents of the metadata object after the test -- which parsers touched the file?

> Parser Order: image get parsed by GDALParser instead of TesseractOCRParser
> --------------------------------------------------------------------------
>
>                 Key: TIKA-3812
>                 URL: https://issues.apache.org/jira/browse/TIKA-3812
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 2.4.1
>            Reporter: Eugen Caruntu
>            Priority: Minor
>             Fix For: 2.5.0
>
>         Attachments: parser-diffs.tgz
>
>
> The selected parser seems to be different in 2.4.1. For example sending an image (jpg/png) that was previously (2.4.0) processed by TesseractOCRParser, now gets parsed by GDALParser.
> Seems that when multiple parsers support same file types, the selected parser depends on the order in which they get loaded.
> For example the GDALParser, ImageParser and TesseractOCRParser all support image/jpeg, image/png, image/gif ...
> A recent change is reversing the parser order (TIKA-3750).
> Re-configuring the GDALParser by excluding the image mime types might work, but there could be other duplicated parsers.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)