[
https://issues.apache.org/jira/browse/LUCENE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184986#comment-13184986
]
Robert Muir commented on LUCENE-3690:
-------------------------------------
{quote}
There are differences in the behavior, but I guess all of these could be
characterized as bug fixes:
{quote}
This sounds awesome!
{quote}
Good point. Should I make it a new Lucene feature on 3.X? That is, should I
remove Solr's HTMLStripCharFilter and have it refer to a new Lucene
HTMLStripCharFilter?
{quote}
I think so.
If you want to, you can make it package-private + deprecated inside
o.a.solr.analysis. The Solr factory could respect
the luceneMatchVersion parameter for backwards compatibility, and instantiate
the old version in that case.
So you would then move the old charfilter from modules/analysis to the same
place in trunk, too... its purely a solr
back-compat issue. For lucene users its just a new feature and they don't see
any of this.
This is what we did with Synonyms.
> 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]
