The issue isn't with multiple wildcards exactly. Specifically, the problem
is if the query starts with a wildcard. In the case where it starts with a
wildcard, lucene has no option but to linearly go over every term in the
index to see if it matches your pattern. It must visit every singe term i
The expected behavior is to sometimes treat a character as indicating a new
token and other times to ignore the same character?
This sounds like behavior that should be much better documented than it
currently is.
Why would this be the default? What cases is it meant for?
-Original Message--