Hello Jan,
i think personally the same (switch URL for my indexing code), but my
requirement is to use the same query.
Thanks for your suppose with this one trick. Great idea which could work in
my case, i test it.
Regards
Vadim
2011/11/2 Jan Høydahl
> Personally I think it is better to be e
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
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 decemb
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 s
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 O
