[
https://issues.apache.org/jira/browse/LUCENE-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743364#action_12743364
]
Michael McCandless commented on LUCENE-1792:
--------------------------------------------
{quote}
Since we use UnescapedCharSequence in the FieldQueryNode values.
We can identify the wildcards in the Processors and have one simple
processor that converts FieldQueryNode to StandardWildcardQueryNode and to
StandardPrefixWildcardQueryNode,
and we can remove WildcardQueryNode and PrefixWildcardQueryNode from the core.
{quote}
+1
bq. we could change the parser to generate directly StandardBooleanQN and
StandardWildcardQN, that makes more sense.
+1 too... whenever standard subclasses a core node for some reason, it seems
like the core syntax parser shouldn't produce the core node anymore.
Luis or Adriano do you want to take a crack at this? Can you do this shortly
(2.9 looks iminent)? Else we can simply revert my changes and then move this
to 3.1...
> 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
