[ 
https://issues.apache.org/jira/browse/SOLR-7873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659440#comment-14659440
 ] 

Randy Jacobsen commented on SOLR-7873:
--------------------------------------

Thanks for your suggestion.
With debugQuery=on the first two queries generate what you would expect.
You can use as many terms as you want with only one field.
You can use as many fields as you want with only one term.
The third query generates "+pub_name:5 +journal_name:radar* +journal+name:c" 
which is obviously bogus.

>From StackOverflow:

"Might I suggest the solr prefix query plugin if you are only using it for 
wildcards on the suffix as we were 
http://lucene.apache.org/solr/4_0_0/solr-core/org/apache/solr/search/PrefixQParserPlugin.html

example usage

http://localhost:8983/solr/collection/select?q={!prefix%20f=name}Bob%20Smi
would match "Bob Smith" or "Bob Smit" but not convert into a check of ("Bob" OR 
"Smi*") as would happen if you used the first solution you might consider along 
the lines of q=name:Bob%20Smi*

Hopefully this is of some help to you or someone else looking for a simple 
solution because I was banging my head against a wall for hours before I found 
this!"


> prefix query parser fails with two words and a second field
> -----------------------------------------------------------
>
>                 Key: SOLR-7873
>                 URL: https://issues.apache.org/jira/browse/SOLR-7873
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.8
>            Reporter: Randy Jacobsen
>            Priority: Minor
>
> works: {!prefix f=journal_name}radar c
> works: pub_name:5 AND {!prefix f=journal_name}radar
> fails: pub_name:5 AND {!prefix f=journal_name}radar c
> both fields are lowercased text fields
> fail results in 0 matches
> any equivalent queries would be welcome



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to