Bump tika from 2.9.2 to 3.2.2

[prudhvigodithi]

Description

Bump tika from 2.9.2 to 3.2.2

Related Issues

Resolves https://nvd.nist.gov/vuln/detail/CVE-2025-54988

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

❌ Gradle check result for 8a5b04d: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for f652414: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for f652414: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for ced203c: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 2aca636: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for b05f9fb: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[prudhvigodithi]

Thanks @cwperks seeing your suggestion prudhvigodithi#29 the issue was with the checksums.

[prudhvigodithi]

Adding @peterzhuamazon @getsaurabh02

[github-actions]

❌ Gradle check result for d9c5755: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for e8c2639: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[github-actions]

❌ Gradle check result for 23d6cd4: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

[prudhvigodithi]

Do we know where to part this Roboto license and notice files?

Fixed the issue, @cwperks and @reta please let me know if we are good to move forward. Thanks

[cwperks]

Given that the checksums being changed had to do with the upgrade from 2.x and 3.0 and then didn't need to be updated again after choosing a dummy font, I think its safe to say that font did not matter. The changes in this PR LGTM.

[github-actions]

✅ Gradle check result for 0fa9041: SUCCESS

[prudhvigodithi]

Adding @andrross

[reta]

Fixed the issue, @cwperks and @reta please let me know if we are good to move forward. Thanks

Thanks a lot @prudhvigodithi , LGTM

[opensearch-trigger-bot]

The backport to 2.19 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-2.19 2.19
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-2.19
# Create a new branch
git switch --create backport/backport-19125-to-2.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5b897117a6b253d9fc2d5b22292b989be1d7af8b
# Push it to GitHub
git push --set-upstream origin backport/backport-19125-to-2.19
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-2.19

Then, create a pull request where the base branch is 2.19 and the compare/head branch is backport/backport-19125-to-2.19.

[opensearch-trigger-bot]

The backport to 3.2 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch/backport-3.2 3.2
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch/backport-3.2
# Create a new branch
git switch --create backport/backport-19125-to-3.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5b897117a6b253d9fc2d5b22292b989be1d7af8b
# Push it to GitHub
git push --set-upstream origin backport/backport-19125-to-3.2
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch/backport-3.2

Then, create a pull request where the base branch is 3.2 and the compare/head branch is backport/backport-19125-to-3.2.

[cwperks]

@prudhvigodithi can we open a backport to 2.19?

[prudhvigodithi]

@prudhvigodithi can we open a backport to 2.19?

Let me create a backport PR.

[prudhvigodithi]

@prudhvigodithi can we open a backport to 2.19?

Here is the backport PR for 2.19 #19242.