[
https://issues.apache.org/jira/browse/TIKA-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327721#comment-15327721
]
Thamme Gowda commented on TIKA-1986:
------------------------------------
Regarding documentation for all the parameters:
We can let javadoc auto generate it for us from annotations.
My plan of action is : We can add an additional attribute called
'description' where we can describe the field/param. And then make javadoc
program include these strings {name, required, description} in generated
javadocs. I will make those changes if I receive +1 on this plan.
Regarding why do we need Configurable layer ?:
I think its is not necessary now. My plan was to use it as a [Marker Interface
| https://en.wikipedia.org/wiki/Marker_interface_pattern] to decide whether or
not we need to bind parameters from the configuration. (That if condition could
save some time as the reflections are usually slower as per my knowledge).
Looks like we are going to make most parsers as configurable to some extent. So
we can just ignore the configurable check?
Regarding addition of clazz parameter:
I am not sure what is the use of it, could you please point me to the place
where it was previously discussed?
If you have started working on it, that's fine too.
> 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)
