[
https://issues.apache.org/jira/browse/TIKA-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17389087#comment-17389087
]
Hudson commented on TIKA-3505:
------------------------------
UNSTABLE: Integrated in Jenkins build Tika ยป tika-main-jdk8 #295 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/295/])
TIKA-3505 -- move maxemitbatchbytes to PipesConfigBase, improve documentation
and remove the unused AsyncClientConfig.java (tallison:
[https://github.com/apache/tika/commit/ead2e752cee9cefaa4ec44aed70b2c77f5732bbe])
* (delete)
tika-core/src/main/java/org/apache/tika/pipes/async/AsyncClientConfig.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesConfigBase.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/async/AsyncConfig.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesServer.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesClient.java
> 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)
