[
https://issues.apache.org/jira/browse/TIKA-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556552#comment-17556552
]
Hudson commented on TIKA-3794:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #649 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/649/])
TIKA-3794 -- Fix bug that prevented specification of rendered image type via
http header in the PDFParser. (tallison:
[https://github.com/apache/tika/commit/213747d7e6f45f3e30cf40dcce8b2135f9d52bc2])
* (add)
tika-server/tika-server-standard/src/test/resources/test-documents/testColorRendering.pdf
* (edit)
tika-server/tika-server-core/src/test/java/org/apache/tika/server/core/CXFTestBase.java
* (edit) CHANGES.txt
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-pdf-module/src/main/java/org/apache/tika/parser/pdf/PDFParser.java
* (edit)
tika-server/tika-server-standard/src/test/java/org/apache/tika/server/standard/UnpackerResourceTest.java
* (edit)
tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-pdf-module/src/main/java/org/apache/tika/parser/pdf/PDFParserConfig.java
> ocrImageType is not configurable via headers in tika-server
> -----------------------------------------------------------
>
> Key: TIKA-3794
> URL: https://issues.apache.org/jira/browse/TIKA-3794
> Project: Tika
> Issue Type: Bug
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Minor
> Fix For: 2.4.2
>
>
> If a user sets the OCRImageType as a string, we aren't adding it to the
> "userConfigured" set which is used to decide what to modify during a clone
> operation of the PDFParserConfig.
> This happens when users try to specify an ocr image type via headers in
> tika-server. The fix is trivial.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
