I agree, might be a redundant check now. This test was added when the query
parser was enhanced to optionally allow leading wild card (revision 468291
),
but this case calls getWildCardQuery(), not getPrefixQuery().
Still, the check seems harmless - sort of defensive - protecting against
the
case
In certain cases, I use a modified QueryParser which does not allow "field:"
syntax. While testing variants of Prefix and Wildcard Query, I came across an
oddity with getPrefixQuery(). The standard getPrefixQuery() (2.1) is given
termStr without the trailing *, so the check
if (!allowLeading
