You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2023/06/10 18:26:00 UTC

[jira] [Commented] (TIKA-4063) PipesServer should not initialize emitters if the server will never emit results

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

Hudson commented on TIKA-4063:
------------------------------

SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk11 #1103 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk11/1103/])
TIKA-4063 -- skip initialization of emitter in PipesServer if emitting from the server has been turned off. (tallison: [https://github.com/apache/tika/commit/1da3b76dee4aef19f0019eea0210a58fbaabcff2])
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesServer.java


> PipesServer should not initialize emitters if the server will never emit results
> --------------------------------------------------------------------------------
>
>                 Key: TIKA-4063
>                 URL: https://issues.apache.org/jira/browse/TIKA-4063
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Tim Allison
>            Priority: Trivial
>             Fix For: 2.8.1
>
>
> As a safety valve for large extracts, we enabled direct emitting of data from the PipesServer, without passing the data back to the PipesClient to be emitted by the main process.
> If a user has disabled emitting from the PipesServer, we should not initialize the emitters in the PipesServer.
> I ran into this recently because sqlite does not like multiple processes interacting with the same db afaict.  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)