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
gt; that runs through an example in more detail.
>
> See:
> http://www.lulu.com/us/en/shop/jack-krupansky/solr-4x-deep-dive-early-access-release-7/ebook/product-21203548.html
>
> -- Jack Krupansky
>
> -Original Message----- From: Alexandre Rafalovitch
> Sent: Sunday, October
detail.
See:
http://www.lulu.com/us/en/shop/jack-krupansky/solr-4x-deep-dive-early-access-release-7/ebook/product-21203548.html
-- Jack Krupansky
-Original Message-
From: Alexandre Rafalovitch
Sent: Sunday, October 12, 2014 7:40 PM
To: solr-user
Subject: What happens if you don't
Hello,
I am working on - yet another - minimal schema, which involves the
settings that are matching defaults (or non-harming if defaults are
used). The one I am trying to figure out now is: positionIncrementGap
We set it to a 100 in all text field definitions. Does it mean it is
NOT some reasona
