Because one of the restrictions of wildcards is that they cannot appear as the first character in a search term if you use QueryParser. QueryParser rejects it (as you've seen). This is a deliberate design decision since this query will be humongous and most likely throw a TooManyClauses exception in any corpus of any size.....
You can create a Filter by enumerating the terms yourself, think about RegexTermEnum. Best Erick On 1/30/07, poeta simbolista <[EMAIL PROTECTED]> wrote:
Hi guys, I have been through the docs and I can't see why the parser does not parse this correctly: description:*sql is not correct: Lexical error at line 1, column 16. Encountered: "*" (42), after : "" However, the following: description: sql* is correct. Any idea why you can't use wildcard there? Cheers D -- View this message in context: http://www.nabble.com/Why-this-query-is-not-correct--tf3142268.html#a8709041 Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
