[TIKA-3141] LINUX - Tika shouldn't throw an exception for an empty TIKA_CONFIG environment variable value

• Type: Bug
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 1.20
• Component/s: config

Environment

Any Linux distro.  I'm running the bash shell.  Not sure about other platforms.

• Assignee: Unassigned
• Reporter: Josh Burchard
• Created: 16/Jul/20 22:42
• Updated: 04/Oct/22 17:14
• Resolved: 04/Oct/22 17:14

Description

On my Linux box I configure Tika using the TIKA_CONFIG environment variable to point the Tika server at my config.xml file.   Sometimes, however, I want to clear this variable to use the default config and I noticed that Tika will throw an exception and abort if I do the following:

export TIKA_CONFIG=''

Seems like a case that should be handled just by ignoring the empty value (i.e., there's no config to be used so go with the default)  or at the most, log a warning that the variable was detected but it's value is empty, but still carry on using the default config.

Exception in thread "main" java.lang.RuntimeException: Unable to access default configuration
{{ at org.apache.tika.config.TikaConfig.getDefaultConfig(TikaConfig.java:410)}}
{{ at org.apache.tika.Tika.<init>(Tika.java:116)}}
{{ at org.apache.tika.server.TikaServerCli.main(TikaServerCli.java:125)}}
Caused by: org.apache.tika.exception.TikaException: Specified Tika configuration not found:
{{ at org.apache.tika.config.TikaConfig.getConfigInputStream(TikaConfig.java:317)}}
{{ at org.apache.tika.config.TikaConfig.<init>(TikaConfig.java:254)}}
{

{ at org.apache.tika.config.TikaConfig.getDefaultConfig(TikaConfig.java:405)}

}