Hi,
bq. setting non-zero for dates/ints/longs does not
I am not 100% sure, but position increment gap is set to 1 for
FieldMaskingSpanQuery to work.
On Monday, October 13, 2014 5:37 PM, Alexandre Rafalovitch
wrote:
On 13 October 2014 10:08, Shawn Heisey wrote:
> I don't think it needs to be
Original Message-
From: Alexandre Rafalovitch
Sent: Monday, October 13, 2014 10:37 AM
To: solr-user
Subject: Re: What happens if you don't set positionIncrementGap
On 13 October 2014 10:08, Shawn Heisey wrote:
I don't think it needs to be defined, but it can be thought of as
helpful
On 13 October 2014 10:08, Shawn Heisey wrote:
> I don't think it needs to be defined, but it can be thought of as
> helpful to explicitly state a value in the example even if that value is
> in fact the default, so a new user doesn't have to wonder what the value
> is on those field types.
I thi
On 10/12/2014 8:33 PM, Alexandre Rafalovitch wrote:
> Thanks Jack, this makes sense for text.
>
> But what about for the ints, dates, and floats? The package web page
> does not seem to say anything. And your book (at least in my release
> 7) is also only talking about the text field. Yet, we seem
Thanks Jack, this makes sense for text.
But what about for the ints, dates, and floats? The package web page
does not seem to say anything. And your book (at least in my release
7) is also only talking about the text field. Yet, we seem to have a
need to define the value (still as zero) in the sch
Read the Lucene analysis package summary section entitled "Field Section
Boundaries":
http://lucene.apache.org/core/4_10_0/core/org/apache/lucene/analysis/package-summary.html
TL;DR - if you leave it as the default, then a word at the end of one
section and a word at the start of the next secti
