[
https://issues.apache.org/jira/browse/TIKA-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved TIKA-1652.
-------------------------------------
Resolution: Fixed
- Fixed:
{noformat}
bash-3.2$ svn commit -m "Fix for TIKA-1652, TIKA-1426: Tika Server should allow
config file override from the command line like Tika App" CHANGES.txt
tika-server/src/main/java/org/apache/tika/server/TikaServerCli.java
Sending CHANGES.txt
Sending
tika-server/src/main/java/org/apache/tika/server/TikaServerCli.java
Transmitting file data ..
Committed revision 1683966.
bash-3.2$
{noformat}
Note the thing about this is that it creates first the actual parser specified
in tika-config.xml (or a DefaultParser if not specified) when specifying the
Tika config on the command line - as opposed to the environment variable and/or
system property way in which it directly creates the DefaultParser, regardless.
This can cause big time havoc say if you have a parser that decorates
AutoDetectParser like cTAKESParser does. The only way in fact for it to work
correctly with SPI and all the surrounding config magic is to specify the
config from the command line which this fix enables.
> Tika Server should allow config file override from the command line like Tika
> App
> ---------------------------------------------------------------------------------
>
> Key: TIKA-1652
> URL: https://issues.apache.org/jira/browse/TIKA-1652
> Project: Tika
> Issue Type: Bug
> Components: server
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 1.9
>
>
> Tika-app's TikaCLI allows a command line parameter, --config, to override the
> Tika config at the command line. For whatever reason, Tika-server doesn't it
> should since it causes a different control flow for things to get created. I
> first saw this when testing the CTAKESParser (TIKA-1645) in Tika-server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
