You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2014/06/14 20:59:01 UTC

[jira] [Resolved] (TIKA-1336) Provide a Detector JAXRS endpoint

     [ https://issues.apache.org/jira/browse/TIKA-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann resolved TIKA-1336.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6

Committed an initial version of the JAX-RS detect interface in r1602617 from GitHub PR #10. Also updated docs on wiki and in README file. You have to give it a hint on CSVs by providing the filename in the Content-Disposition header, but maybe later we can improve our media type detection more on CSV files to differentiate them from text/plain. Thanks to [~gagravarr] and [~kxu] for motivation in getting this done.

> Provide a Detector JAXRS endpoint
> ---------------------------------
>
>                 Key: TIKA-1336
>                 URL: https://issues.apache.org/jira/browse/TIKA-1336
>             Project: Tika
>          Issue Type: Improvement
>          Components: detector, server
>    Affects Versions: 1.5
>            Reporter: Nick Burch
>            Assignee: Chris A. Mattmann
>             Fix For: 1.6
>
>
> As identified in TIKA-1335, the Tika Server now has an endpoint which will tell you what Detectors are available to it, but not one that will trigger detection. That means your only way to do detection is to request the metadata, and check the content type, but that isn't always as accurate as an explicit detection call (eg if a general parser picks up the file)
> We should therefore add in a new endpoint that just does the detection



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