[
https://issues.apache.org/jira/browse/SOLR-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomás Fernández Löbbe updated SOLR-1604:
----------------------------------------
Attachment: SOLR-1604-alternative.patch
I'm attaching an alternative patch with what I propose:
It works fine with what's committed today in Lucene, it doesn't require
LUCENE-3758 committed to compile or LUCENE-1486 committed to run the tests,
however, it
has the limitations of the currently committed ComplexPhraseQueryParser.
I have some commented testUnorderedPhraseQuery. It is commented because it
currently doesn't run to the the limitations of LUCENE-3758
testFieldedQuery is also commented, as it doesn't run until LUCENE-1486 is
committed.
I added testAutogeneratingPhraseQueries, but it is also commented as hyphenated
queries don't work when "autogenerate phrase queries" is set to true. This is
something we should continue working on in this issue.
I would like to hear opinions on how to continue working.
> 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-alternative.patch, SOLR-1604.patch, 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: [email protected]
For additional commands, e-mail: [email protected]
