[
https://issues.apache.org/jira/browse/TIKA-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raimund Merkert updated TIKA-1047:
----------------------------------
Attachment: patch
This patch is a little bit more complete than the previous one. Metadata can be
be retrieved as either text/csv and application/json.
A single metadata field can be retrieved as either text/csv, application/json,
or text/plain (if single-valued).
I've also added multiple unit tests for the new endpoint (based on
MetadataResourceTest)
I tried to keep the formatting close to the original and fixed the whitespace
issues from the first patch.
The old endpoint MetadataResource is still there, but its functionality is
completely subsumed by this patch.
> 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
> 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
