I've added the includeSpanScore parameter back in for 5.4, so you might do
better to wait until that's released. Otherwise, the code looks correct to me.
Alan Woodward
www.flax.co.uk
On 19 Oct 2015, at 21:57, William Bell wrote:
> Alan,
>
> Does this code look equivalent? And how do I
Hi Bill,
This looks like an oversight on my part when migrating the payload scoring
queries - can you open a JIRA ticket to add 'includeSpanScore' as an option to
PayloadScoreQuery?
As a workaround, you should be able to use a custom similarity that returns 1
for all scores (see
I opened https://issues.apache.org/jira/browse/LUCENE-6844
Alan Woodward
www.flax.co.uk
On 19 Oct 2015, at 08:49, Alan Woodward wrote:
> Hi Bill,
>
> This looks like an oversight on my part when migrating the payload scoring
> queries - can you open a JIRA ticket to add 'includeSpanScore' as
Alan,
Does this code look equivalent? And how do I change PayLoadScoreQuery to do
a Custom Similarity?
PayloadScoreQuery psq = new PayloadScoreQuery(sq, new
AveragePayloadFunction());
@Override
public Query parse() throws SyntaxError {
if (qstr == null || qstr.length() == 0) return null;
Here is my first stab at it. Thoughts?
Question:
new PayloadTermQuery(new Term(nv[0].substring(1), nv[1]), new
AveragePayloadFunction(), false)
How do I handle the "false" ? It means boolean includeSpanScore
@Override
public Query parse() throws SyntaxError {
if (qstr == null ||
Wondering how to change my payload based on example:
https://lucidworks.com/blog/2014/06/13/end-to-end-payload-example-in-solr/
PayloadTermQuery and BooleanQuery are deprecated in 5.3.x
@Override
public Query parse() throws SyntaxError {
if (qstr == null || qstr.length() == 0) return null;
