You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2026/01/18 13:09:00 UTC

[jira] [Created] (TIKA-4626) Consider using tika-pipes in the backend for /rmeta and /tika endpoints i n4.x

Tim Allison created TIKA-4626:
---------------------------------

             Summary: Consider using tika-pipes in the backend for /rmeta and /tika endpoints i n4.x
                 Key: TIKA-4626
                 URL: https://issues.apache.org/jira/browse/TIKA-4626
             Project: Tika
          Issue Type: Task
          Components: tika-server
            Reporter: Tim Allison
         Attachments: tika-pipes-integration-plan.md

In 4.x, we're consolidating the forking options to pipes parser. We've removed the "fork the entire server" option in main. We should consider swapping in tika pipes, writing to a tmp file, for /rmeta and /tika.

This will prevent the entire server going down on oom, etc.

If users want crashability, perhaps we add back in a /tika-legacy endpoint?

I'm attaching the plan that I worked out with claude.

We can do the same for /meta and /unpack on a separate ticket.

Any concerns?



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