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

Tim Allison commented on TIKA-4181:
-----------------------------------

Sorry, I shouldn't have responded on the dev list. We should discuss this here.

To confirm, this would be an alternative to tika-server?

The response for /pipes would be pipes/parse status -- did the 
fetch->parse->emit work. The response for /async would be "got the request" or 
"too many" requests.

I have a bunch of time on my hands :P and would be happy to chat via google 
meet or similar if that would be more efficient.

> Grpc + Tika Pipes - pipe iterator and emitter
> ---------------------------------------------
>
>                 Key: TIKA-4181
>                 URL: https://issues.apache.org/jira/browse/TIKA-4181
>             Project: Tika
>          Issue Type: New Feature
>          Components: tika-pipes
>            Reporter: Nicholas DiPiazza
>            Priority: Major
>
> Add full tika-pipes support of grpc
>  * pipe iterator
>  * fetcher
>  * emitter
> Requires we create a service contract that specifies the inputs we require 
> from each method.
> Then we will need to implement the different components with a grpc client 
> generated using the contract.
> This would enable developers to run tika-pipes as a persistently running 
> daemon instead of just a single batch app, because it can continue to stream 
> out more inputs.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to