Re: Filter query with multiple raw/literal ORs

2014-04-04 Thread Yonik Seeley
On Fri, Apr 4, 2014 at 5:28 PM, Mikhail Khludnev wrote: > On Fri, Apr 4, 2014 at 4:08 AM, Yonik Seeley wrote: > >> Try adding a space before the first term, so the >> default lucene query parser will be used: >> > > Yonik, I'm curious, whether it a feature? Yep, it was completely on purpose that

Re: Filter query with multiple raw/literal ORs

2014-04-04 Thread Mikhail Khludnev
On Fri, Apr 4, 2014 at 4:08 AM, Yonik Seeley wrote: > Try adding a space before the first term, so the > default lucene query parser will be used: > Yonik, I'm curious, whether it a feature? -- Sincerely yours Mikhail Khludnev Principal Engineer, Grid Dynamics

Re: Filter query with multiple raw/literal ORs

2014-04-03 Thread Yonik Seeley
On Thu, Apr 3, 2014 at 7:04 PM, Gregory Chanan wrote: > {!raw f=foobar v=*} OR {!raw f=foobar v=a} > but this seems to give me the same results as the single-clause query. Right... the query parser is detected as "raw" and the rest of the value is used as the term (or rather it's ambiguous becaus

Re: Filter query with multiple raw/literal ORs

2014-04-03 Thread Ahmet Arslan
Hi Greg, One way is to use _query_ hook _query_:"{!raw f=foobar v=*}" OR _query_:"{!raw f=foobar v=a}" http://searchhub.org/2009/03/31/nested-queries-in-solr/ On Friday, April 4, 2014 2:07 AM, Gregory Chanan wrote: I have a string field called foobar.  I'm constructing a FilterQuery with