[
https://issues.apache.org/jira/browse/LUCENE-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744424#action_12744424
]
Luis Alves commented on LUCENE-1792:
------------------------------------
{quote}
One question: wouldn't it be better if the WildcardQueryNode knew the positions
of the wildcard characters? Then e.g. the AllowLeadingWildcardProcessor would
not have to have knowledge about the wildcard chars * and ? and would not have
to check again.
{quote}
I like the idea, I'll create another JIRA for that, since WildcardQueryNode
already knows about the wildcard positions,
we just need to add a method.
{quote}
I think I'm happy with the patch... I'll look a bit more tomorrow and commit
then at the end of the day if I don't find any issues and nobody objects.
{quote}
Those are great news. One less issue for 2.9, almost there.
> new QueryParser fails to set AUTO REWRITE for multi-term queries
> ----------------------------------------------------------------
>
> Key: LUCENE-1792
> URL: https://issues.apache.org/jira/browse/LUCENE-1792
> Project: Lucene - Java
> Issue Type: Bug
> Components: contrib/*
> Affects Versions: 2.9
> Reporter: Michael McCandless
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1792.patch, LUCENE-1792.patch,
> LUCENE-1792_update_v1.patch, LUCENE-1792_update_v3.patch,
> removal_of_wildcard_and_prefix_detection_from_the_syntaxparser.patch
>
>
> The old QueryParser defaults to constant score rewrite for
> Prefix,Fuzzy,Wildcard,TermRangeQuery, but the new one seems not to.
--
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
