[
https://issues.apache.org/jira/browse/TIKA-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327447#comment-15327447
]
Tim Allison edited comment on TIKA-1986 at 6/13/16 2:06 PM:
------------------------------------------------------------
bq. we may need to start a wiki page to list all params for each parser, so we
will have all configs at one place.
We could do this, but can't we rely on the javadocs for each parser's
getters/setters?
In looking at this again, and remembering [~chrismattmann]'s and [~gagravarr]'s
discussion...do we need the Configurable layer at all? Or, in other words,
what does that buy us over just sending in a ParseContext for each
parse/translation/langdetect, etc?
You've solved the xml configuration issue very elegantly with the JAXB code.
What would you think of changing:
{code}
public void setParam(String key, Param<?> value)
{code}
to
{code}
public void setParam(Class clazz, String key, Param<?> value)
{code} ?
This would accomplish [~chrismattmann]'s suggestion for strict namespacing of
the parameters.
was (Author: [email protected]):
bq. we may need to start a wiki page to list all params for each parser, so we
will have all configs at one place.
In looking at this again, and remembering [~chrismattmann]'s and [~gagravarr]'s
discussion...do we need the Configurable layer at all? Or, in other words,
what does that buy us over just sending in a ParseContext for each
parse/translation/langdetect, etc?
You've solved the xml configuration issue very elegantly with the JAXB code.
What would you think of changing:
{code}
public void setParam(String key, Param<?> value)
{code}
to
{code}
public void setParam(Class clazz, String key, Param<?> value)
{code} ?
This would accomplish [~chrismattmann]'s suggestion for strict namespacing of
the parameters.
> 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)
