[
https://issues.apache.org/jira/browse/TIKA-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17563221#comment-17563221
]
Tim Allison commented on TIKA-3812:
-----------------------------------
Ugh. Thank you. I'll look into this. I don't think we have any integration
tests with the scientific parsers. That type of testing would have caught
this. Y. Let me see what else may have changed.
I'm not sure of the path forward. The fix in TIKA-3750 was indeed a fix, and
I'm hesitant to revert that.
> 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.4.2
>
>
> 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)
