[ https://issues.apache.org/jira/browse/TIKA-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612994#comment-17612994 ]
Hudson commented on TIKA-3812: ------------------------------ SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #833 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/833/]) TIKA-3812 add example of how to configure gdal programmatically (tallison: [https://github.com/apache/tika/commit/33c21a3a4c9b4805908600083786eb11c127fd94]) * (edit) tika-parsers/tika-parsers-extended/tika-parsers-extended-integration-tests/src/test/java/org/apache/tika/parser/ocr/TestOCR.java > 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)