[
https://issues.apache.org/jira/browse/TIKA-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327929#comment-15327929
]
Thamme Gowda commented on TIKA-1986:
------------------------------------
Thanks for the reply
bq. Would that go on the individual parser's setters or somewhere else?
Those annotations will go on individual setters/fields. example :
{code}
@Field(description="Executor, example:python")
public String executor
{code}
bq. Do we have use cases where we need to set multiple settings and then
initialize?
Here is my example: imagine we have a parser that has to download a resource
and place it on FS to make it work. It has two params: model 'url' and
'localpath' . We have to wait for both the params to be bound. I recommend to
use {{configure(...)}} method to download the resource (and raise an exception
if it fails). Ofcourse we can otherwise add an {{if(condition)}} in
{{parse(..)}} to do the same, but it is (1) ugly - parse isnt meant to do this.
If there are any issues with settings we let the parse fail early itself before
even attempting to read the input and call parse (2) inefficient - {{if(...)}}
is checked for all incoming documents. Having multiple options would be okay,
we can use whichever is convenient.
bq. if a user is calling the AutoDetectParser programmatically, they have a
single ParseContext for every parser.
Ah! I missed that part. Please suggest what to do in that case?
> support parser parameters with type (int, double, etc) in configuration XML
> file
> --------------------------------------------------------------------------------
>
> Key: TIKA-1986
> URL: https://issues.apache.org/jira/browse/TIKA-1986
> Project: Tika
> Issue Type: Sub-task
> Components: config
> Reporter: Thamme Gowda
> Fix For: 1.14
>
>
> Tika Configuration should be enhanced to support for basic types like int,
> double, boolean, url, file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
