[
https://issues.apache.org/jira/browse/SOLR-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199774#comment-13199774
]
Ahmet Arslan commented on SOLR-1604:
------------------------------------
Committed o.a.l.queryparser.complexPhrase.ComplexPhraseQueryParser does not
work with non-default fields. Several Lucene users raised this issue on mailing
lists. Mark Harwood said the following on LUCENE-1486 which is still
unresolved. However it didn't get any attention.
{quote}Fixing this would require changing the package name of
ComplexPhraseQueryParser or changing the visibility of "field" in the
QueryParser base class to "protected".
Anyone have any strong feelings about which of these is the most
acceptable?{quote}
That's why attachment of this issue is not consuming committed
o.a.l.queryparser.complexPhrase.ComplexPhraseQueryParser and released as a
solr-plugin.
> Wildcards, ORs etc inside Phrase Queries
> ----------------------------------------
>
> Key: SOLR-1604
> URL: https://issues.apache.org/jira/browse/SOLR-1604
> Project: Solr
> Issue Type: Improvement
> Components: search
> Affects Versions: 1.4
> Reporter: Ahmet Arslan
> Priority: Minor
> Fix For: 3.6, 4.0
>
> Attachments: ComplexPhrase.zip, ComplexPhrase.zip, ComplexPhrase.zip,
> ComplexPhrase.zip, ComplexPhrase.zip, ComplexPhraseQueryParser.java,
> SOLR-1604.patch
>
>
> Solr Plugin for ComplexPhraseQueryParser (LUCENE-1486) which supports
> wildcards, ORs, ranges, fuzzies inside phrase queries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
