t; Sent: Friday, March 28, 2014 3:14 PM
> To: solr-user@lucene.apache.org
> Subject: Re: commit=false in Solr update URL
>
> On 3/28/2014 1:02 PM, Joshi, Shital wrote:
>> You mean default for openSearcher is false right? So unless I specify
>> commit=false&openSear
Thank you!
-Original Message-
From: Shawn Heisey [mailto:s...@elyograg.org]
Sent: Friday, March 28, 2014 3:14 PM
To: solr-user@lucene.apache.org
Subject: Re: commit=false in Solr update URL
On 3/28/2014 1:02 PM, Joshi, Shital wrote:
> You mean default for openSearcher is false right?
On 3/28/2014 1:02 PM, Joshi, Shital wrote:
You mean default for openSearcher is false right? So unless I specify
commit=false&openSearcher=true in my Solr Update URL the current searcher and
caches will not get invalidated.
If commit=false, openSearcher does not matter -- it's part of a commi
2014 12:48 PM
To: solr-user@lucene.apache.org
Subject: Re: commit=false in Solr update URL
On 3/28/2014 10:22 AM, Joshi, Shital wrote:
> What happens when we use commit=false in Solr update URL?
> http://$solr_url/solr/$solr_core/update/csv?commit=false&separator=|&trim=true&skipLi
On 3/28/2014 10:22 AM, Joshi, Shital wrote:
What happens when we use commit=false in Solr update URL?
http://$solr_url/solr/$solr_core/update/csv?commit=false&separator=|&trim=true&skipLines=2&_shard_=$shardid
1. Does it invalidate all caches? We really need to know this.
2. Nothing
