Thanks Jason. Hope this can be fixed in the next update of SolrJ.
On Thu, Feb 22, 2018 at 10:49 AM, Jason Gerlowski
wrote:
> My apologies Santosh. I added that comment a few releases back based
> on a misunderstanding I've only recently been disabused of. I will
> correct it.
>
> Anyway, Sha
My apologies Santosh. I added that comment a few releases back based
on a misunderstanding I've only recently been disabused of. I will
correct it.
Anyway, Shawn's explanation above is correct. The queueSize parameter
doesn't control batching, as he clarified. Sorry for the trouble.
Best,
Ja
Thanks for the explanation Shawn. Very helpful. I think I got misled by the
JavaDoc text for
*ConcurrentUpdateSolrClient.Builder.withQueueSize*
/**
* The number of documents to batch together before sending to Solr. If
not set, this defaults to 10.
*/
public Builder withQueueSize(
On 2/21/2018 7:41 AM, Santosh Narayan wrote:
> May be it is my understanding of the documentation. As per the
> JavaDoc, ConcurrentUpdateSolrClient
> buffers all added documents and writes them into open HTTP connections.
>
> So I thought that this class would buffer documents in the client side
>
Hi Shawn,
May be it is my understanding of the documentation. As per the
JavaDoc, ConcurrentUpdateSolrClient
buffers all added documents and writes them into open HTTP connections.
So I thought that this class would buffer documents in the client side
itself till the QueueSize is reached and then
On 2/21/2018 1:21 AM, Santosh Narayan wrote:
I'm using ConcurrentUpdateSolrClient to push data into Solr. Currently, I'm
initializing it as follows:
ConcurrentUpdateSolrClientclient = new
ConcurrentUpdateSolrClient.Builder(serverUrl).withThreadCount(100).withQueueSize(50).build();
This works fi
