> public CompletableFuture<NamedList<Object>> requestAsync(SolrRequest<?> request);
NamedList<Object> aside, this looks like a great async API to me. But I would still like some control over the thread pool/executor that's being used. Maybe that doesn't have to be part of the requestAysnc method signature, maybe it could be part of the SolrClient constructor/builder, but then maybe I'll want a different one for reads and writes? So maybe an overloaded version of requestAsync with an extra paramater for a thread pool/executor? - Bram --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
