Not automatically as far as I know. You can use custom routing to achieve this though.
That said, be careful before you jump this way. While it _seems_ elegant, something like have one shard per day for the retention period (say 30 days) and just rotate the oldest one out, it may not be best. Consider the news case. Usually most people care about today's news, and a hot story will generate lots of queries, all of which are serviced by today's shard. Spreading your queries out amongst all 30 shards may actually be a better user experience, then to purge old data just do a delete-by-query on a datestamp, something like timestamp:[* TO NOW-30DAYS]. Don't know if it applies to your particular use case or not, but.... Erick On Wed, Jul 3, 2013 at 2:53 AM, kowish.adamosh <kowish.adam...@gmail.com>wrote: > Otis, > > Is it implemented? I can find only unresolved JIRA issues. > > Kowish > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr-cloud-date-based-paritioning-tp4074729p4074993.html > Sent from the Solr - User mailing list archive at Nabble.com. >
