You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Nick Burch (JIRA)" <ji...@apache.org> on 2014/03/03 21:06:28 UTC

[jira] [Commented] (TIKA-1254) No warning when Tika does not find a parser.

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

Nick Burch commented on TIKA-1254:
----------------------------------

This is as expected - it's assumed that if you're depending on only tika-core then you're supplying all your own custom parsers, or just using the detection parts

If you ask TikaConfig nicely, it'll tell you the parsers it has registered, and the mimetypes it can handle parsing for. See tika-app for an example of how to do that. You're best off adding that sort of check to your own code if you can risk missing key parsers, as only you know which mime types matter for your use case

> No warning when Tika does not find a parser.
> --------------------------------------------
>
>                 Key: TIKA-1254
>                 URL: https://issues.apache.org/jira/browse/TIKA-1254
>             Project: Tika
>          Issue Type: Wish
>            Reporter: Ankit Gupta
>            Priority: Minor
>
> When using Tika using Gradle or Maven, if the dependency is specified only on tika-core and not on tika-parsers, then there is no warning to let you know that there is a library missing and the function returns an empty string.



--
This message was sent by Atlassian JIRA
(v6.2#6252)