Skip to content

Comments

Fixing the filepath used if the TIKA_JAR_HASH_ALGO env var is used#439

Merged
chrismattmann merged 1 commit intochrismattmann:masterfrom
matt-dies-tenet3:master
Feb 21, 2026
Merged

Fixing the filepath used if the TIKA_JAR_HASH_ALGO env var is used#439
chrismattmann merged 1 commit intochrismattmann:masterfrom
matt-dies-tenet3:master

Conversation

@matt-dies-tenet3
Copy link
Contributor

The TIKA_JAR_HASH_ALGO environment variable can be used to customize which hash algorithm is used for checksums of the Tika jarfile. It's primarily in use for FIPS systems on which using the default hash algorithm (MD5) will raise an exception.

If the user customizes this environment variable currently, it will raise a FileNotFoundError, as the hash file is currently hardcoded to be an .md5 file, and not the filetype that's actually needed.

Fixes #438.

The TIKA_JAR_HASH_ALGO environment variable can be used to customize which hash algorithm is used for checksums of the Tika jarfile. It's primarily in use for FIPS systems on which using the default hash algorithm (MD5) will raise an exception.

If the user customizes this environment variable currently, it will raise a `FileNotFoundError`, as the hash file is currently hardcoded to be an `.md5` file, and not the filetype that's actually needed.
@chrismattmann chrismattmann self-assigned this Feb 21, 2026
@chrismattmann chrismattmann modified the milestone: tika-next Feb 21, 2026
@chrismattmann chrismattmann merged commit 436d5c3 into chrismattmann:master Feb 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TIKA_JAR_HASH_ALGO usage is currently broken

2 participants