Sourced from tika-core's changelog.

Release 2.0.0-ALPHA - 01/13/2021

BREAKING CHANGES in 2.0.0

• General

  • OCR is now triggered automatically for PDFs if tesseract is on the user's path see (https://cwiki.apache.org/confluence/display/TIKA/TikaOCR#TikaOCR-disable-ocr) for how to disable OCR.
  • Removed deprecated Metadata keys/properties (TIKA-1974).
  • Removed dangerous calls to read an inputstream or convert to bytes without specifying a charset
  • Parsers can be configured via tika-config.xml on instantiation. We have moved away from configuration via .properties files because of confusion among users. This affects the PDFParser, TesseractOCRParser and the StringsParser.
  • For those parsers that can be configured per parse via a config object passed in through the ParseContext, the config object will only update those fields that the user has modified. The config object will no longer fully reset all settings to the default settings per parse. This has a more intuitive "update the base/configured settings" with what has been changed in the config object.

• tika-parsers

  • The parser modules have been broken into three main modules: tika-parsers-classic, tika-parsers-extended and tika-parsers-advanced. Users may now need to add tika-parsers-extended to tika-app and tika-server to include parsers that used to be included by default (for example: envi, gdal, grib, isatab, netcdf).
  • ChmParser was moved to org.apache.tika.parser.microsoft.chm
  • RTFParser was moved to org.apache.tika.parser.microsoft.rtf

• tika-app

• tika-server

  • tika-server now by default forks a process to isolate the parsing in the forked process (this was called the -spawnChild option in tika-1.x). Clients must now expect that tika-server will restart on OOM, timeouts, crashes or after parsing a large number of files. When this happens tika-server will restand and not receive connections for brief periods. The less robust, legacy behavior of not forking a process is available with "-noFork"

  • tika-server's /metadata endpoint requires tika-server-classic to write XMP/rdf output. This output is not available in tika-server-core.

Release 1.26 - ??/??/????

• The "writeLimit" header now pertains to the combined characters written per container document (and embedded documents) in the /rmeta endpoint in tika-server (TIKA-3325); it no longer functions only

... (truncated)

• 2e83fd4 [maven-release-plugin] prepare release 1.26-rc1
• 1842758 fix rat and imports for 1.26 release
• 8c21fba Update CHANGES.txt for 1.26 release
• da05576 TIKA-3334 -- fix thread safety bug in handling embedded docs in open office p...
• 2b8c9a3 TIKA-3336 -- new zip bombs detect in 1.26-SNAPSHOT compared with 1.25 -- bug,...
• b1e8641 TIKA-3335 -- handle bad xml more robustly when checking for encryption
• b29cce5 TIKA-3244 -- general upgrades for 1.26
• b63072c Merge remote-tracking branch 'origin/branch_1x' into branch_1x
• 8bf65c0 TIKA-3332 -- recursively process the embedded file tree in PDFs.
• 6a27f3e TIKA-3244: update spring
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually