Lucene query behavior using NOT

2015-02-08 Thread Ian Koelliker
Hello, I am trying to understand whether I am using the NOT operator correctly. I have the following scenario: Query 1 = body:(a OR NOT b) This is parsed as: (body:a) -(body:b) and finds 96,620 hits Query 2 = body:(a OR (*:* AND NOT b)) This is parsed as: (body:a) (+*:* -(body:b)) and finds

RE: index corruption with Lucene 2.9.4

2015-01-15 Thread Ian Koelliker
Best to upgrade Lucene (we stopped relying on File.exists a while back). Mike McCandless http://blog.mikemccandless.com On Thu, Jan 15, 2015 at 12:10 PM, Ian Koelliker ikoelli...@axsone.com wrote: Hello, We are seeing some weird instances of index corruption periodically when using Lucene

index corruption with Lucene 2.9.4

2015-01-15 Thread Ian Koelliker
Hello, We are seeing some weird instances of index corruption periodically when using Lucene 2.9.4. There are two specific cases we are seeing. 1) We are using the compound format and have noticed that sometimes we get errors when searching noting that files are missing (i.e. .fnm, .fdt,