[
https://issues.apache.org/jira/browse/TIKA-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091668#comment-17091668
]
Tim Allison edited comment on TIKA-3093 at 4/24/20, 4:13 PM:
-------------------------------------------------------------
I think using both Solr and Elastic as targets in unit tests would help us make
this generalizable...enough.
* How do users specify the endpoint? Config file into tika-server upon
initialization or via headers?
* How do we handle unit tests? MockSolr/MockElastic servers?
* How do we handle security/username/password in sending the docs to the target
endpoint?
* How can we allow simple manipulations of the standard /rmeta json output?
was (Author: [email protected]):
I think using both Solr and Elastic as targets in unit tests would help us make
this generalizable...enough.
* How do we handle unit tests? MockSolr/MockElastic servers?
* How do we handle security/username/password in sending the docs to the target
endpoint?
* How can we allow simple manipulations of the standard /rmeta json output?
> 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)
