Hi,
This sounds like a straight-forward AND query and I bet you can copy/paste
example code for that from some online Lucene tutorials of even from the freely
downloadable code that comes with Lucene in Action.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Mes
My Indexing Code
---
public void index(File indexDir, File dataDir) throws IOException
{
if (!dataDir.exists() || !dataDir.isDirectory()) {
throw new IOException(dataDir + " does not exist or is not a
directory");
}
IndexWrite
Vivek - exactly, all of those are good reasons for index partitioning. In
addition, think about how much of a huge index will be able to fit in RAM/FS
buffers of a single server? At some point you'll have to spread your index
over N servers.
Otis
--
Sematext -- http://sematext.com/ -- Lucene
Can you kill -QUIT right after you fire those 20-30 concurrent
queries? This could tell you/us where those threads are blocking, if they are
blocking, or what they are all doing.
Thanks,
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Michae
On Samstag, 26. Januar 2008, Jay Hill wrote:
> I have added stemming Analyzer to my indexing and searching. I've tried
> both Porter and KStem, have gotten very good results with both with
> KStem being the best. The only problem is that, when analyzing on the
> search end using QueryParser part o
