[
https://issues.apache.org/jira/browse/TIKA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276833#comment-14276833
]
Tim Allison commented on TIKA-1509:
-----------------------------------
Y, I agree on compatibility. How about we add a "tika_2_0_dev" attribute
towards the top of the Tika Config XML file. If that ="true", then the new
behavior will be executed.
How about adding the different strategies into CompositeParser and allow the
user to select the strategy via an enum? This could be passed through
AutoDetectParser, and the default/unspecified would be
COMPOSITE_STRATEGY.CLASSIC or similar.
It sounds like the recommended path ahead, then, is to add small patches to
trunk as we go and let the users opt in to the new behavior. So, we won't
create a TIKA-1509 branch, and we won't branch a 1_8 and develop on trunk _and_
1_8. Once we numerically approach 2.0, we can make any breaking changes that
are necessary.
> Create configurable strategies for composite parsers
> ----------------------------------------------------
>
> Key: TIKA-1509
> URL: https://issues.apache.org/jira/browse/TIKA-1509
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
>
> Several parsers can handle the same mime type, and we are currently ordering
> which parser is chosen (roughly) by the alphabetic order of the parser class
> name.
> Let's allow users to configure strategies for picking parsers.
> ***NOTE: this description is just a place holder, will edit later.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
