[
https://issues.apache.org/jira/browse/TIKA-2490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16351487#comment-16351487
]
Pascal Essiembre commented on TIKA-2490:
----------------------------------------
I still believe the warnings should be there by default for missing libs, or at
a minimum having clear error messages to that effect when documents that would
need them are encountered. Otherwise people may think there is a bug in Tika
or won't know why they get an exception and/or their document was not parsed.
What I would suggest though, is making it easier to turn off for those aware of
those missing dependencies. Why couldn't we use regular logging for those
warnings instead? I think it would align best with expectations if we could
just turn it off by setting a higher log level in log4j configuration (or
whatever logging implementation).
Make sense?
> Turn off stderr warnings in Tika-app
> ------------------------------------
>
> Key: TIKA-2490
> URL: https://issues.apache.org/jira/browse/TIKA-2490
> Project: Tika
> Issue Type: Bug
> Components: app
> Affects Versions: 1.16
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Trivial
> Fix For: 1.17
>
> Attachments: NUTCH-2439-1.17.patch
>
>
> Let's get rid of the stderr messages in tika-app and confirm that users can
> turn off warnings via tika-config.xml
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
