tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1336) Provide a Detector JAXRS endpoint
Date Sat, 14 Jun 2014 20:06:02 GMT

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

Hudson commented on TIKA-1336:

SUCCESS: Integrated in tika-trunk-jdk1.6 #46 (See [https://builds.apache.org/job/tika-trunk-jdk1.6/46/])
Update docs for TIKA-1335 TIKA-1336. (mattmann: http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1602618)
* /tika/trunk/CHANGES.txt

> 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

View raw message