Hi Eric, From: Eric Luo <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Wednesday, February 19, 2014 10:03 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Partial index sorting problem
so this paragraph tells me that when I quey a view, I send the request to a SINGLE node, then this single node collect the collate the partial indices and return to me a full list.Now my only question is: the items in each partial index is sure ordered by default( e.g. ordered by post date field), but what happened when the requested node 'collect and collate' these partial indices?, does it 're-order' this new full list by the sorting field or it just 'concat' the partial lists in to a full one without caring the final ordering? >From what I've learned from my application, I think it's the second situation >that is the final returned list is NOT properly ordered. So can you tell me I >am wrong about this and explain to me? Indeed, if you're getting a different order there is an issue somewhere. Generally, the cluster should merge sort the resulting query from all of the nodes so it should always be ordered. One question though, do you have a reduce() function? The reason I ask is that the component that does the merge sort may have to re-reduce your results based on any reductions being done. It might be great if you could file an issue at couchbase.com/issues<http://couchbase.com/issues> with any sample data and views. Thanks, Matt -- Matt Ingenthron Couchbase, Inc. -- You received this message because you are subscribed to the Google Groups "Couchbase" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
