&defType=lucene &q=NOT foo
No problem! Also no problem: &q=foo AND NOT bar But, problem when the operand to an "OR" is a NOT: &q=foo OR (NOT bar) Does NOT work correctly. Can be worked around if you instead do this: &q=foo OR (*:* AND NOT bar)So I think 1.4.1 lucene query parsers handling of "pure negative" queries only goes so far, mainly until there's an "OR" involved.