[dependabot]

Bumps org.apache.tika:tika-core from 3.2.1 to 4.0.0.

Changelog

Sourced from org.apache.tika:tika-core's changelog.

Release 4.3.0 - ???

BREAKING CHANGES AND DEPRECATIONS

• FetcherManager.getFetcher and EmitterManager.getEmitter return a Lease (AbstractComponentManager.getComponent is now acquire); close it when done with the component and anything it returned. Pipes now closes a Closeable fetcher or emitter when a runtime save or delete replaces it (after the last task using it ends) and on graceful shutdown; nothing closed them before. EmittingUnpackHandler takes the emitter, not the EmitterManager (TIKA-5001).

• tika-grpc refuses SaveFetcher with configStoreType memory (FAILED_PRECONDITION): the forks never saw such a fetcher, so every fetch through it failed. Use file or ignite (TIKA-5001).

SERVER, PIPES AND OPERATIONS

• tika-server no longer requires a "server" block in its config file; an absent block means the server defaults, as "server": {} did. A tika-app config, or the documented Docker example { "text-recognizers": [] }, now works as is (TIKA-XXXX).

• The tika-server full and tika-grpc Docker images no longer install ttf-mscorefonts-installer, which downloaded Microsoft's fonts from SourceForge at build time; non-embedded Verdana, Georgia, Trebuchet, Impact, Comic Sans and Arial Black now render with Liberation fonts. The images add the IPA and WenQuanYi fonts, so pages in non-embedded Japanese and Chinese fonts render instead of showing empty boxes or nothing (TIKA-5005).

• The S3 fetcher, emitter and pipes iterator accept credentialsProvider "web_identity" for EKS IAM roles for service accounts (IRSA); the plugin now bundles the AWS STS module it needs (TIKA-5006).

• tika-grpc applies parse-context.timeout-limits and exception-reporting in the server process too, so its backstop for a hung worker no longer falls back to the built-in timeouts. A FetchAndParse call interrupted before the parse finished (server shutdown) closes with UNAVAILABLE; a unary call used to fail with INTERNAL "no value received", a server-streaming call completed with no reply, and a bidirectional stream went on to throw on the closed call. Thanks to Kristian Rickert and Davide Polato (TIKA-5010).

• The GCS fetcher, emitter and pipes iterator no longer require projectId. When it is unset, the client resolves a project from the environment, as it does for its credentials (TIKA-5009).

• The Kafka emitter reports success only once Kafka has acknowledged every record (per acks); a rejected or timed-out record fails the emit instead of being lost silently, and the producer is flushed and closed on shutdown. (TIKA-5008).

• The JDBC emitter is thread-safe: concurrent emits (shared-server mode, several async emitter threads) shared one connection and prepared statement unguarded, mixing values across rows and committing each other's batches (TIKA-5007).

... (truncated)

Commits

• 514e1b3 [maven-release-plugin] prepare release 4.0.0-rc1
• 4e39e07 revert second rc1 attempt
• 7975986 javadocs take 42
• 95d4235 [maven-release-plugin] prepare for next development iteration
• 666289b [maven-release-plugin] prepare release 4.0.0-rc1
• c9f6585 TIKA-4808 - revert aborted 4.0.0-rc1 release commits; fix per-module javadoc ...
• 41183e7 [maven-release-plugin] prepare for next development iteration
• 5dd7fc7 [maven-release-plugin] prepare release 4.0.0-rc1
• 4b231cf TIKA-4808 -- prep CHANGES.txt for release
• 532a685 TIKA-4808 - remove access to the network parser from cli (#3036)
• Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
org.apache.tika:tika-core	[>= 4.1.a, < 4.2]

---

This change is 

[dependabot]

Looks like org.apache.tika:tika-core is up-to-date now, so this is no longer needed.