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 2025/12/08 19:06:00 UTC

[jira] [Resolved] (TIKA-4545) Fully integrate new json based deserializer in 4.x

     [ https://issues.apache.org/jira/browse/TIKA-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Allison resolved TIKA-4545.
-------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

I think we've hit good enough on this ticket. Next steps are to remove TikaConfig entirely on TIKA-4553.

> Fully integrate new json based deserializer in 4.x
> --------------------------------------------------
>
>                 Key: TIKA-4545
>                 URL: https://issues.apache.org/jira/browse/TIKA-4545
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>             Fix For: 4.0.0
>
>
> Follow on for TIKA-4544.
> Steps:
>  * Add annotations to components (parsers, etc.) and unit tests to confirm they work (finished this today)
>  * Modify components (parsers etc), at least a few of them so that they are actually configurable. We don't have to modify all, just the most important ones PDFParser, tesseract, MSOffice, and others???
>  * Move to tika-config.json in tika-pipes client/server, tika-async-cli, tika-app and tika-server one by one



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