On Sat, Nov 26, 2011 at 8:43 PM, Michael Sokolov wrote:
> That's great news! We can't really track trunk, but it looks like this is
> targeted for 3.6, right? As a short-term alternative, I was considering
> using ICUFoldingFilter; this won't preserve some of the finer distinctions,
> but will at
That's great news! We can't really track trunk, but it looks like this
is targeted for 3.6, right? As a short-term alternative, I was
considering using ICUFoldingFilter; this won't preserve some of the
finer distinctions, but will at least sort the accented characters in
with their unaccented
It's checked in, SOLR-2438. Although it's getting some surgery so you
can expect it to morph a bit.
Erick
On Wed, Nov 23, 2011 at 11:22 PM, Michael Sokolov wrote:
> Thanks for confirming that, and laying out the options, Robert.
>
> -Mike
>
> On 11/23/2011 9:03 PM, Robert Muir wrote:
>>
>> hi,
>
On Wed, Nov 23, 2011 at 11:22 PM, Michael Sokolov wrote:
> Thanks for confirming that, and laying out the options, Robert.
>
FYI: Erick committed the multiterm stuff, so I opened an issue for
this: https://issues.apache.org/jira/browse/SOLR-2919
--
lucidimagination.com
Thanks for confirming that, and laying out the options, Robert.
-Mike
On 11/23/2011 9:03 PM, Robert Muir wrote:
hi,
locale sensitive range queries don't work with these filters, only sort,
although erick erickson has a patch that will enable this (the lowercasing
wildcards patch, then you coul
hi,
locale sensitive range queries don't work with these filters, only sort,
although erick erickson has a patch that will enable this (the lowercasing
wildcards patch, then you could add this filter to your multiterm chain).
separately locale range queries and sort both work easily on trunk (wit
I'm using CollectionKeyFilter to sort my documents using the Unicode
root collation, and my documents do appear to be getting sorted
correctly, but I'm getting weird results when performing range filtering
using the sort key field. For example:
ifp_sortkey_ls:["youth culture" TO "youth cultur
