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 2018/07/17 05:17:00 UTC

[jira] [Commented] (TIKA-1982) Add language (and possibly other fields) to /rmeta endpoint

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

Chris A. Mattmann commented on TIKA-1982:
-----------------------------------------

[~tallison@apache.org] any chance we could get this into 1.19?

> Add language (and possibly other fields) to /rmeta endpoint
> -----------------------------------------------------------
>
>                 Key: TIKA-1982
>                 URL: https://issues.apache.org/jira/browse/TIKA-1982
>             Project: Tika
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 1.14
>         Environment: Debian Jessie
> Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
> Tika 1.14 
>            Reporter: Philipp Steinkrueger
>            Assignee: Tim Allison
>            Priority: Minor
>              Labels: features
>
> While the /meta endpoint includes the detected language of a document send to the server, the /rmeta endpoint does not.
> This may apply to other metadata as well. In general, I think, the /meta endpoint should be a subset of /rmeta endpoint so that there is nothing in /meta that is not also available in /rmeta.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)