?
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Thursday, May 21, 2015 11:30 AM
To: solr-user@lucene.apache.org
Subject: Re: optimal shard assignment with low shard key cardinality
using compositeId to enable shard splitting
I question your base
: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Thursday, May 21, 2015 11:30 AM
To: solr-user@lucene.apache.org
Subject: Re: optimal shard assignment with low shard key cardinality
using compositeId to enable shard splitting
I question your base assumption:
bq: So shard by document
, May 21, 2015 11:30 AM
To: solr-user@lucene.apache.org
Subject: Re: optimal shard assignment with low shard key cardinality using
compositeId to enable shard splitting
I question your base assumption:
bq: So shard by document producer seems a good choice
Because what this _also_ does is force
[mailto:erickerick...@gmail.com]
Sent: Thursday, May 21, 2015 11:30 AM
To: solr-user@lucene.apache.org
Subject: Re: optimal shard assignment with low shard key cardinality using
compositeId to enable shard splitting
I question your base assumption:
bq: So shard by document producer seems a good
Hi
I'd like some feedback on how I'd like to solve the following sharding problem
I have a collection that will eventually become big
Average document size is 1.5kb
Every year 30 Million documents will be indexed
Data come from different document producers (a person, owner of his documents)
I question your base assumption:
bq: So shard by document producer seems a good choice
Because what this _also_ does is force all of the work for a query
onto one node and all indexing for a particular producer ditto. And
will cause you to manually monitor your shards to see if some of them
