[jira] [Commented] (TIKA-3093) Enable tika-server to forward parse results to another endpoint

["David Eric Pugh (Jira)" <ji...@apache.org>]

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

David Eric Pugh commented on TIKA-3093:
---------------------------------------

Out of curiosity, is this type of behavior, the "Let me chain a set of interactions together" something that already exists?   

Imagine System A is a CMS, System B is Tika, and System C is Solr...

What if I wanted to do something like "Send a request for a doc by id to system A, have it dig up doc by id in System A, then forward to System B for Extraction, and then forward to System C for storage"..   

Is there an already existing pattern for this that Tika could conform too?   It feels like a pipe of some kind...   



> 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
>            Priority: Major
>
> 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)