Just to comment on my own post...
I don't believe index-time will be involved in this sort of functionality, as
there's no way to know at index-time what 'tag groups' a given term will be in
at any given time.
This leads me to believe that a query request parser plugin approach might be
I have a need to favor documents from one shard over another when duplicates
occur. I found this code in the query component:
String prevShard = uniqueDoc.put(id, srsp.getShard());
if (prevShard != null) {
// duplicate detected
numFound--;
It seems like changing an element in a priority queue breaks the
invariants, and hence it's not doable with a priority queue and with
the current strategy of adding sub-responses as they are received.
One way to continue using a priority queue would be to add
sub-responses to the queue in the
It also seems like it should be possible to include the shard number in the
ordering of responses.
On Sat, Feb 6, 2010 at 8:33 AM, Yonik Seeley yo...@lucidimagination.comwrote:
It seems like changing an element in a priority queue breaks the
invariants, and hence it's not doable with a
so if we received the response from shard2 before shard1, we would just
queue it up and wait for the response to shard1.
This crossed my mind, but my concern was how to handle the case when shard1
never responds. Is this something I need to worry about?
-mike
On Sat, Feb 6, 2010 at 11:33 AM,
Command line Solr check softwares
-
Key: SOLR-1761
URL: https://issues.apache.org/jira/browse/SOLR-1761
Project: Solr
Issue Type: New Feature
Affects Versions: 1.4
Reporter: Jason Rutherglen
