Yeah! You did respond earlier. I think it might have been me who failed to
respond.

I think 2.0.0 is fine as is. Still tons of value there. Definitely a lot
more to go coming from my end as soon as I unbury from tasks.

-Nicholas

On Tue, Jul 6, 2021 at 10:52 AM Tim Allison <[email protected]> wrote:

> Hi Nicholas,
>
> I can't remember if I ever responded to this...sorry!  I think scaling
> to multiple tika-servers is a client-side responsibility.  We might
> model it in the tika-server-client module, but I don't think we should
> hold up 2.0.0 for that.
>
> Let me know if you disagree.
>
> Cheers,
>
>       Tim
>
> On Wed, Jun 9, 2021 at 12:08 PM Nicholas DiPiazza
> <[email protected]> wrote:
> >
> > One thing I think is still remaining is how the fetch queue is
> distributed
> > horizontally to multiple tika servers. I don't quite understand how that
> is
> > currently set up.
> >
> >
> >
> > On Wed, Jun 9, 2021 at 11:03 AM Tim Allison <[email protected]> wrote:
> >
> > > Makes sense.  Thank you!  Anything else we need to do?
> > >
> > > On Wed, Jun 9, 2021 at 11:00 AM Nicholas DiPiazza
> > > <[email protected]> wrote:
> > > >
> > > > I would like to make sure the Tika Pipes has one more full end-to-end
> > > test
> > > > case that covers the creation of configurations using the rest API.
> Right
> > > > now the test exists is completely based on Tika run from CLI.
> > > >
> > > > I will work on this asap hopefully something by monday.
> > > >
> > > > On Tue, Jun 8, 2021 at 4:40 PM Tim Allison <[email protected]>
> wrote:
> > > >
> > > > > All,
> > > > >   I plan to run the full regression tests in the next few days.
> What
> > > would
> > > > > you think of going for a 2.0.0 release next week or so?
> > > > >   We should release 1.27 shortly thereafter. I think?
> > > > >
> > > > >   Cheers,
> > > > >
> > > > >       Tim
> > > > >
> > >
>

Reply via email to