On Fri, Sep 20, 2013 at 10:39 AM, Yonik Seeley wrote:
> On Fri, Sep 20, 2013 at 10:15 AM, Yonik Seeley wrote:
>> Also, it looks like route.field can be specified for the compositeId
>> rotuer as well.
>
> Actually, I decided to leave that out of the docs since on further
> review the implementati
On Fri, Sep 20, 2013 at 10:15 AM, Yonik Seeley wrote:
> Also, it looks like route.field can be specified for the compositeId
> rotuer as well.
Actually, I decided to leave that out of the docs since on further
review the implementation looks incorrect (or perhaps I don't
understand the intended A
OK, I was just reviewing some of the router code changes (better late
than never...)
ImplicitDocIdRouter has this:
if(shard == null) shard =params.get("_shard_"); //deperecated
for back compat
Also, it looks like route.field can be specified for the compositeId
rotuer as well.
I'll update tha
I notice that Noble updated the Collections API page with the
information that was needed - thank you.
Based on that, I updated this page:
https://cwiki.apache.org/confluence/display/solr/Shards+and+Indexing+Data+in+SolrCloud
Yonik or Noble, if you one of you would look the section on Document
Ro
Yonik / Noble / Shalin in particular:
we need clarification here on these changes for 4.5...
https://issues.apache.org/jira/browse/SOLR-4221?focusedCommentId=13769675&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13769675
Cassandra and i were talking on IRC thi
