Re: Empty results with OR filter query

2012-02-10 Thread Steven Ou
For anyone having this issue in the future: I managed to narrow it down to Solr-RA 3.5. Installing Solr 3.5 solved the issue. I don't really know how the internals of Solr-RA work, but it appears that it was using AND operators even when I explicitly used OR operators in the query. The other solut

Re: Empty results with OR filter query

2012-02-09 Thread Erik Hatcher
On Feb 9, 2012, at 20:11 , Steven Ou wrote: > Sorry, what do you mean "explicit category rather than boolean expression"? q=category_ids_im:634 for example. Just to get an idea of what matches each category. > Type was not changed midstream - hasn't really been changed ever, really. > And I h

Re: Empty results with OR filter query

2012-02-09 Thread Steven Ou
Sorry, what do you mean "explicit category rather than boolean expression"? Type was not changed midstream - hasn't really been changed ever, really. And I happen to have *just* reindexed, too. Don't seem to have a default operator set. Not sure how to do it, either...? -- Steven Ou | 歐偉凡 *ravn.

Re: Empty results with OR filter query

2012-02-09 Thread Erik Hatcher
Extremely odd. Hmmm... other things to try: * query on an explicit category, rather than in a boolean expression * try a different field type than sint (say just int, or string) * shouldn't matter (since you're using "OR" explicitly) but double check the default operator in schema.xml *

Re: Empty results with OR filter query

2012-02-09 Thread Steven Ou
I'm really sorry to be spamming everyone. I know I've sent out a ton of emails, but I ran it without *any* other filters (just solr/select?q=category_ids_im:(637+OR+639+OR+634)&debugQuery=true) and here's the debug. This produces 1 result only. Removing category 634 produces 11 results. Can anyone

Re: Empty results with OR filter query

2012-02-09 Thread Steven Ou
Actually, I take that back. Using q instead of fq still produces the same problem. Somehow it's *less* inconsistent so at first glance it looked like it fixed it. However, it does *not* fix it :( -- Steven Ou | 歐偉凡 *ravn.com* | Chief Technology Officer steve...@gmail.com | +1 909-569-9880 On Thu

Re: Empty results with OR filter query

2012-02-09 Thread Steven Ou
Well, keeping all other filter queries the same, changing fq= category_ids_im:(637+OR+639) to fq=category_ids_im:(637+OR+639+OR+634) causes results to not show up. In fact, I took out *all* other filter queries. And while I wasn't able to reproduce it exactly, nonetheless when I added the third ca

Re: Empty results with OR filter query

2012-02-09 Thread Erik Hatcher
Yes, certainly should work fine as a filter query... I was merely trying to eliminate variables from the equation. You've got several filters and a q=*:* going on below, so it's obviously harder to pinpoint what could be going wrong. I suggest continuing to eliminate variables here, as more th

Re: Empty results with OR filter query

2012-02-09 Thread Steven Ou
By turning fq=category_ids_im:(637+OR+639+OR+634) to q=category_ids_im:(637+OR+639+OR+634) it appears to produce the correct results. But... that doesn't seem to make sense to me? Shouldn't it work just fine as a filter query? -- Steven Ou | 歐偉凡 *ravn.com* | Chief Technology Officer steve...@gmail

Re: Empty results with OR filter query

2012-02-09 Thread Steven Ou
I don't really know how to analyze the debug output... Here it is for the full query I'm running, which includes other filter queries. *:* *:* MatchAllDocsQuery(*:*) *:* LuceneQParser type:Event displayable_b:true category_ids_im:(637 OR 639 OR 634) end_datetime_dt:[2012\-02\-10T00\:17\:52Z TO

Re: Empty results with OR filter query

2012-02-09 Thread Steven Ou
Heh, yeah, I bolded the numbers for emphasis. The field type follows. *Dynamically Created From Pattern: **_IM *Field Type: *SINT *Schema: *Indexed, Multivalued, Omit Norms *Index: *(unstored fiel

Re: Empty results with OR filter query

2012-02-09 Thread Erik Hatcher
What type of field is category_ids_im? And I'm assuming that the *'s below are for emphasis and not really in your query? Try your query in the q parameter and turn on debug (&debugQuery=true) and see how your query is parsing. That'll likely tell all. Erik On Feb 9, 2012, at 18:42 ,