Well, you have bad problem. You have a requirement that forces you to build an expensive, unreliable search system.
You need to do specific shard creation at specific times every day. What happens if that fails? Does search go down until it is fixed because all searches are going to a shard that doesn’t exist? Or do the documents get randomly sent to existing shards, so you need to search all the shards anyway? If docs are distributed, you’ll need to clean that day up with delete by query. You need to build that as a failure recovery. Does your code handle leap years for shard creation? Daylight saving time? How do you test that code? You’ll be writing a lot of custom code that other people don’t need. If you are a consultant, this is great. For the customer, not so good. Whoever wrote that requirement does not know very much about Solr. It sounds like they are trying to force RDBMS sharding onto Solr. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Jul 20, 2017, at 8:09 AM, rehman kahloon > <mrehman_kahl...@yahoo.com.INVALID> wrote: > > blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px > #715FFA solid !important; padding-left:1ex !important; background-color:white > !important; } Hi Eric, > Thank you very much for your guidance. > No sir that is our requirmnt to load data into specific shard and later after > rentention time we will delete that shard. > Please share if you have any manual sharding exercise dicument. > 2nd is it posible data automatically load into specific shard without using > shard name during loading. > > Is there any solr file where i mentioned all my shards name with specific > date. When data come automTically load dara into alredy mentioned shard? > Once again Thank you very much. > Kind regards,Muhammad rehman kahloon > > Sent from Yahoo Mail for iPhone > > > On Thursday, July 20, 2017, 19:57, Erick Erickson <erickerick...@gmail.com> > wrote: > > Use the "implicit" router (being renamed "manual". that takes the > value of a particular field (_route_ by default) and sends docs to > that exact shard. > > But I also question whether sharding on this schema is a good idea. If > you have an access pattern where most queries are for, say, the last > two days then all the work will be done on only 2 machines and all the > rest will be idle. You should at least consider just using normal > routing that distributes the data across all shards and then use > delete-by-query to delete the data older than 10 days. > > Best, > Erick > > On Thu, Jul 20, 2017 at 12:51 AM, rehman kahloon > <mrehman_kahl...@yahoo.com.invalid> wrote: >> >> Hi Sir, >> Taken your id from your document on SlideShare. >> Need your guidance on my plan ,My target is to create sub-collection/shards >> within a collection. >> e.g >> Currently 1 have 10 days data and want to store data against each >> date in separate partitions. like oracle partition concepts (one table can >> have many partitions) >> Plan is to store each date data with in separate node, Total physical nodes >> are 10 and after 10 days, 11th date data load in node1 and existing data >> backup (oldest date data with purge and backed up). >> Please guide me how can i perform that using SolrCloud. 1 collection with >> unlimited sub collection. >> >> Thank you very much in advanced. >> >> Kind Regards,Muhammad Rehman Kahloon. > > >
