I can't think of a good reason for you to keep the index in memory - The
performance increase (from blazing-fast to super-blazing-fast) just isn't
something your users are going to notice. And it's at the cost of building
the index from scratch every time you start up.
Eventually, for one reason
first thanks for your response Dan,
It I'll be around 5.000 database records with three indexed fields:
id, title(1 line) and description(around three lines). I was even
considering using the in memory feature for faster access but I'm new to
lucene and I'don't know if that I'll cause my proble
If this is a small index and it won't change after install (you are just
using it to search, not to index), place it in a sub-directory of WEB-INF.
If it is a larger index (something you don't want to copy frequently), or it
will change after install, then you shouldn't keep it inside your web
app
What would be the best practice storing the index in a webapp.
I mean in wich folder?
Thanks.
Raul.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
