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

Uwe Schindler edited comment on LUCENE-1391 at 2/13/11 1:49 PM:
----------------------------------------------------------------

I would like to deprecate ShingleMatrix as there is nobody that maintains or 
even understand it. In trunk we should remove it. In my opinion, it's too 
special-case: Look e.g. at the payload stuff in it, it does not even use the 
payload's packages PayloadEncoders.

Any comments? I want to keep this open to possibly deprecate it.

      was (Author: thetaphi):
    I would like to drop ShingleMatrix as there is nobody that maintains or 
even understand it. In trunk we should simply remove it. In my opinion, it's 
too special-case: Look e.g. at the payload stuff in it, it does not even use 
the payload's packages PayloadEncoders.

Any comments? I want to keep this open to possibly deprecate it.
  
> Token type and flags values get lost when using ShingleMatrixFilter
> -------------------------------------------------------------------
>
>                 Key: LUCENE-1391
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1391
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: contrib/analyzers
>    Affects Versions: 2.4, 2.9, 3.0
>            Reporter: Wouter Heijke
>            Assignee: Uwe Schindler
>             Fix For: 3.1, 4.0
>
>         Attachments: LUCENE-1391.patch
>
>
> While using the new ShingleMatrixFilter I noticed that a token's type and 
> flags get lost while using this filter. ShingleFilter does respect these 
> values like the other filters I know.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to