On 5/11/2017 8:38 AM, Webster Homer wrote:
> When I ran the backup and restore of a real collection: which I restored to
> sial-catalog-product-2 I didn't see a new config for sial-catalog-product-2
> in Zookeeper. When I did what you describe it I see the config name is
> sial-catalog-product n
It appears that RESTORE pretty much ignores the configuration that was
backed up by the backup command, so why does backup bother?
The documented behavior of RESTORE is not very clear, and a scenario where
we are restoring a collection from a backup after the configuration in the
original collectio
When I ran the backup and restore of a real collection:
sial-catalog-product which I restored to sial-catalog-product-2 I didn't
see a new config for sial-catalog-product-2 in Zookeeper. When I did what
you describe it I see the config name is sial-catalog-product not
sial-catalog-product-2
So was
On 5/10/2017 12:26 PM, Webster Homer wrote:
> Looking at the solrcloud restore API I am confused about the solr
> configuration
> It seems to me that the restore should create a new configset in Zookeeper
> from the backed up configset and use the new collection name as the name of
> the config se
Looking at the solrcloud restore API I am confused about the solr
configuration
What configuration gets loaded into the restored collection? The one in
Zookeeper or the one from the backup?
Say I have a collection, BAZ which has a configuration BAZ.config
Now I create a backup of BAZ
I make chang
