[ 
https://issues.apache.org/jira/browse/LUCENE-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743314#action_12743314
 ] 

Michael McCandless commented on LUCENE-1792:
--------------------------------------------

Urgh I see.  But then I'd also need to make a StandardPrefixWildcardQueryNode?  
And then a two new builder classes corresponding to these new nodes?

Could we then fix StandardSyntaxParser to never create WildcardQueryNode (ie, 
always create StandardWildcardQueryNode)?  And then remove 
WildcardQueryNodeBuilder?  (Though, why do we still have 
BooleanQueryNodeBuilder?).

Maybe, instead, we should just make this fix in the builder (then it'd be like 
a 2-line change)?  I realize that violates the "builders can't consult 
configuration", but perhaps that rule is too strict.... in this case it means 
having to make 4 new classes instead of adding 2 lines into the existing 
classes (I think?).

Alternatively, we could just revert my changes.  In 3.0, these queries will set 
their defaults to AUTO, anyway, at which point this is no longer an issue.  
Plus, since we are no longer planning to aggressively swap the current 
QueryParser with this new one, this issue is less important to fix.

> 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 McCandless
>            Priority: Minor
>             Fix For: 2.9
>
>         Attachments: LUCENE-1792.patch, LUCENE-1792.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

Reply via email to