[jira] [Commented] (TIKA-3071) tika-server's unpacker should pass the parent parser into the parsecontext to be used for inline parsing

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

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

Hudson commented on TIKA-3071:
------------------------------

SUCCESS: Integrated in Jenkins build tika-branch-1x #325 (See [https://builds.apache.org/job/tika-branch-1x/325/])
TIKA-3071 -- OCR on rendered PDF pages should work in /unpack endpoint (tallison: [https://github.com/apache/tika/commit/9fc6cac6dad00082a090ffe0321190da2dd652e6])
* (edit) tika-server/src/main/java/org/apache/tika/server/resource/UnpackerResource.java
* (edit) tika-server/src/test/java/org/apache/tika/server/UnpackerResourceTest.java


> tika-server's unpacker should pass the parent parser into the parsecontext to be used for inline parsing
> --------------------------------------------------------------------------------------------------------
>
>                 Key: TIKA-3071
>                 URL: https://issues.apache.org/jira/browse/TIKA-3071
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Major
>             Fix For: 1.25
>
>
> A small handful of our parsers call other parsers "inline" to handle portions of a document.  By, inline, I mean that they aren't calling the other parsers on attachments or embedded objects; rather, they are calling the parsers on material that is meant to be understood as part of the main document, e.g. TesseractOCRParser on a rendered image of a PDF page.
> On TIKA-3069, [~carina.antunes] pointed out that there is a bit of a disconnect in returning the container file's text in the /unpack/all endpoint with images in PDFs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)