[
https://issues.apache.org/jira/browse/LUCENE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688494#action_12688494
]
Mark Miller commented on LUCENE-1570:
-------------------------------------
Yonik spit out a bit of a better answer while I typed - right, you do have
access to the field in getWildcardQuery, and the leading check happens there,
so you can override it. My brain always runs towards building the support in,
but in this case it may be clear to leave it out anyway. Its somewhat of a
niche concern. Just had the new QueryParser on my mind.
> 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
