Hi Shawn,
Before I was running java 6 compiled code on java 8 when I was getting the
exception. Now the code is compiled using java 8 and things are looking good.
I will monitor if this happens again I can share the code.
thanks,
Snehal
On Apr 9, 2015, at 8:59 PM, Shawn Heisey
It would be better to implement such logic as a separate process - watching
for events or reading from a stream, and then feeding discrete requests (or
modest-sized batches of documents) to Solr in parallel with such processing.
-- Jack Krupansky
On Sat, Apr 11, 2015 at 1:49 AM, vishal dsouza
Hi Ha,
I am the author of the blog post you mention. To your question, I don't
know if the code will work without change (since the Lucene/Solr API has
evolved so much over the last few years), but a more preferred way using
Function Queries way may be found in slides for Timothy Potter's talk
Hello -
I have qf boosting setup and that works well and balanced across different
fields.
However, I have a requirement that if a particular manufacturer is part of the
returned matched documents (say top 20 results) , all those matched docs from
that manufacturer should be bumped to the
It all depends on what you want your scores to look like. Or do you care at
all what the scores look like?
Here's one strategy... Divide the score space into two halves, the upper
half for a preferred manufacturer and the lower have for non-preferred
manufacturers. Step 1: Add 1.0 to the raw
Thanks Jack. I'll give that a whirl.
From: Jack Krupansky jack.krupan...@gmail.com
To: solr-user@lucene.apache.org; Mike L. javaone...@yahoo.com
Sent: Saturday, April 11, 2015 12:04 PM
Subject: Re: Bq Question - Solr 4.10
It all depends on what you want your scores to look like. Or
Thanks Ahmet. There are couple reasons we couldn't index those fields:
1. pricing logic is complex and must be done in ERP.
2. price requires real-time update if indexed
3. those fields could be changed frequently, for example inventory, while we
try to minimize index update because we have a
