> > I see, thanks for the answer! There seem be some way to have a timeout > > in the Lucene API, but it doesn't look very straightforward... should > > I open a separate issue to track that? > > Yes
Ok, I'll do that > Are you able to contribute for this additional feature? Perhaps in the future but not immediately no unfortunately... > The client side also streams - so it returns results until it hits the > bad syntax and throws an exception. Ok > The only way to have the server return an HTTP status code 4xx is run he > query to completion, buffering the results, before starting the response > so it can send the status code. That is a big impact on large results. Sure, this doesn't look like a compelling option... Thanks! -- Elie
