lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (LUCENE-2094) Prepare CharArraySet for Unicode 4.0
Date Mon, 30 Nov 2009 19:26:20 GMT

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

Uwe Schindler edited comment on LUCENE-2094 at 11/30/09 7:25 PM:
-----------------------------------------------------------------

Yes it causes. If you have an old index without posincr, the query parser would produce queries
that do not work (we had this issue in 2.9.1 shortly before release, one of the reasons why
it was delayed).

The version flag is for backwards compatibility. If you do not reinex with a new Version constant
you should use the old version constant everywhere and things will play happy together. Even
solr users will have old indexes, and for them there should be a property to specify the version
constant (using this valueOf of enums). Solr should then create all components that require
a version (and since 3.0 *all* analyzers need this) using this property. And then everything
will play wonderful together (anayzers, query parser and so on).

Also Highlighter had a problem with it (same issue with the QP problem in pre-2.9.1)!

      was (Author: thetaphi):
    Yes it causes. If you have an old index without posincr, the query parser would produce
queries that do not work (we had this issue in 2.9.1 shortly before release, one of the reasons
why it was delayed).

The version flag is for backwards compatibility. If you do not reinex with a new Version constant
you should use the old version constant everywhere and things will play happy together. Even
solr users will have old indexes, and for them there should be a property to specify the version
constant (using this valueOf of enums). Solr should then create all components that require
a version (and since 3.0 *all* analyzers need this) using this property. And then everything
will play wonderful together (anayzers, query parser and so on).
  
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message