d adding a little more detail about how you're working
> around the problem?
>
> I'm still evaluating our different options so am interested in what you
> did.
>
> Todd
>
> On Mon, Nov 3, 2008 at 2:37 PM, PabloS <[EMAIL PROTECTED]> wrote:
>>
>>
Thanks hossman, but I've already 'solved' the problem without the need to
patch lucene. I had to code a bit around Lucene's visibility restrictions
but I've managed to completely skip the field caching mechanism and add
ehcache to it.
At the moment it seems to be working quite well, although not
thats a lot of sort fields for a large index.
>
> If LUCENE-831 ever gets off the ground you will be able to change the
> cache used, and possibly use something that spills over to disk.
>
> PabloS wrote:
>> Hi,
>>
>> I'm having a similar problem with my applic
Hi,
I'm having a similar problem with my application, although we are using
lucene 2.3.2. The problem we have is that we are required to sort on most of
the fields (20 at least). Is there any way of changing the cache being used?
I can't seem to find a way, since the cache is being accessed using
