[
https://issues.apache.org/jira/browse/TIKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17389119#comment-17389119
]
Hudson commented on TIKA-3505:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #296 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/296/])
TIKA-3505 -- general clean up and ensure that PipesResource turns
maxemitbatchbytes to zero -- everything must be emitted through the forked
process. (tallison:
[https://github.com/apache/tika/commit/73222dd87e3c78ff1eca45c0c05cffe985b3b67d])
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesClient.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesServer.java
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/resource/PipesResource.java
* (edit)
tika-server/tika-server-core/src/test/java/org/apache/tika/server/core/TikaPipesTest.java
* (edit) tika-server/tika-server-core/pom.xml
> Move maxForEmitBatchBytes into PipesConfigBase
> ----------------------------------------------
>
> Key: TIKA-3505
> URL: https://issues.apache.org/jira/browse/TIKA-3505
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Trivial
> Fix For: 2.0.1
>
>
> If the extracted text is < maxForEmitBatchBytes, the text will be sent back
> to the pipes client so that it can be batched and then emitted. If the
> extracted text is >= this value, it will be emitted directly from the
> PipesServer with no batching.
> This applies to both a pipes process and an async process and should be in
> PipesConfigBase, not only in AsyncConfig.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
