information.
Am I right?
--Sumukh
Michael McCandless-2 wrote:
>
>
> Since Lucene doesn't represent/store end position for a token, I don't
> think the index can properly represent SYN spanning two positions?
>
> I suppose you could encode this into payloads, and create a
d by another
> word SYN.
>
> If I place SYN after WORD1 with positionIncrement set to 0, WORD2 will
> follow SYN,
> which is incorrect; and the other way round if I place it after WORD2.
>
> If any of you have solved a similar problem, I'd be thankful if you could
> share some light on
> the solution.
>
> Regards,
> Sumukh
>
>
WORD1 with positionIncrement set to 0, WORD2 will
follow SYN,
which is incorrect; and the other way round if I place it after WORD2.
If any of you have solved a similar problem, I'd be thankful if you could
share some light on
the solution.
Regards,
Sumukh