[dependabot]

Bumps tika.version from 3.3.0 to 4.2.0.
Updates org.apache.tika:tika-core from 3.3.0 to 4.2.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

• 9136189 [maven-release-plugin] prepare release 4.2.0-rc2
• 872182e TIKA-4991 windows reset (#3417)
• e68fdf4 fix publish-docs (#3418)
• ec1882f [maven-release-plugin] prepare for next development iteration
• 557418a [maven-release-plugin] prepare release 4.2.0-rc2
• 3a40d6c update CHANGES.txt
• eb8d704 revert to 4.2.0-SNAPSHOT (#3416)
• 265c4a4 TIKA-4984 (#3415)
• 6ab42aa TIKA-4991: wait for the body budget to drain between requests in MaxRequestSi...
• 867344f [maven-release-plugin] prepare for next development iteration
• Additional commits viewable in compare view

Updates org.apache.tika:tika-parsers-standard-package from 3.3.0 to 4.2.0

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}