If you decide to go with multiple collection and aliasing, this would be useful
https://blog.cloudera.com/blog/2013/10/collection-aliasing-near-real-time-search-for-really-big-data/ On Sat, Jul 22, 2017 at 10:37 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 7/22/2017 5:02 AM, m rehman kahloon wrote: > > but my R&D is to find a way, not to use shard name using loading > > time,solrcloud automatically load data into predefined shard/date > specific > > shard. > > The implicit router is the only one you can use when you're doing time > interval sharding, because it's the only one that allows the addition of > new shards after collection creation. > > There is a reason that we are considering renaming the "implicit" router > to "manual" instead. > > https://issues.apache.org/jira/browse/SOLR-6630 > > When you use the implicit router, you're completely in charge of > sharding. There is no automation. You must name the shards, create > them, delete them, and inform Solr during indexing about which shard > will get new documents. If you want to only query a subset of the > shards in a collection, you are responsible for telling Solr that with > the shards parameter on the query. > > If you want to come up with a way to patch the Solr source code to add a > new router that does automated time interval sharding, that will be > welcome. > > Thanks, > Shawn > >
