[
https://issues.apache.org/jira/browse/TIKA-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304061#comment-15304061
]
Tim Allison commented on TIKA-1986:
-----------------------------------
The other major thing...I realize looking back at our discussion. Unless we're
very careful with parameter names, we'll have collisions across parsers and
even Configurables
[link|https://issues.apache.org/jira/browse/TIKA-1508?focusedCommentId=15187805&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15187805].
What would you think of:
context.setParams(SpecificConfigurable.class, Map<String, Param<?>)
context.setParam(SpecificConfigurable.class, String paramName, Param<?>)
> 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)
