[jira] [Commented] (TIKA-2978) maxMainMemoryBytes should be long on

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Commented] (TIKA-2978) maxMainMemoryBytes should be long on

Tim Allison (Jira)

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

Christian Ribeaud commented on TIKA-2978:

As a workaround, you might extend {{PDFParserConfig}} to return the value you want to specify (bypassing so the _setter_).

> maxMainMemoryBytes should be long on
> -------------------------------------
>                 Key: TIKA-2978
>                 URL: https://issues.apache.org/jira/browse/TIKA-2978
>             Project: Tika
>          Issue Type: Improvement
>          Components: config, parser
>    Affects Versions: 1.22
>            Reporter: Christian Ribeaud
>            Priority: Major
> [PDFParserConfig|https://github.com/apache/tika/blob/master/tika-parsers/src/main/java/org/apache/tika/parser/pdf/PDFParserConfig.java] should handle _ maxMainMemoryBytes_ as *long*. The getter returns a *long*. However the setter requests an *int*. Why this inconsistency?

This message was sent by Atlassian Jira