I think this is one of the primary use-cases for custom sharding. Solr 4.0 doesn't really lend itself to this scenario, but I _believe_ that the patch for custom sharding has been committed...
That said, I'm not quite sure how you drop off the old shard if you don't need to keep old data. I'd guess it's possible, but haven't implemented anything like that myself. FWIW, Erick On Fri, Dec 21, 2012 at 12:17 PM, Upayavira <u...@odoko.co.uk> wrote: > I'm working on a system for indexing logs. We're probably looking at > filling one core every month. > > We'll maintain a short term index containing the last 7 days - that one > is easy to handle. > > For the longer term stuff, we'd like to maintain a collection that will > query across all the historic data, but that means every month we need > to add another core to an existing collection, which as I understand it > in 4.0 is not possible. > > How do people handle this sort of situation where you have rolling new > content arriving? I'm sure I've heard people using SolrCloud for this > sort of thing. > > Given it is logs, distributed IDF has no real bearing. > > Upayavira >
