You should not be copying things into a Solr index unless
1> you absolutely and totally guarantee that no current Solr is running
2> you absolutely and totally guarantee that you replace it entirely
You're really just asking for maintenance issues with this approach. I'd do
one
of two things:
1>
Hi Alessandro,
The requirement is pretty simple. We have a product that makes use of
Solr collections. Anyone can download the product and deploy it locally
(alongside a local Solr instance) on their own machine and start using
it. To make it clear, each installation of the product operates by
Honestly is highly discouraged to share an index, making N Solr nodes using
it.
Can you express better your requirement ? Why can't you replicate the
index ?
Cheers
2015-09-23 15:37 GMT+01:00 Henrique O. Santos :
> Hello everyone,
>
> In our development efforts, we came into the necessity of sh
Hello everyone,
In our development efforts, we came into the necessity of sharing Solr
indexes with some initial documents to be deployed alongside our
application. For that, I just started copying the collection directory
with its conf and data subdirs.
That worked for some time, but it now
