Olivier's solution is the fastest one. You can also use
queryParser.SetAllowLeadingWildcard(true) to be able to use wildcards at the beginning. DIGY -----Original Message----- From: Olivier Spinelli [mailto:[email protected]] Sent: Wednesday, October 14, 2009 2:42 PM To: [email protected] Subject: RE: [jira] Updated: (LUCENENET-196) Wildcard as the first character in search Hello, This is a classical issue. You may consider indexing the terms also in reverse order (indexing 'indexing' and 'gnixedni') - either in the same or in a dedicated field. HTH Olivier -----Message d'origine----- De : Stig Føyn (JIRA) [mailto:[email protected]] Envoyé : mercredi 14 octobre 2009 12:51 À : [email protected] Objet : [jira] Updated: (LUCENENET-196) Wildcard as the first character in search [ https://issues.apache.org/jira/browse/LUCENENET-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stig Føyn updated LUCENENET-196: -------------------------------- Description: I have a business requirement to search for terms with a wildcard at the beginning "*order". Someone told me that this was in the the issue-tracking system, but I cant seem to find it. > Wildcard as the first character in search > ----------------------------------------- > > Key: LUCENENET-196 > URL: https://issues.apache.org/jira/browse/LUCENENET-196 > Project: Lucene.Net > Issue Type: Improvement > Reporter: Stig Føyn > > I have a business requirement to search for terms with a wildcard at the > beginning "*order". Someone told me that this was in the the issue-tracking > system, but I cant seem to find it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
