[
https://issues.apache.org/jira/browse/TIKA-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327810#comment-15327810
]
Thamme Gowda commented on TIKA-1986:
------------------------------------
bq. Ok, I figured the setters on the parsers/langdetectors/translators would be
sufficient, no?
That would be okay. How about this http://stackoverflow.com/q/20354943/1506477,
is it better ?
bq. I'll remove the rest of the Configurable code now in that branch, if
that's ok.
Does that mean we have to remove {{void configure(ParseContext context) ;}}
method as well?
I think we will need this call, IMO this is how we can tell a
Parser/translator/langdetector that we are done binding ALL the parameters and
it is now a good time to initialize and possibly raise exception if something
is not okay.
bq. The use is to avoid parameter name conflicts (let's imagine two parsers
have "isLenient", you'd want to be able to tell one parser to be lenient but
the other one not lenient).
I do not see that coming. Each parser is currently getting its own Map of
params so there are no such name conflicts across the parsers with current
implementation [Check this code snippet |
https://github.com/apache/tika/commit/ef1f7b9ec1b39d957450f3b8a11d045579068e6d#diff-6f9d905e5bd46ee7dee173a3d72d2874L568].
The way parameters are specified in XML file is local to each parser (the
{{params}} is wrapped inside {{parser}} tag, which means the map of params is
not global and not shared by other parsers.
> 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)
