[
https://issues.apache.org/jira/browse/TIKA-3812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612937#comment-17612937
]
David Pilato commented on TIKA-3812:
------------------------------------
When excluding {{GDALParser}} from the {{{}DefaultParser{}}}, I'm able to get
the same behavior as before.
But I don't know how to add the {{GDALParser}} again with exclusions on the
mime-types you shown using Java code. Which method I should use to mimic the
following?
{{ <parser class="org.apache.tika.parser.gdal.GDALParser">}}
{{ <mime-exclude>image/jpeg</mime-exclude>}}
{{ <mime-exclude>image/png</mime-exclude>}}
{{ <mime-exclude>image/jp2</mime-exclude>}}
{{ <mime-exclude>image/gif</mime-exclude>}}
{{ </parser>}}
> 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)
