[
https://issues.apache.org/jira/browse/TIKA-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157450#comment-17157450
]
ASF GitHub Bot commented on TIKA-3133:
--------------------------------------
nddipiazza opened a new pull request #326:
URL: https://github.com/apache/tika/pull/326
see https://issues.apache.org/jira/browse/TIKA-3133
and https://issues.apache.org/jira/browse/TIKA-3126
this will add new parameters to `rmeta` rest endpoint
`writeLimit` - max number of characters to store; if < 0, the handler will
store all characters
`maxEmbeddedResources` - number of embedded resources that will be parsed.
if < 0, it will handle unlimited embedded resources.
This will make it so we can control how many embedded docs will be parsed in
a call to rmeta, and how many bytes will be written to the body.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> /rmeta endpoint should not hard code writeLimit and maxEmbeddedResources
> ------------------------------------------------------------------------
>
> Key: TIKA-3133
> URL: https://issues.apache.org/jira/browse/TIKA-3133
> Project: Tika
> Issue Type: Improvement
> Components: server
> Reporter: Nicholas DiPiazza
> Priority: Trivial
>
> When parsing using /rmeta endpoint, you are stuck with the unlimited
> writeLimit and unlimited number of maxEmbeddedResources
> We should add these as optional headers that allow us to control that
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
