You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Peter Kronenberg (Jira)" <ji...@apache.org> on 2021/02/08 19:58:00 UTC

[jira] [Comment Edited] (TIKA-3296) Allow tesseract/tessdata path to be specified by environment variables

    [ https://issues.apache.org/jira/browse/TIKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281336#comment-17281336 ] 

Peter Kronenberg edited comment on TIKA-3296 at 2/8/21, 7:57 PM:
-----------------------------------------------------------------

Would like to get some thoughts on this.  I originally implemented this where the environment variables would override what is specified in TesseractOCRConfig.  Only if the environment variables are not specified would the config variables be used.

[~lfcnassif] suggested doing it the other way.  The values in config will override, so you can specify global, system-wide defaults with the environment variables, but then individual systems can override by specifying in config.

Either way can be done in an upward compatible, non-breaking way.  If the environment variables are not specified, everything continues to work as before.

Any suggestions on which way to go?  I'm seeing the benefit of doing it the way Luis suggested.


was (Author: peterkronenberg):
Would like to get some thoughts on this.  I originally implemented this where the environment variables would override what is specified in TesseractOCRConfig.  Only if the environment variables are not specified would the config variables be used.

[~lfcnassif] suggested doing it the other way.  The values in config will override, so you can specify global, system-wide defaults with the environment variables, but then individual systems can override by specifying in config.

Even way can be done in an upward compatible, non-breaking way.  If the environment variables are not specified, everything continues to work as before.

Any suggestions on which way to go?  I'm seeing the benefit of doing it the way Luis suggested.

> Allow tesseract/tessdata path to be specified by environment variables
> ----------------------------------------------------------------------
>
>                 Key: TIKA-3296
>                 URL: https://issues.apache.org/jira/browse/TIKA-3296
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Peter Kronenberg
>            Priority: Trivial
>
> Allow tesseract/tessdata path to be specified by environment variables, overriding whatever is specified in TesseractOCRConfig.properties.  This allows the paths to be specified externally from the jar, allowing for easier execution on multiple systems



--
This message was sent by Atlassian Jira
(v8.3.4#803005)