On 10/13/10, Erick Erickson wrote:
> Try IndexWrite.addIndexes. I confess that I haven't used that since
> 2.4, but I suspect it's what you want.
>
ok after I started asking around in stackoverflow regarding this
problem. someone was kind enough to give an answer. well sort of.
private int index
I'm not at all sure this is true. We all start by thinking "of course if the
entire
directory were in RAM it would be faster". But lots of work has gone into
making efficient use of RAM for things like caches etc. So it may not
make any difference.
But that doesn't mean you can't try. It's trivial
Try IndexWrite.addIndexes. I confess that I haven't used that since
2.4, but I suspect it's what you want.
Best
Erick
P.S. hijacking. No problem. It's more a matter of helping find topics
rather than who started the conversation.
On Mon, Oct 11, 2010 at 9:37 PM, Yakob wrote:
> well actuall
Start by reading the javadocs for RAMDirectory.
--
Ian.
On Tue, Oct 12, 2010 at 6:39 AM, wrote:
>
> I am also having a similar requirement .But its other way round.
>
> Basically ,I have indexes in FSDirectory and which is transferred to
> another machine on regular basis. But now for the rea
I am also having a similar requirement .But its other way round.
Basically ,I have indexes in FSDirectory and which is transferred to
another machine on regular basis. But now for the reason of faster
searches, it would be better to copy the indexes onto RAM. (RAMDirectory).
Not sure of how it c