heh, i just don't think thats the typical case. Its definitely extreme.
Even still, in many cases using the filesystem (properly warmed) with
compression might still be better. It depends how you are measuring
latency. storing your whole index in gigabytes of heap ram without any
compression on a
WHOOPS.
First sentence was, until just before I clicked 'send',
"Hardware has .5T of RAM. Index is relatively small (20g) ..."
On Thu, Feb 12, 2015 at 4:51 PM, Benson Margulies wrote:
> Robert,
>
> Let me lay out the scenario.
>
> Hardware has .5T of Index is relatively small. Application pro
Robert,
Let me lay out the scenario.
Hardware has .5T of Index is relatively small. Application profiling
shows a significant amount of time spent codec-ing.
Options as I see them:
1. Use DPF complete with the irritation of having to have this
spurious codec name in the on-disk format that has
On Thu, Feb 12, 2015 at 8:51 AM, Benson Margulies wrote:
> On Thu, Feb 12, 2015 at 8:43 AM, Robert Muir wrote:
>
>> Honestly i dont agree. I don't know what you are trying to do, but if
>> you want file format backwards compat working, then you need a
>> different FilterCodec to match each lucene
rom: Benson Margulies [mailto:ben...@basistech.com]
> Sent: Thursday, February 12, 2015 11:34 AM
> To: java-user@lucene apache. org
> Subject: Re: A codec moment or pickle
>
> Based on reading the same comments you read, I'm pretty doubtful that
> Codec.getDefault() is going
Uwe Schindler
> >> H.-H.-Meier-Allee 63, D-28213 Bremen
> >> http://www.thetaphi.de
> >> eMail: u...@thetaphi.de
> >>
> >>
> >>> -Original Message-
> >>> From: Benson Margulies [mailto:bimargul...@gmail.com]
> >>&g
ybe try it out, was just an idea :-)
>>
>> Uwe
>>
>> -
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>>
>>> -Original Message-
>>> From: Benson Marg
u...@thetaphi.de
>
>
>> -Original Message-
>> From: Benson Margulies [mailto:bimargul...@gmail.com]
>> Sent: Thursday, February 12, 2015 2:11 AM
>> To: java-user@lucene.apache.org
>> Subject: A codec moment or pickle
>>
>> I have a class that ext
AM
> To: java-user@lucene.apache.org
> Subject: A codec moment or pickle
>
> I have a class that extends FilterCodec. Written against Lucene 4.9, it uses
> the
> Lucene49Codec.
>
> Dropped into a copy of Solr with Lucene 4.10, it discovers that this codec is
> read-only in 4.10.
I have a class that extends FilterCodec. Written against Lucene 4.9,
it uses the Lucene49Codec.
Dropped into a copy of Solr with Lucene 4.10, it discovers that this
codec is read-only in 4.10. Is there some way to code one of these to
get 'the default codec' and not have to chase versions?
--
10 matches
Mail list logo
