[
https://issues.apache.org/jira/browse/LUCENE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783784#action_12783784
]
Yonik Seeley commented on LUCENE-2094:
--------------------------------------
Preserving gaps from stopword removal isn't always desirable... seems it should
remain an option to enable/disable it.
No biggie if y'all don't agree in Lucene land though - Solr's factory could
just switch between alternate classes to enable/disable position increments.
Solr's query parser (the one that just extends Lucene's QueryParser) always
enables position increments. That allows the true control to rest with the
filters for specific fields.
bq. It is recommeneded to turn it on. But if its off, it must be also disabled
in the QueryParser.
Why? What undesirable things happen if the QueryParser has
enablePositionIncrements(true) with a StopFilter that doesn't produce gaps?
> Prepare CharArraySet for Unicode 4.0
> ------------------------------------
>
> Key: LUCENE-2094
> URL: https://issues.apache.org/jira/browse/LUCENE-2094
> Project: Lucene - Java
> Issue Type: Bug
> Components: Analysis
> Affects Versions: 1.9, 2.0.0, 2.1, 2.2, 2.3, 2.3.1, 2.3.2, 2.3.3, 2.4,
> 2.4.1, 2.4.2, 2.9, 2.9.1, 2.9.2, 3.0, 3.0.1, 3.1
> Reporter: Simon Willnauer
> Assignee: Uwe Schindler
> Fix For: 3.1
>
> Attachments: LUCENE-2094.patch, LUCENE-2094.patch, LUCENE-2094.patch,
> LUCENE-2094.txt, LUCENE-2094.txt, LUCENE-2094.txt
>
>
> CharArraySet does lowercaseing if created with the correspondent flag. This
> causes that String / char[] with uncode 4 chars which are in the set can not
> be retrieved in "ignorecase" mode.
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
