lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] Resolved: (LUCENE-1570) QueryParser.setAllowLeadingWildcard could provide finer granularity
Date Fri, 10 Apr 2009 19:24:14 GMT


Mark Miller resolved LUCENE-1570.

    Resolution: Won't Fix

Yoniks solution is the right call for this rather than any changes I think.

As I hoped, the new QueryParser just contributed will be able to handle this type of thing
very elegantly :)

> QueryParser.setAllowLeadingWildcard could provide finer granularity
> -------------------------------------------------------------------
>                 Key: LUCENE-1570
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: QueryParser
>    Affects Versions: 2.4.1
>            Reporter: Jonathan Watt
> It's great that Lucene now allows support for leading wildcards to be turned on. However,
leading wildcard searches are more expensive, so it would be useful to be able to turn it
on only for certain search fields. I'm specifically thinking of wiki searches where it may
be too expensive to allow leading wildcards in the 'content:' field, but it would still be
very useful to be able to selectively turn on support for 'path:' and perhaps other fields
such as 'title:'. Would this be possible?

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:
For additional commands, e-mail:

View raw message