tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1047) Provide a JAX-RS to detect only the mediatype
Date Sun, 27 Jan 2013 19:05:13 GMT

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

Chris A. Mattmann commented on TIKA-1047:

Error applying patch:

[INFO] -------------------------------------------------------------
[ERROR] /Users/mattmann/tmp/tika1.4/tika-server/src/main/java/org/apache/tika/server/JSONMessageBodyWriter.java:[56,42]
illegal start of type
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
illegal start of type


While running mvn install 
> Provide a JAX-RS to detect only the mediatype
> ---------------------------------------------
>                 Key: TIKA-1047
>                 URL: https://issues.apache.org/jira/browse/TIKA-1047
>             Project: Tika
>          Issue Type: Wish
>          Components: server
>            Reporter: Raimund Merkert
>            Assignee: Chris A. Mattmann
>            Priority: Critical
>             Fix For: 1.4
>         Attachments: patch
> Currently I can use the JAX-RS server to detect the mediatype using the meta endpoint.
The problem I have with this is that I need to send the entire document to get all metadata.

> To detect the mediatype, only a few bytes are often necessary and so I'd like to only
send, say 8K or so, to the server and let it tell me the mediatype.
> In order to accomplish this, it would be good to modify the /meta endpoint to address
the individual fields that might be returned:
> /meta/mediatype
> /meta/author
> /meta/lastModified
> The parts currently following the path could be turned into a query parameter, which
I think is more appropriate anyways (also easier to manipulate with tools like jquery).
> If sufficient data is not available, I'd just return with a BAD_REQUEST.
> If this would be of interest to TIKA, I think I could possibly implement this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message