You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Dominik Schmidt (Jira)" <ji...@apache.org> on 2026/08/29 19:16:00 UTC

[jira] [Commented] (TIKA-4860) PDF RENDER_PAGES_BEFORE_PARSE ignores maxPages

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

Dominik Schmidt commented on TIKA-4860:
---------------------------------------

 Bounding the pre-parse rendering by maxPages would make both strategies behave the same, which is what I expected. The alternative is documenting that maxPages only applies to text extraction, in case someone relies on RENDER_PAGES_BEFORE_PARSE to render all pages while extracting little text. Which way would you prefer?

>  PDF RENDER_PAGES_BEFORE_PARSE ignores maxPages
> -----------------------------------------------
>
>                 Key: TIKA-4860
>                 URL: https://issues.apache.org/jira/browse/TIKA-4860
>             Project: Tika
>          Issue Type: Bug
>            Reporter: Dominik Schmidt
>            Priority: Major
>
> With "imageStrategy": "RENDER_PAGES_BEFORE_PARSE" the PDF parser renders every page (PageRangeRequest.RENDER_ALL) even when maxPages limits the parse; RENDER_PAGES_AT_PAGE_END honours it. A 10-page PDF with maxPages: 1 renders 10 pages before parse and 1 page at page end. Either bound the pre-parse rendering by maxPages or document that maxPages only applies to text extraction.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)