tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Allison (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1657) Allow easier XML serialization of TikaConfig
Date Thu, 03 Sep 2015 18:27:46 GMT

    [ https://issues.apache.org/jira/browse/TIKA-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729517#comment-14729517

Tim Allison commented on TIKA-1657:

Hmmm...not sure I see the difference.

I do see a difference between:
#  TIKA-1558-blacklist.xml (where you're saying: do the dynamic loading, but make some crucial

# a dump of the full "effective" config.  (I think this is your second option?)

bq. For service loading, we want both the dynamic flag, and the ignore/warn/throw setting

Y, sorry, have them both.

> Allow easier XML serialization of TikaConfig
> --------------------------------------------
>                 Key: TIKA-1657
>                 URL: https://issues.apache.org/jira/browse/TIKA-1657
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Tim Allison
>            Priority: Minor
>             Fix For: 1.11
>         Attachments: TIKA-1558-blacklist-effective.xml
> In TIKA-1418, we added an example for how to dump the config file so that users could
easily modify it.  I think we should go further and make this an option at the tika-core level
with hooks for tika-app and tika-server.  I propose adding a main() to TikaConfig that will
print the xml config file that Tika is currently using to stdout.
> I'd like to put this into core so that e.g. Solr's DIH users can get by without having
to download tika-app separately.  
> There's every chance that I've not accounted for issues with dynamic loading etc.  Also,
I'd be ok with only having this available in tika-app and tika-server if there are good reasons.
> Feedback?

This message was sent by Atlassian JIRA

View raw message