e memory,
> of course. Depending upon how big your index is, this could
> be quite a lot.
>
> Yet another time/space tradeoff But yeah, use filter queries
> until you have OOMs, then get more memory ...
>
> Best
> Erick
>
> On Wed, Aug 24, 2011 at 8:07 PM, Joshua H
4:48 PM, Shawn Heisey wrote:
> On 8/24/2011 2:02 PM, Joshua Harness wrote:
>
>> I've done some basic query performance testing on my SOLR instance,
>> which allows users to search via a faceted search interface. As such,
>> document relevancy is less important to me
All -
I apologize if this question has been asked before - I couldn't seem to
find a straightforward answer by researching it on google and stackoverflow.
I am trying to understand when I should use filter queries vs plain vanilla
queries. Here's what I understand:
* Filter queries can be m
I noticed that lucene supports 'Nested Documents'. However - I
couldn't find mention of this feature within SOLR. Does anybody know
how to leverage this lucene feature through SOLR?
Thanks!
Josh Harness
How does one issue span queries in SOLR (Span, SpanNear, etc)? I've
done a bit of research and it seems that these are not supported. It
would seem that I need to implement a QueryParserPlugin to accomplish
this. Is this the correct path? Surely this has been done before. Does
anybody have links to