After your last request, this is the next on my list... how did you get ahold of my list?!
There’s an alpha async parser that persists requests and emit data in an h2 db. I have to wire that into the async handler in Tika-server. I’d normally welcome the help but this is all so new, lemme take a look. On Wed, Apr 21, 2021 at 1:17 PM Giovanni De Stefano <[email protected]> wrote: > Hello all, @TimAllison 😊 > > I am using tika-server-classic. > I post to AsyncResource: let’s say 100 AsyncRequest with each 1 > FetchEmitTuple. I receive 100 ok added responses. > > AsyncEmitter starts polling each of those 100 FetchEmitTuple and begins > processing: when AsyncParser fails, the server restarts and AsyncEmitter > ends up with an empty queue… > > Do you think it would be a sensible feature persisting the queue to > survive restarts? > > I also looked at JdbcFetchIterator but: > > 1. It’s not enabled in tika-server-classic > 2. TikaConfig supports only one (the first) iterator > > I know I took a leap of faith adopting 2.0.0 now, and I would appreciate > if you could share the current line of thought on those subjects and > perhaps an ETA 😊 . I am obviously willing to contribute as well. > > Thank you, > Giovanni > > >
