Thanks for the help Yonik.
Cheers
Gilad
--
View this message in context:
http://lucene.472066.n3.nabble.com/empty-result-set-for-a-sort-query-tp4309256p4309500.html
Sent from the Solr - User mailing list archive at Nabble.com.
Ah, 2-phase distributed search is the most likely answer (and
currently classified as more of a limitation than a bug)...
Phase 1 collects the top N ids from each shard (and merges them to
find the global top N)
Phase 2 retrieves the stored fields for the global top N
If any of the ids have been d
.
I don't think we have empty keys in our production schema but maybe it can
give a clue.
Thanks
Gilad
--
View this message in context:
http://lucene.472066.n3.nabble.com/empty-result-set-for-a-sort-query-tp4309256p4309315.html
Sent from the Solr - User mailing list archive at Nabble.com.
any custom plugin/query processor.
--
View this message in context:
http://lucene.472066.n3.nabble.com/empty-result-set-for-a-sort-query-tp4309256p4309304.html
Sent from the Solr - User mailing list archive at Nabble.com.
Is there any change Real Time Get is getting confused since rows=1?
On Sun, Dec 11, 2016 at 8:34 AM, Yonik Seeley wrote:
> On Sun, Dec 11, 2016 at 11:22 AM, moscovig wrote:
>> Hi
>> In solr 6.2.1 as server and solr 6.2.0 for client
>> It's a 2 shards index, 3 replicas for each shard.
>>
>> We ar
On Sun, Dec 11, 2016 at 11:22 AM, moscovig wrote:
> Hi
> In solr 6.2.1 as server and solr 6.2.0 for client
> It's a 2 shards index, 3 replicas for each shard.
>
> We are fetching the latest document with sorting over creationTime desc and
> rows=1.
>
> At the same time we are committing sanity tes
then gets
deleted and we get an empty result set. We would expect Solr to send that
document back or any other non deleted document.
What could be the problem?
Is this some kind of a bug in solr?
Thanks
Gilad
--
View this message in context:
http://lucene.472066.n3.nabble.com/empty-result-se
