"Aliases are meant for read operations can refer to one or more real collections".
So should I go with the approach of creating a collection for per day's data and aliasing a collection with all these collection names? So instead of trying to route the documents to a shard should I send to a specific collection? The problem I'm facing is even with routing the documents using date!id one shard contains docs from other date ranges too. On Mon, Apr 14, 2014 at 4:53 PM, Alexandre Rafalovitch <arafa...@gmail.com>wrote: > Would collection aliasing be a relevant feature here (a different > approach): > http://blog.cloudera.com/blog/2013/10/collection-aliasing-near-real-time-search-for-really-big-data/ > > Regards, > Alex. > Personal website: http://www.outerthoughts.com/ > Current project: http://www.solr-start.com/ - Accelerating your Solr > proficiency > > > On Mon, Apr 14, 2014 at 6:05 PM, Mukesh Jha <me.mukesh....@gmail.com> > wrote: > > Hello Experts, > > > > I want to index my documents in a way that all documents for a day are > > stored in a single shard. > > > > I am planning to have shards for each day e.g. shard1_01_01_2010, > > shard1_02_01_2010 ... > > And while hashing the documents of 01/01/2010 should go to > > shard1_01_01_2010. > > > > Thins way I can query a specific shard for my documents of a given date, > > also I can just delete the shards for date older than some data. > > > > For this I tried using date*!*docId as my hashing param but it calculates > > the hash on the date feild and assigns a shard (based on which shard is > > assigned for that hash) to it which is not what i desire to have. > > > > Is this possible using the current solr-cloud? > > > > -- > > > > > > Thanks & Regards, > > > > *Mukesh Jha <me.mukesh....@gmail.com>* > -- Thanks & Regards, *Mukesh Jha <me.mukesh....@gmail.com>*
