We have to clean up packaging. I’m intentionally not bundling all of the fetchers and emitters with the Tika-server jar. We should have the main class add those at runtime or (worse) require users to add them to their class path
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 > > >
