Thanks guys. Yeah, separate rolling collections seem like the better way to
go.
-Scott
On Sat, Dec 29, 2012 at 1:30 AM, Otis Gospodnetic <
otis.gospodne...@gmail.com> wrote:
> https://issues.apache.org/jira/browse/SOLR-4237
Scott (OP), maybe you are after http://search-lucene.com/m/YBn4w1UAbEB and
https://issues.apache.org/jira/browse/SOLR-4237 ?
Otis
--
Solr & ElasticSearch Support
http://sematext.com/
On Fri, Dec 21, 2012 at 6:57 AM, Per Steffensen wrote:
> Custom routing is a nice improvement for 4.1, but i
Custom routing is a nice improvement for 4.1, but if I understand you
correctly it is probably not what you want to use.
If I understand you correctly you want to make a collection with a
number of slices - one slice for each day (or other period) - and then
make kinda "slicing window" where y
On Tue, Dec 18, 2012 at 2:20 PM, Scott Stults
wrote:
> I'm going to be building a Solr cluster and I want to have a rolling set of
> slices so that I can keep a fixed number of days in my collection. If I
> send an update to a particular slice leader, will it always hash the unique
> key and (prob
I'm going to be building a Solr cluster and I want to have a rolling set of
slices so that I can keep a fixed number of days in my collection. If I
send an update to a particular slice leader, will it always hash the unique
key and (probably) forward the doc to another leader?
Thank you,
Scott
