Saw that one.  Can't remember for certain, but recall the actual syntax error 
was in a filter query.   It could have been a quoting error or a date math 
error in a range expression.  But, either way, the issue was in the fq.  Using 
edismax.  hth

-----Original Message-----
From: Jack Krupansky [mailto:jack.krupan...@gmail.com] 
Sent: Friday, March 20, 2015 5:08 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr Unexpected Query Parser Exception

Which query parser are you using? The dismax query parser does not support wild 
cards or "*:*".

Either way, the error message is unhelpful - worth filing a Jira.

-- Jack Krupansky

On Fri, Mar 20, 2015 at 7:21 AM, Vishnu Mishra <vdil...@gmail.com> wrote:

> Hi, I am using solr 4.10.3 and doing distributed shard query. I am 
> getting following syntax exception at regular intervals.
>
>
>  ERROR org.apache.solr.core.SolrCore  ?
> org.apache.solr.common.SolrException: org.apache.solr.search.SyntaxError:
> Cannot parse '*:*': Encountered "<EOF>" at line 1, column 3.
> Was expecting one of:
>     "NOT" ...
>     "+" ...
>     "-" ...
>     <BAREOPER> ...
>     "(" ...
>     "*" ...
>     "^" ...
>     <QUOTED> ...
>     <TERM> ...
>     <FUZZY_SLOP> ...
>     <PREFIXTERM> ...
>     <WILDTERM> ...
>     <REGEXPTERM> ...
>     "[" ...
>     "{" ...
>     <PROXY_MF> ...
>     <JOIN_MF> ...
>     <FRQ_CUT_OFF> ...
>     <NUMBER> ...
>     <TERM> ...
>     "*" ...
>
>
> My query to solr is *:* can anyone explain me why this exception is 
> occurring.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-Unexpected-Query-Parser-Except
> ion-tp4194156.html Sent from the Solr - User mailing list archive at 
> Nabble.com.
>

*************************************************************************
This e-mail may contain confidential or privileged information.
If you are not the intended recipient, please notify the sender immediately and 
then delete it.

TIAA-CREF
*************************************************************************

Reply via email to