Re: Out of memory exception for big indexes

I wanted to reply on this because it seems that a few people have had similar problems and I am very pleased with the simple solution. Basically I re-created the index using OMIT NORMS where ever possible, as well as Field.Store.NO where ever possible. The result shrunk my index from 19GB to 4

Re: Mixing Case and Case-Insensitive Searching

Yeah, what Hoss said. That's a much more elegant solution than I suggested. If you use the same filter for indexing and searching, it'll all "just happen" for you. Erick On 4/17/07, Chris Hostetter <[EMAIL PROTECTED]> wrote: : I've run into a case where we want to search for the acronym 'LET'

MultiSearcher vs MultiReader

I've been on this list long enough to have a vast repository of information about using a MultiSearcher versus an IndexSearcher that works on a MultiReader. However, after looking through several hundred list postings, I could not find what I was looking for. So if there is a posting or threa

Re: Mixing Case and Case-Insensitive Searching

: I've run into a case where we want to search for the acronym 'LET', : however this three letter word occurs very frequently in quite a : number of documents. : : What I'm looking to do is a query that's case insensitive _except_ for : that specific term. it sounds like you need to create a cust

Re: Mixing Case and Case-Insensitive Searching

Would it work to index the upper-case LET as something else? For instance, index it as '$let' Now, all your searches are on one index, but you have to substitute '$let' where you want to find LET in your query.. This won't match your other occurrences of let... You'll have to watch to be sure yo

Mixing Case and Case-Insensitive Searching

I've run into a case where we want to search for the acronym 'LET', however this three letter word occurs very frequently in quite a number of documents. What I'm looking to do is a query that's case insensitive _except_ for that specific term. And, it appears to do so, things get very ugly, ver

Re: question about field equality in query

Chris, Thank you for your reply, your solution doesnt work in my case because I was thinking of indexing more than one document in a single index and each document representing a table in database. so if I put more than one document some fields for a single document will be empty. something like t