[
https://issues.apache.org/jira/browse/LUCENE-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1253:
----------------------------------
Attachment: LUCENE-1253-3x.patch
Patch for the two broekn TokenFilters and refactoring of StopFilter. Also tests
improved. No Version was added, instead the whole thing was done like for
StopFilter by a ctor boolean. Tests were added for both Lucene and Solr. Also
Solr's KeepWordFilter(+Factory) were changed to respect matchVersion for the
CharArraySet. Also synced this filter's factory with the StopFilterFactory
(params, parsing,...).
After commit to 3.x I will port to trunk - oh no :(
> LengthFilter and other TokenFilters that skip tokens ignore relative
> positionIncrement
> --------------------------------------------------------------------------------------
>
> Key: LUCENE-1253
> URL: https://issues.apache.org/jira/browse/LUCENE-1253
> Project: Lucene - Java
> Issue Type: Bug
> Components: contrib/analyzers
> Affects Versions: 2.3.1
> Reporter: Walter Ferrara
> Assignee: Uwe Schindler
> Priority: Minor
> Fix For: 3.1, 4.0
>
> Attachments: LUCENE-1253-3x.patch
>
>
> See for reference:
> http://www.nabble.com/WordDelimiterFilter%2BLenghtFilter-results-in-termPosition%3D%3D-1-td16306788.html
> and http://www.nabble.com/Lucene---Java-f24284.html
> It seems that LengthFilter (at least) could produce a stream in which the
> first Token has a positionIncrement of 0, which make CheckIndex and Luke
> function "Reconstruct&Edit" to generate exception.
> Should something be done to avoid this situation, or could the error be
> ignored (by allowing Term with a position of -1, and relaxing CheckIndex
> checks?)
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
