Hello,
>From: Vikram Kumar
>
>We have a multi-tenant Solr deployment with a core for each user.
>
>Due to the limitations we are facing with number of cores,
>lazy-loading (and associated warm-up times), we are researching about
>consolidating several users into one core with queries limited by
We have a multi-tenant Solr deployment with a core for each user.
Due to the limitations we are facing with number of cores,
lazy-loading (and associated warm-up times), we are researching about
consolidating several users into one core with queries limited by
user-id field.
My question is about
See below.
On Wed, Jan 19, 2011 at 7:26 PM, Joscha Feth wrote:
> Hello Erick,
>
> Thanks for your answer!
>
> But I question why you *require* many different indexes. [...] including
> > isolating one
> > users'
> > data from all others, [...]
>
>
> Yes, thats exactly what I am after - I need to
Hello Erick,
Thanks for your answer!
But I question why you *require* many different indexes. [...] including
> isolating one
> users'
> data from all others, [...]
Yes, thats exactly what I am after - I need to make sure that indexes don't
mix, as every user shall only be able to query his own
Solr will handle lots of cores, but that page is talking about lots.
Thousands.
But I question why you *require* many different indexes. It's perfectly
reasonable
to store different fields in different documents in the *same* index, unlike
a table in an RDBMS.
There are good reasons to have separ
Hello Solrs,
I am looking into using Solr, but my intended usage would require having
many different indexes which are not connected (e.g some index-tenancy with
one or multiple indexes per user).
I understand that creating independent indexes in Solr happens by creating
Solr cores via CoreAdmin.
