Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 3713 invoked from network); 14 Feb 2010 03:52:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Feb 2010 03:52:46 -0000 Received: (qmail 64076 invoked by uid 500); 14 Feb 2010 03:52:45 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 63901 invoked by uid 500); 14 Feb 2010 03:52:45 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 63893 invoked by uid 99); 14 Feb 2010 03:52:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Feb 2010 03:52:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of markrmiller@gmail.com designates 209.85.221.202 as permitted sender) Received: from [209.85.221.202] (HELO mail-qy0-f202.google.com) (209.85.221.202) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Feb 2010 03:52:34 +0000 Received: by qyk40 with SMTP id 40so3344594qyk.14 for ; Sat, 13 Feb 2010 19:52:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:cc; bh=d2GFUZnUhzdm4phA/PHN8ehc0E/t/4JjIn2GD6U50+A=; b=dY8RgirfGZgi8dJwh1DII8DTIchdS4EtIskZEUmB4DUgU/dkBBofYVmfQSTTjrVqjo betvMCznKlBp5XFqfwAyYZimIhDcCOYQgp69la081GCD5SoYPpLI/VgUrl3xRGTroeD6 TQnXJaEFtxoI8lfVbFaEfQtkK5TP1EyhjQn5o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc; b=UenY6gX1csw/KED45CVlHRiRFUwIiJ8LkhgLysW5qLqZ1/hixPDPMZDgQx2B8nVIML yUyJ23Zfr7v1xJzGbvZV5S3E+IZxYfo9zYU6BoTC5uqDI0B8t4HAlq4FoGBsQRxExjXA OJo6/AB3pM9/CCzuZO/ZY6JC6P0mG90XhHXtY= Received: by 10.224.45.16 with SMTP id c16mr48894qaf.296.1266119533374; Sat, 13 Feb 2010 19:52:13 -0800 (PST) Received: from ?192.168.1.112? (ool-44c639d9.dyn.optonline.net [68.198.57.217]) by mx.google.com with ESMTPS id 6sm13992875qwd.46.2010.02.13.19.52.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 13 Feb 2010 19:52:12 -0800 (PST) References: <1104225058.259011266117747951.JavaMail.jira@brutus.apache.org> Message-Id: <1AA668E1-886C-4139-8545-C0D19D371341@gmail.com> From: Mark Miller To: "java-dev@lucene.apache.org" In-Reply-To: <1104225058.259011266117747951.JavaMail.jira@brutus.apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7E18) Mime-Version: 1.0 (iPhone Mail 7E18) Subject: Re: [jira] Commented: (LUCENE-2262) QueryParser should now allow leading '?' wildcards Date: Sat, 13 Feb 2010 22:51:45 -0500 Cc: "java-dev@lucene.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org Nah, let's just make fuzzy not work in the qp by default :) And make that back compat while your at it - while not abusing Version so that it's used for something subjective :) wouldn't want to rile up Hoss. I'm like 3/4 serious. - Mark http://www.lucidimagination.com (mobile) On Feb 13, 2010, at 10:22 PM, "Robert Muir (JIRA)" wrote: > > [ https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833496#action_12833496 > ] > > Robert Muir commented on LUCENE-2262: > ------------------------------------- > > bq. in my opinion disallowing these queries with leading wildcards, > be it * or ? or whatever, is rather silly, since we allow even > slower fuzzyqueries by default. > > bq. Agree. > > What do you think, should we skip this step then and simply > deprecate the entire setAllowLeadingWildcard concept all together, > setting it to true for Version >= 3.1? > > >> QueryParser should now allow leading '?' wildcards >> -------------------------------------------------- >> >> Key: LUCENE-2262 >> URL: https://issues.apache.org/jira/browse/LUCENE-2262 >> Project: Lucene - Java >> Issue Type: Improvement >> Components: QueryParser >> Affects Versions: Flex Branch >> Reporter: Robert Muir >> Assignee: Robert Muir >> Priority: Minor >> Fix For: Flex Branch >> >> Attachments: LUCENE-2262.patch, LUCENE-2262_backwards.patch >> >> >> QueryParser currently throws an exception if a wildcard term begins >> with the '?' operator. >> The current documentation describes why this is: >> {noformat} >> When set, * or ? are allowed as the first character of a >> PrefixQuery and WildcardQuery. >> Note that this can produce very slow queries on big indexes. >> {noformat} >> In the flexible indexing branch, wildcard queries with leading '?' >> operator are no longer slow on big indexes (they do not enumerate >> terms in linear fashion). >> Thus, it no longer makes sense to throw a ParseException for a >> leading '?' >> So, users should be able to perform a query of "?foo" and no longer >> get a ParseException from the QueryParser. >> For the flexible indexing branch, wildcard queries of 'foo?', '? >> foo', 'f?oo', etc are all the same from a performance perspective. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org > For additional commands, e-mail: java-dev-help@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org