Fixing the filepath used if the TIKA_JAR_HASH_ALGO env var is used #439
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.md5file, and not the filetype that's actually needed.Fixes #438.