[
https://issues.apache.org/jira/browse/LUCENE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184904#comment-13184904
]
Robert Muir commented on LUCENE-3690:
-------------------------------------
{quote}
This would be the first back-compat enabled CharFilter. Should the existing
HTMLStripCharFilter instead vanish off the face of the earth?
{quote}
What would be the motivation? Are there some features of the previous one that
don't make sense in this implementation?
I don't think fixing offsets bugs like LUCENE-2208 counts as breaking index
backwards compat, because it won't change search results.
It will just prevent highlighters from throwing exceptions.
(LUCENE-3642 and LUCENE-3668 fixed lots of offset bugs already, we didn't spend
time on any back compat).
> JFlex-based HTMLStripCharFilter replacement
> -------------------------------------------
>
> Key: LUCENE-3690
> URL: https://issues.apache.org/jira/browse/LUCENE-3690
> Project: Lucene - Java
> Issue Type: New Feature
> Components: modules/analysis
> Affects Versions: 3.5, 4.0
> Reporter: Steven Rowe
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
> Attachments: LUCENE-3690.patch, LUCENE-3690.patch
>
>
> A JFlex-based HTMLStripCharFilter replacement would be more performant and
> easier to understand and maintain.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
