I'm a bit confused, to be honest.

There is no way to customize the enabled flags right now. That can be annoying, and adding methods to control that is definitely a good idea. However, *all flags are enabled* by default. As you noticed yourself, passing "-1" as a flag simply enables all features (that's what you did in your snippet of code).

So I'm not sure how your patch solved the problem exactly, and I'm not even sure what caused the problem. Maybe it was indeed FieldContextSimpleQueryParser? It looks like it doesn't normalize terms before creating queries, like it should. Depending on your analyzer, that could cause no results to be returned.

That being said, if you manage to make it work using standard Lucene classes instead of our custom query parser *and* to make all pre-existing integration tests pass... Well, that would be awesome.