[
https://issues.apache.org/jira/browse/LUCENE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
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: https://issues.apache.org/jira/browse/LUCENE-1570
> 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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
