Yes, , we will offer something for this - just a matter of priorities for the 4 release. My current priority is heavily bug side at the moment personally.
It's more likely in 4.1 or 4.2 or something. - Mark On Tue, Sep 11, 2012 at 2:37 AM, Pavel Goncharik <pavel.goncha...@gmail.com> wrote: > Apparently https://issues.apache.org/jira/browse/SOLR-2592 will help you out. > Unfortunately, it seems that this issue will not be included into Solr > 4.0 release. > > I'm wondering myself if there are any plans to commit and release this > issue or an equivalent, to give users control over partititioning in > the SolrCloud? > > On Tue, Sep 11, 2012 at 7:00 AM, Nikhil Chhaochharia > <nikhil...@yahoo.com> wrote: >> Hi, >> >> I am trying out SolrCloud using a recent Solr 4 nightly. We use result >> grouping (FieldCollapsing) and found that the value of ngroups returned by >> Solr is not correct. >> >> My understanding is that all the documents belonging to the same group >> should be on the same shard to ensure that ngroups returns the correct >> value. However, the shard that a document is sent to is decided >> automatically based on the value of the uniqueKey field. >> >> Is it possible for Solr to hash fieldX instead of the uniqueKey while >> distributing the documents to the different shards? Is there some other way >> of getting accurate values of ngroups when using SolrCloud? >> >> Thanks, >> Nikhil
