Personally I think it is better to be explicit about where you index, so that when you create a new shard "december", you also switch the URL for your indexing code.
I suppose one trick you could use is to have a core called "current", which now would be for november, and once you get to december, you create a "november" core, and do a SWAP between "current"<->"november". Then your new core would now be "current" and you don't need to change URLs on the index client side. -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Solr Training - www.solrtraining.com On 2. nov. 2011, at 11:16, Vadim Kisselmann wrote: > Hello Jan, > > thanks for your quick response. > > It's quite difficult to explain: > We want to create new shards on the fly every month and switch the default > shard to the newest one. > We always want to index to the newest shard with the same update query > like http://localhost:8983/solr/update.(content stream) > > Is our idea possible to implement? > > Thanks in advance. > Regards > > Vadim > > > > > > 2011/11/2 Jan Høydahl <jan....@cominvent.com> > >> Hi, >> >> The only difference is the core name in the URL, which should be easy >> enough to handle from your indexing client code. I don't really understand >> the reason behind your request. How would you control which core to index >> your document to if you did not specify it in the URL? >> >> You could name ONE of your cores as ".", meaning it would be the "default" >> core living at /solr/update, perhaps that is what you're looking for? >> >> -- >> Jan Høydahl, search solution architect >> Cominvent AS - www.cominvent.com >> Solr Training - www.solrtraining.com >> >> On 2. nov. 2011, at 10:00, Vadim Kisselmann wrote: >> >>> Hello folks, >>> i have an problem with shard indexing. >>> >>> with an single core i use this update command: >>> http://localhost:8983/solr/update ..... >>> >>> now i have 2 shards, we can call them core0 / core1 >>> http://localhost:8983/solr/core0/update ..... >>> >>> >>> can i adjust anything to indexing in the same way like with a single core >>> without core-name? >>> >>> thanks and regards >>> vadim >> >>