Re: Data from 4.10 to 6.5.1

Thanks for the reply. Sure will pay attention. Indeed our approach was also to use the latest managed schema and configs only and add our custom schema from the old version. Luckily we have only one shard of data and others are replica only and also we are not using any fields types ( pint,

Re: The unified highlighter html escaping. Seems rather extreme...

Hi, I'm not so sure about the escaping, but to control how much text is returned as context around the highlighted frag, you can set the following in solrconfig.xml. 200 This will limit the fragments to consider for highlight to around 200 characters, and it will not return the whole chunk of

Re: StandardDirectoryReader.java:: applyAllDeletes, writeAllDeletes

After reading some more code it seems if we are sure that there are no deletes in this segment/index, then setting applyAllDeletes and writeAllDeletes both to false will achieve similar to what I was getting in 4.5.0 However, after I read the comment from IndexWriter::DirectoryReader

TLog for non-Solrcloud scenario

Hi, SolrCloud document mentions: "The sync can be tunable e.g. flush vs fsync by default can protect against JVM crashes but not against power failure and can be much faster " Does it mean that flush protects against JVM crash but not power

Re: Solr uppercase inside phrase query

Many thank. I will try it. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-uppercase-inside-phrase-query-tp4337403p4337787.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Solr uppercase inside phrase query

Many thank. I will try it -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-uppercase-inside-phrase-query-tp4337403p4337786.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: StandardDirectoryReader.java:: applyAllDeletes, writeAllDeletes

Thanks Michael and Shawn for the detailed response. I was later able to pull the full history using gitk; and found the commits behind this patch. Mike: So, in solr 4.5.0 ; some earlier developer has added code and config to set applyAllDeletes to false when we reindex all the data. At the

Re: StandardDirectoryReader.java:: applyAllDeletes, writeAllDeletes

Sorry, yes, that commit was one of many on a feature branch I used to work on LUCENE-5438, which added near-real-time index replication to Lucene. Before this change, Lucene's replication module required a commit in order to replicate, which is a heavy operation. The writeAllDeletes boolean

Re: StandardDirectoryReader.java:: applyAllDeletes, writeAllDeletes

On 5/27/2017 8:35 PM, Nawab Zada Asad Iqbal wrote: > I am looking at following change in lucene-solr which doen't mention any > JIRA. How can I know more about it? > > "1ae7291 Mike McCandless on 1/24/16 at 3:17 PM current patch" The reason that there's no Jira issue mentioned is that the commit