[
https://issues.apache.org/jira/browse/TIKA-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031647#comment-14031647
]
ASF GitHub Bot commented on TIKA-1336:
--------------------------------------
GitHub user chrismattmann opened a pull request:
https://github.com/apache/tika/pull/10
Fix for TIKA-1336: initial working detect stream interface, along with u...
...nit tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chrismattmann/tika TIKA-1336
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tika/pull/10.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #10
----
commit b315a1797f2ffb0f83abdcff051d110facf2a128
Author: Chris Mattmann <[email protected]>
Date: 2014-06-14T18:25:21Z
Fix for TIKA-1336: initial working detect stream interface, along with unit
tests.
----
> 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
>
> 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)
