[
https://issues.apache.org/jira/browse/LUCENE-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787654#action_12787654
]
Steven Rowe commented on LUCENE-2124:
-------------------------------------
bq. this will move the contrib/collation JDK-based components to core
+1
bq. and later we should consider deprecating the alternatives that are not
scalable.
The alternatives don't scale well, true, but they don't result in
non-human-readable index terms, either, so for people that need human-readable
index terms and who have a low-cardinality term set, maybe we should leave the
alternatives in place?
bq. this will move the contrib/collation ICU based components to contrib/iCU,
and this is where I want to bring the unicode 5.2 support.
+1
> move JDK collation to core, ICU collation to ICU contrib
> --------------------------------------------------------
>
> Key: LUCENE-2124
> URL: https://issues.apache.org/jira/browse/LUCENE-2124
> Project: Lucene - Java
> Issue Type: Task
> Components: contrib/*, Search
> Reporter: Robert Muir
> Assignee: Robert Muir
> Priority: Minor
> Fix For: 3.1
>
> Attachments: LUCENE-2124.patch, LUCENE-2124.patch
>
>
> As mentioned on the list, I propose we move the JDK-based
> CollationKeyFilter/CollationKeyAnalyzer, currently located in
> contrib/collation into core for collation support (language-sensitive sorting)
> These are not much code (the heavy duty stuff is already in core,
> IndexableBinaryString).
> And I would also like to move the
> ICUCollationKeyFilter/ICUCollationKeyAnalyzer (along with the jar file they
> depend on) also currently located in contrib/collation into a contrib/icu.
> This way, we can start looking at integrating other functionality from ICU
> into a fully-fleshed out icu contrib.
--
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: [email protected]
For additional commands, e-mail: [email protected]
