Slave replicating partially before write operation completes on master

Hi Team, We have below critical issue in our project. Please suggest how to fix this issue. Whenever indexing happening on master, slave replicating documents partially. Due to this, search results on website are showing wrongly. During indexing on master, I have observed below versions on

Re: Enable https for Solr

Hi Shawn, The same problem is happening in both SolrJ and SimplePostTool. I got the same error for both. Regards, Edwin On 22 April 2017 at 20:25, Shawn Heisey wrote: > On 4/22/2017 1:45 AM, Zheng Lin Edwin Yeo wrote: > > Hi Steve, > > > > Yes, I have set that in

Re: Modify solr score

This may be suggesting a solution that is too experimental or using the wrong hammer for the job, but to me it sounds like you could use “payloads” for this type of ranking of terms relationship to a document. See SOLR-1485 for the recent work I’ve been doing (and aim to get committed

Re: Data Changes Logging

Do a range search on that field with the desired date range. Request rows=0. Compare the numFound to the total docs. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Apr 22, 2017, at 8:40 AM, Rick Leir wrote: > > Preeti, >

Re: Data Changes Logging

Preeti, Suppose you have a field named 'modifiedDate' and you update it when you change the 'column' (i assume you mean some field in your document). Then you need to decide how often to check for alerts. When you check for an alert you would do a select with a bit of date math to see how many

Re: Enable https for Solr

On 4/22/2017 1:45 AM, Zheng Lin Edwin Yeo wrote: > Hi Steve, > > Yes, I have set that in solr.in.cmd. The *client* is where the certificate validation problem is happening. The client (you said SolrJ, but the stacktrace indicates it is SimplePostTool) is what needs the keystore-related system

Re: Enable https for Solr

Hi Steve, Yes, I have set that in solr.in.cmd. Regards, Edwin On 22 April 2017 at 01:51, Steve Rowe wrote: > Edwin, > > Did you set the required keystore/truststore/password system properties? > See the example at