t; 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
> >
t;
>
> >
> >From: Vadim Kisselmann
> >To: solr-user@lucene.apache.org
> >Sent: Wednesday, November 2, 2011 6:16 AM
> >Subject: Re: shard indexing
> >
> >Hello Jan,
> >
> >thanks for your quick response.
>
e.apache.org
>Sent: Wednesday, November 2, 2011 6:16 AM
>Subject: Re: shard indexing
>
>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
ol 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?
>>
e 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.
> >
>
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
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
