Do the requests in parallel (separate threads) and then the performance
won't be impacted significantly.
-- Jack Krupansky
-----Original Message-----
From: Sourajit Basak
Sent: Sunday, June 23, 2013 10:23 AM
To: solr-user@lucene.apache.org
Subject: Re: edismax: date range facet with queries containing OR clause
Thats exactly how we are doing now. However, we need to offer the search
over slow networks, hence was wondering if there's a way to reduce server
round-trips.
On Sun, Jun 23, 2013 at 7:14 PM, Jack Krupansky
<j...@basetechnology.com>wrote:
Just do separate faceted query requests:
q= keyword1
facet.range=date_field_name
...
facet=true
q= keyword2
facet.range=date_field_name
...
facet=true
Where the "..." means fill in the additional facet.range.xxx parameters
(start, end, gap, etc.)
-- Jack Krupansky
-----Original Message----- From: Sourajit Basak
Sent: Sunday, June 23, 2013 8:52 AM
To: solr-user@lucene.apache.org
Subject: edismax: date range facet with queries containing OR clause
When we have a user query like keyword1 OR keyword2, we can find the count
of each keyword using the following params.
q= keyword1 OR keyword2
facet.query=keyword1
facet.query=keyword2
facet=true
How do we do a date range facet that will return results for each keyword
faceted by date range ?
