[
https://issues.apache.org/jira/browse/TIKA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947368#comment-16947368
]
Hudson commented on TIKA-2941:
--
SUCCESS: Integrated in Jenkins build tika-branch-1x #241 (See
[
https://issues.apache.org/jira/browse/TIKA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947364#comment-16947364
]
Hudson commented on TIKA-2941:
--
SUCCESS: Integrated in Jenkins build Tika-trunk #1705 (See
[
[
https://issues.apache.org/jira/browse/TIKA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947353#comment-16947353
]
Hudson commented on TIKA-2941:
--
UNSTABLE: Integrated in Jenkins build tika-2.x-windows #460 (
[
https://issues.apache.org/jira/browse/TIKA-2941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16947341#comment-16947341
]
Bob Paulin commented on TIKA-2941:
--
Looks like there's a configuration option that does e
Ramesh Thumati created TIKA-2960:
Summary: Detected 1 vulnerable components: [ERROR]
com.fasterxml.jackson.core:jackson-databind:jar:2.9.8
Key: TIKA-2960
URL: https://issues.apache.org/jira/browse/TIKA-2960
I think it is not related to file size, but maximum record size handled by
POI. It is a protection against OutOfMemoryErrors. I increased this limit
to 10M because was seeing many of them. I do not know if it is configurable
in tika server.
Regards,
Luis
Em ter, 8 de out de 2019 17:46, Chris Matt
Hi,
Thanks for your question. Yes, the same way you set the byte size property in
Tika-App (I think through
parser configuration) is how you would do it for Tika-Server. You would just
start the Tika Server yourself
with a custom config file that set this property and then start it on the
d
