Chris, > the safe thing to do is make sure the first token has > a positionIncrement of "1" and the 'synonyms" after that use an > increment of "0"
Yes it makes sense to have at minimum the first token with positionIncrement=1 I didn't see outside "the vacuum" at all, thank you for explaining. Does it make sense for me to rewrite the ShingleFilter patch to ensure the first token returned always has positionIncrement=1 regardless if enablePositions is true or false? (i'll test too that BooleanQuery works as presumed in my case...) Would such a rewrite of the ShingleFilter patch be a substitute for the custom Analyzer you talk about? (i'm pushing to keep any patch restricted to the ShingleFilter since my gut feeling is still that's where the change in behaviour is). ~mck -- "Between two evils, I always pick the one I never tried before." Mae West | semb.wever.org | sesat.no | sesam.no |
signature.asc
Description: This is a digitally signed message part
