Re: commit=false in Solr update URL

2014-03-29 Thread Erick Erickson
] 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=falseopenSearcher=true in my Solr Update URL the current

Re: commit=false in Solr update URL

2014-03-28 Thread Shawn Heisey
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=falseseparator=|trim=trueskipLines=2_shard_=$shardid 1. Does it invalidate all caches? We really need to know this. 2. Nothing

RE: commit=false in Solr update URL

2014-03-28 Thread Joshi, Shital
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=falseseparator=|trim=trueskipLines=2_shard_=$shardid 1

Re: commit=false in Solr update URL

2014-03-28 Thread Shawn Heisey
On 3/28/2014 1:02 PM, Joshi, Shital wrote: You mean default for openSearcher is false right? So unless I specify commit=falseopenSearcher=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

RE: commit=false in Solr update URL

2014-03-28 Thread Joshi, Shital
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? So