You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2021/01/26 20:35:00 UTC
[jira] [Resolved] (TIKA-3093) Enable tika-server to forward parse
results to another endpoint
[ https://issues.apache.org/jira/browse/TIKA-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Allison resolved TIKA-3093.
-------------------------------
Fix Version/s: 2.0.0
Assignee: Tim Allison
Resolution: Fixed
Fixed as part of TIKA-3226 – add a pipes modules that includes fetchers and emitters.
> Enable tika-server to forward parse results to another endpoint
> ---------------------------------------------------------------
>
> Key: TIKA-3093
> URL: https://issues.apache.org/jira/browse/TIKA-3093
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
> Fix For: 2.0.0
>
> Attachments: test_recursive_embedded.docx.json
>
>
> bq. I see the "send the results to a remote network service" thing as probably being separate from the Content Handler.
> The above is from [~nick] on TIKA-2972.
> It would be useful to allow users to forward the results of parsing to another endpoint. For example, a user could specify a Solr URL/update/json/docs handler or an elastic /<index>/_doc/<_id>
> We may want to allow users to do custom mapping before redirecting to another URL, whitelisting/blacklisting of metadata keys, etc.
> I'd propose using /rmeta as the basis for this.
> cc [~ehatcher] and [~dadoonet].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)