[ 
https://issues.apache.org/jira/browse/LUCENE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630772#action_12630772
 ] 

Michael Semb Wever commented on LUCENE-1380:
--------------------------------------------

Ok. So there's no way to do it through configuration only.
Would a patch with such a TokenFilter be useful for anybody else other than 
ShingleFilter users? Again i'm a newbie here but i suspect there's no other 
filter (yet) which works _across_ the tokens (and hence breaks down the 
importance of positionIncrement) within a query in the way ShingleFilter does. 
for example from the mailing list from steve:
> On the other hand, I'm not sure how useful position information is for 
> shingles in the general case: they already have relative position info 
> embedded within them.  And how likely is it that one would want to perform a 
> phrase/span query over shingles?  Pretty unlikely, ...

> Patch for ShingleFilter.enablePositions
> ---------------------------------------
>
>                 Key: LUCENE-1380
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1380
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: contrib/analyzers
>            Reporter: Michael Semb Wever
>            Assignee: Karl Wettin
>             Fix For: 2.4
>
>         Attachments: LUCENE-1380.patch, LUCENE-1380.patch
>
>
> Make it possible for *all* words and shingles to be placed at the same 
> position.
> Default is to place each shingle at the same position as the unigram (or 
> first shingle if outputUnigrams=false). That is, each coterminal token has 
> positionIncrement=1 and every other token a positionIncrement=0. 
> This leads to a MultiPhraseQuery where at least one word/shingle must be 
> matched from each word/token. This is not always desired. 
> See http://comments.gmane.org/gmane.comp.jakarta.lucene.user/34746 for 
> mailing list thread.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to