Yonik Seeley wrote on 08/12/2006 05:08 AM:
> On 8/11/06, Chuck Williams <[EMAIL PROTECTED]> wrote:
>> 1) a b C D ...results in: _gap_ _gap_ C _gap_ D
>> 2) a B C D ...results in: _gap_ B _gap_ C _gap_ D
>> 3) A b c D ...results in: A _gap_ _gap_ _gap_ D
>>
>> This seems a natural behavior and
On 8/11/06, Chuck Williams <[EMAIL PROTECTED]> wrote:
1) a b C D ...results in: _gap_ _gap_ C _gap_ D
2) a B C D ...results in: _gap_ B _gap_ C _gap_ D
3) A b c D ...results in: A _gap_ _gap_ _gap_ D
This seems a natural behavior and is consistent with the use cases you
describe (which are es
: > 3) A _gap_ b _gap_ c _gap_ D ...results in: A _double_gap_ D
: >
: > ...is that the behavior you are seeing?
: >
: Almost. The only difference is that case 3 has 3 gaps, so it's A
: _triple_gap_ D.
sorry ... brain fart on my part.
: 1. My bulk update code was always generating the positio
Chris Hostetter wrote on 08/11/2006 09:08 AM:
> (using lower case
> to indicate no tokens produced and upper case to indicate tokens were
> produced) ...
>
> 1) a b C _gap_ D ...results in: C _gap_ D
> 2) a B _gap_ C _gap_ D ...results in: B _gap_ C _gap_ D
> 3) A _gap_ b _gap_
: For example, if a field F has values A, B and C the following example
: cases arise:
: 1. A and B both generate no tokens ==> no positionIncrementGaps are
: generated
: 2. A has no tokens but B does ==> just the gap between B and C
: 3. A has tokens but B and C do not ==> both gaps betwe
Hi All,
There is a strange treatment of positionIncrementGap in
DocumentWriter.invertDocument().The gap is inserted between all
values of a field, except it is not inserted between values if the
prefix of the value list up to that point has not yet generated a token.
For example, if a field F
